Steps to reproduce:
Install & Launch App
When push notifications are registered, the push notification token received is a "production" push notification token rather than a "development" push notification token.
We are trying to test on the sandbox environment with development push notification tokens, however the apn-environment for all builds we release via TestFlight are being set to "production". We wish to distribute builds via TestFlight with apn-environment set to "development".
At the moment we have only found one way to run the app with apn-environment set to "development" which is to "Export" a Debug build, then manually install it on a device via iTunes on Windows machines. This method is not efficient or considered seamless enough for non-technical testers and stakeholders. They require a seamless way to receive Debug builds via TestFlight without resorting to other third-party platforms which allow us to manually upload the "Exported Debug build".
If anyone knows how to upload a "Debug" build to Testflight which will allow the user to receive a sandbox development push token with "apn-environment" set to development I would really appreciate it.
TestFlight
RSS for tagTestFlight within App Store Connect allows you to invite and manage testers who can install and beta test your iOS, iPadOS, tvOS, and watchOS apps using the TestFlight app on the App Store.
Posts under TestFlight tag
200 Posts
Sort by:
Post
Replies
Boosts
Views
Activity
While uploading the application into the TestFlight the following error received,
ITMS-90714: Invalid binary - The app contains one or more corrupted binaries. Please rebuild the app and resubmit.
After sometimes generate same configuration the application successfully submitted on the TestFlight.
We are using Xcode 15.3
We are received the following error while uploading the application into TestFlight. **ITMS-90714: Invalid binary - The app contains one or more corrupted binaries. Please rebuild the app and resubmit. **
After sometimes we submit the same application without changing the configurations application submitted successfully into the App Store.
We are using the Xcode 15.3 version.
Hi, our app has been using single size app icon for a while and today when I trying to upload a new version of our app I got an email from App Store Connect saying
ITMS-90013: Corrupt Image File - The image file 'AppIcon60x60@2x.png' appears to be corrupt.
We haven't touched the image for ages and these 60x60 image were generated by Xcode from the single 1024x1024 image supplied. I've tried to use a new image and still got the same error.
Does anyone experienced this recently?
My application runs smoothly in our local environment. however, we consistently encounter errors upon launch in TestFlight. Despite our efforts to update our libraries and address these issues, the problem still persists. For more detailed insight, I have attached the crash log here.
So, we've got a mobile app that is using background processing to occasionally scan for nearby BLE beacons. When running a debug / local build of the app, everything behaves as expected, but if we upload a build to TestFlight and install from there, the background processing doesn't happen.
This behavior would seem to point to a capability in the App ID not being provisioned, but when I look in the Identifiers section of Apple Developer, Background Modes as a capability isn't listed for either the existing Application Identifier or when creating a brand new one. The app has the Background Modes capability assigned if I look at it in XCode.
Any thoughts as to where to look next or what I'm missing?
Issue Description
The app exhibited one or more bugs that would negatively impact App Store users.
Bug description:
after we entered the provided credentials, an activity indicator was spinning indefinitely and we were unable to use the app
Review device details:
Device type: iPad Air (5th generation)
OS version: iOS 17.4.1
What have I done
So basically Apple is saying that there are issues with https requests that they are making when on App review
The problem is that it always works for me. I've tested on TestFlight on my iPhone and there's no issue. When I directly download the app from the app store in my mac, it works as well.
I've checked the backend logs during the time that the reviewer were checking my app, and there's not a single request made to the mobile login endpoint.
My backend infrastructure, which is hosted on Google Cloud Platform (GCP) in the United States, is configured without any IP-based geolocation blocking or regional access controls. I've tried using a VPN, and even asked to a friend to make a request from the US using Postman. It always worked.
I've tried putting a network checker just after the login attempt. It warns and shows a toast saying that there's no internet connection. Not allowing the request to be made.
I've implemented a timeout in the requests. I started with a 12s timeout. I went progressively downwards with 8s and 4s timeouts in my submissions, and all the submissions were rejected.
I've tried to reach Apple to give me more details about the environment that these networks are made, anything about the error itself. I went to both a Rejection Appeal and a reply to App review, and all that they gave me was the device type and the OS version.
If anyone has any tips or insights on debugging this issue, especially in scenarios involving App Store review processes where the behavior differs from other environments like TestFlight or direct downloads, I would really appreciate any guidance or suggestions on how to proceed.
3 months before I uploaded a build 1.0(1) and had 10000(not sure why it's showing 10001) public testers via public link. Now this build has expired and I've remove all these public testers, but seems these testers are still occupying the tester slots so that new testers are not able to join test for my new uploaded build 1.0(2), showing "beta is full" to them. I've been waiting for 2 days but those removed testers are still showing in the tester list as "deleted" status and not removed. I've tried upload new builds but it didn't work, what shall I do now?
I'm adding many users to internal testing purpose. A few users did't received and welcome to apple developer program after signing in from invitation email. I've checked and didn't they on the user lists, so I can't added to internal tester group. We've tried so many times. I noticed that every users that had the same problem didn't see the trust this device page during the signing process. How should I fix this problem.
Hi everyone,
Our app has been removed from App Store (the status is "Removed from App Store"). So I have prepared new build and tested it in a debug mode. Works fine. I have uploaded the release build to the App Store Connect and submitted it for Review. After couple of hours I received the message that the release build doesn't work for the apple reviewers. When I want to install the app through TestFlight it says that the app doesn't exist (I an see it after I press "Install" button in TestFlight, I guess the reason is because the app has been removed from App Store). IPA file doesn't work as well. IS there any way I can test the release build (through TestFlight or installing IPA)?
Thank you in advance
Test flight app install issue : After clicking install button getting this message as "Could not install appName" and The requested app is not available or does't exits.
After discussion with apple customer care also issue is not resolved
We run automated app uploads to Appstore Connect and TestFlight from our company servers, which are behind a firewall.
Our firewall is configured to allow connections to the HTTPS servers listed in the Transporter User Guide
The problem is, Apple adds new servers (e.g northamerica-1.object-storage.apple.com) to this list without prior announcements and this breaks our automated uploads
because our firewalls are not yet updated with the new servers. Transporter logs report vague errors which are difficult to
correlate with the new servers that were added. For example, the error msg is:
[06:45:19]: [iTMSTransporter] data: null
[06:45:19]: [iTMSTransporter] }
[06:45:19]: [iTMSTransporter] buildAssetSpi: class BuildRelationshipsBuildAssetDescription {
[06:45:19]: [iTMSTransporter] links: class AlbumLocalizationRelationshipsAlbumLinks {
[06:45:19]: [iTMSTransporter] self: https://contentdelivery.itunes.apple.com/<redacted>/iris/v1/builds/<redacted>/relationships/buildAssetSpi
[06:45:19]: [iTMSTransporter] related: https://contentdelivery.itunes.apple.com/MZContentDeliveryService/iris/v1/builds/<redacted>/buildAssetSpi
[06:45:19]: [iTMSTransporter] }
[06:45:19]: [iTMSTransporter] data: null
[06:45:19]: [iTMSTransporter] }
[06:45:19]: [iTMSTransporter] }
[06:45:19]: [iTMSTransporter] links: class ResourceLinks {
[06:45:19]: [iTMSTransporter] self: https://contentdelivery.itunes.apple.com/MZContentDeliveryService/iris/v1/builds/<redacted>
[06:45:19]: [iTMSTransporter] }
[06:45:19]: [iTMSTransporter] }
[06:45:19]: [iTMSTransporter] [2024-03-11 06:45:17 GMT] <main> DBG-X: Returning 1
[06:45:19]: iTunes Transporter output above ^
[06:45:19]: <redacted>.ipa11966153618006795338-swinfo.plist (1) - Bad Status received from server: 401
The above error had nothing to do with authentication or incorrect tokens. We solved it by adding "northamerica-1.object-storage.apple.com" to our firewalls and retrying appstore connect upload.
I'm trying to figure out ways to solve this problem.
Is there any way to subscribe to Apple notification emails/RSS feeds etc to get to know about new servers being added ahead of time ?
Are the wildcard domains -
*.object-storage.apple.com
*.blobstore.apple.com
sufficient to cover any new server that Apple adds to the list mentioned in the Transporter Guide ?
Hello,
I have noticed an issue when using my web application via TestFlight on iOS devices. When I try to print through the application, a message "This action will take you outside the app, press OK to continue" appears. This message prevents the user from printing documents from the application.
Steps to reproduce the issue:
Open my web application via TestFlight on an iOS device.
Press the print button in the application.
Expected behavior:
It is expected that the user can print documents from the web application via TestFlight without any obstacles.
Actual behavior:
When pressing the print button, a message "This action will take you outside the app, press OK to continue" appears, preventing printing.
Hi Team,
We were using Xcode 14 and were getting feedback for the builds submitted to Testflight.
We recently moved to Xcode 15. After this movement, we stopped getting the review feedback when we are submitting the app to Testflight. Please suggest. This is happening with one particular application's submission.
I tried submitting and reviewing but the application keeps reporting an error, please help me find a way to fix it?
After upload using transporter I get following message:
"Cannot be used with TestFlight because the signature for the bundle at “GSequencer.app” is missing an application identifier but has an application identifier in the provisioning profile for the bundle. Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight." (90886)
I am unsure about the cause of this problem, please give some advice howto fix?
On Testflight the SubscriptionStoreView() is loading endlessly (see Image below). In Xcode it works.
What could be the problem?
Hi
I Download my app from test flight, when i click submit button to a backend call. App expects to get back with the response from the backend, to take to next pages.
But the app seems to be stuck waiting for the backend response. No error messages seen. i am sure the backend call is blocked from the test flight version. Same code works well from emulator and the physical device from local and from Google PlayStore. Only the test flight is the problem.
I am sure i messed up some settings , My Info.plist has as in below, can anyone please help.
NSAppTransportSecurity
NSPinnedNetworkSecurityItems
MyBundleName
NSIncludesSubdomains
NSAllowsArbitraryLoads
NSPinnedCAIdentities
SPKI-SHA256-BASE64
THEKEY
Im building a small iphone app with StoreKit and currently testing it in testflight right on my mac, not on iphone. StoreKit part almost exactly copied from SKDemo from one of the Apple's WWDC. For some users and for myself Transaction.currentEntitlements always returns .unverified results. I double-checked Apple Connect settings, i checked my internet connection and everything is fine. Is there some pitfalls for testflight on mac? How can I find out what is causing this problem?
Hello Everyone,
I am having a problem here with my app. I developed a timer that play a sound .mp3 and the sound play every time that the timer start and finish.
Everything works very well in the simulator but not on the devices after I distribute the build and install using the testflight.
I saw the build content and the file is inside. However, I have no idea what I am doing wrong (if it is some option that i forgot to check or some problem in my code). Please, somebody can help me?
Here is the func with the path. (I inserted the sound on the root) in the same place that we can find the Contentview.
func playFinishSound() {
guard let url = Bundle.main.url(forResource: "finish_sound", withExtension: "mp3") else { return }
do {
player = try AVAudioPlayer(contentsOf: url)
player?.play()
} catch {
print("Error playing finish sound")
}
}
}
Thank you very much for your help. I appreciate.
Antonio