In our product, we are submitting app into appstore and testflight using Appstore connect api. We need information about status of the app submission both in appstore and testflight. I was hoping that any notification might be sent through webhook, but couldnt find any way. My requirement is keeping the app status of an app up-to-date (in our product). There are two ways to do that, 1- Regularly check status of the app using rest service (for example every 10 minutes) and update it. 2- Subscribe a service or create a webhook that can be used to notified about status changes. Is there any suggestion, or any guidence how can second way work? Is there any such options?

I've published my app on TestFlight and enabled the public beta link, allowing users to try out the app and provide feedback. I'm considering creating a custom TestFlight badge (Like this - https://askyourself.app/assets/testflight.png) for my app, linking it to the public beta link, and embedding it on my website. Is this an acceptable practice?

I am a watchOS 10.0 device, try to open the developer mode, according to the official website to enter the Settings > Privacy > Developer Mode. But I don't see the developer mode option, how do I turn on the developer mode for watchOS 10.0 device?

I am unable to view my app in testflight. i can see in apple connect but not in testflight. when i try to click the email link for update on in the app, I get the error that "cannot load app"

We have an app with a web extension for Safari. We developed this app for a couple of years. Recently when we pushed an update to TestFlight or the Mac App Store, the user that updated the app, there's the dialog from macOS that asks to : Close Safari to continue the update. Click on continue to quit "safari" … It seems a recent change. Is there a way to prevent quitting Safari when we push to update to TestFlight and Mac App Store?

Hello, Trying to upload build to AppStore but reciving ITMS-90809: Deprecated API Usage. We have tried all possible solutions i think. Searching some help and advice here. All help is appreciated. cmd + shift + f) to find if UIWebView command grep -r "UIWebView". Searched out in the code. There is no web view WKwebview is used in every file ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no longer accepted. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview).

My WatchOS sometimes just freeze and then I got this error message: "<BLSBacklightSceneUpdateAction: 0x18e539c0; info: <BSSettings: 0x18e70f40> {\n (1) = No;\n (2) = No;\n (3) = Yes;\n}; responder: <_BSActionResponder: 0xc0084f00; active: YES; waiting: YES> clientInvalidated = NO;\nclientEncoded = NO;\nclientResponded = NO;\nreply = <BSMachPortSendOnceRight: 0xc008ca60; usable: NO; (496:aa9f:send-once xpcCode) from (34:59d07:send-once take)>;\nannulled = NO;>" Does anyone have this issue? What is the reason and any solution for this? Thanks!

I tried to run my Flutter app in Xcode in release mode, but I got the error: module 'cloud_firestore' not found. When I run my app in debug mode, everything works as expected. I also uploaded my app to the App Store for TestFlight and when I download it there it crashes, but only after I log in with Firebase Authentication. I have verified that the platform: iOS version in the pod file matches the deployment info in Xcode and I have verified that I have runner.xcworkspace open. I have also tried - delete Podfile - 'flutter clean' - 'flutter pub get' - 'flutter build ios' But I still get the error and I think this is the problem why my app crashes on the TestFlight. I am not using the latest version of Xcode, could this be a problem? What else can I do?

A month ago, I released a new version for open testers on Testflight. After one week, I found that the number of installs was much lower than the previous version(10 vs 50+). So I check with our testers' latest version on their device. I count how many people updated the latest version by myself. The exact number was much higher than the number shown in the account (50 vs 10). Then I asked Apple support, he said one possible reason is the number of installs referenced is the number of new installs of the beta build. I searched the official definition of the number of installs, it means the number of installations on devices. And my previous version has very stable numbers except this new one. I am confused about this issue and what is the exact definition of the number of installs. I would appreciate it if someone can help me. Thanks!

If I have built an iPhone (iOS) app in Xcode and want to send it to external testers but some of them don't have access to an iOS device like an iPhone, will they be able to install the iOS app via TestFlight on their Apple Silicon M1 Mac (macOS) instead? Or does TestFlight only allow installs on the target OS?

I was uploading the app to TestFlight or App Store after the archive to test and distribute it. But my Xcode is crash while validating or uploading the app, showing the message below. Please let me know the reason and help me. If you need more information, please reply and I will answer. Any type of help or advice is welcome. Thanks. ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: Xcode [42129] Path: /Applications/Xcode15.3.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 15.3 (22618) Build Info: IDEApplication-22618000000000000~2 (15E204a) Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-04-09 18:01:42.1441 +0900 OS Version: macOS 14.2.1 (23C71) Report Version: 12 Anonymous UUID: 9333BC97-0E78-E2B5-688C-5907A9FE395D Sleep/Wake UUID: 7D678D23-CB4F-444D-BA99-1FECAD6A252B Time Awake Since Boot: 780000 seconds Time Since Wake: 14803 seconds System Integrity Protection: enabled Crashed Thread: 5 Dispatch queue: ConcurrentQueue: -[IDEDistributionPackagingStepViewController viewDidInstall]_block_invoke Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Xcode [42129] Application Specific Information: abort() called Application Specific Signatures: success Thread 0:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x185dd9874 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x185debcf0 mach_msg2_internal + 80 2 libsystem_kernel.dylib 0x185de24b0 mach_msg_overwrite + 476 3 libsystem_kernel.dylib 0x185dd9bf8 mach_msg + 24 4 CoreFoundation 0x185ef7bf4 __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x185ef64bc __CFRunLoopRun + 1208 6 CoreFoundation 0x185ef59ac CFRunLoopRunSpecific + 608 7 HIToolbox 0x1904a4448 RunCurrentEventLoopInMode + 292 8 HIToolbox 0x1904a4284 ReceiveNextEventCommon + 648 9 HIToolbox 0x1904a3fdc _BlockUntilNextEventMatchingListInModeWithFilter + 76 10 AppKit 0x1896d28a4 _DPSNextEvent + 660 11 AppKit 0x189eac980 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 716 12 DVTKit 0x106b8b858 -[DVTApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 300 13 AppKit 0x1896c5d50 -[NSApplication run] + 476 14 DVTKit 0x106b8ab24 -[DVTApplication run] + 60 15 AppKit 0x18969d014 NSApplicationMain + 880 16 dyld 0x185a990e0 start + 2360 Thread 1: 0 libsystem_kernel.dylib 0x185dd9874 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x185debcf0 mach_msg2_internal + 80 2 libsystem_kernel.dylib 0x185de24b0 mach_msg_overwrite + 476 3 libsystem_kernel.dylib 0x185dd9bf8 mach_msg + 24 4 CoreFoundation 0x185ef7bf4 __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x185ef64bc __CFRunLoopRun + 1208 6 CoreFoundation 0x185ef59ac CFRunLoopRunSpecific + 608 7 Foundation 0x186fffa38 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 212 8 DTDeviceKitBase 0x11572f300 +[DTDKRemoteDeviceConnection startServiceBrowsers] + 148 9 Foundation 0x186ff8fb4 __NSThread__start__ + 716 10 libsystem_pthread.dylib 0x185e1a034 _pthread_start + 136 11 libsystem_pthread.dylib 0x185e14e3c thread_start + 8

I recently switched from Admob to Applovin. It worked well in device but when I tried to deploy via Testflight, it failed with following error: Missing Info.plist value. A value for the key “WKApplication”, or “WKWatchKitApp” if your project has a WatchKit App Extension target, is required in “MyApp.app/AppLovinQualityServicePlugin.app” bundle. For details, see: https://developer.apple.com/documentation/watchkit/creating_independent_watchos_apps/setting_up_a_watchos_project (ID: 6caee3d2-4c60-4410-8d68-d0b3b68e1b53) My app is native iOS only and not watchOS app. What did I missing?

New Apple Developer here, I've built my first iOS app in Xcode and wants to get it onto some friends' iPhones to do some external testing and give me some feedback. I've read the Apple Developer documentation on how to use TestFlight, but it's not understandable since step 1 is entering information about the app in App Store Connect and step 2 is uploading the app to App Store Connect? Can someone please write some easy step-by-step directions on how to get an iOS app from Xcode onto external testers' iPhones for a first-timer in 2024? Thank you so much!

Unable to install app. The requested app is either unavailable or does not exist. I encountered this issue when using the upload store, which was not present before (only in testFlight).

After uploading an iOS app for peer testing, users got 'invitation expired' errors. The next day I'm attempting to fix this problem. The uploaded app no longer appears anywhere in the app's TestFlight pages. What happened? Ho do I fix it? I can't re-upload, of course I get 'that version already uploaded'.

I just submitted a build to TestFlight this morning that should have set off the same alarms as last week, but it didn't. We received no emails complaining about "ITMS-91053" violations like happened on this branch before. We've been working hard to figure out how to meet your new privacy requirements, and it's been quite frustrating. I thought I finally fixed it yesterday, but today I wanted to run a sanity test. I went back and created a build that should fail, but now that one is apparently fine as well. I'm at a complete loss.

We would like to include billing functionality for the first time in this version of our currently released application. We have confirmed that billing is in place in local testing, In reality, the billing element has not yet been reflected in the store because it has not yet been reviewed by Apple. We have been informed by Apple that the billing elements will be reflected at the same time as the app review, We think this is a bit risky considering that the billing process may not work and the app may not pass the review process. How can we test the billing process for the store? Any better suggestions are welcome.

We have a use case where we want to have two different builds of our app in TestFlight: one for the test environment and another for production. Each build has a different .env file associated with it, containing different values based on the environment. The test build will only be used by internal testers, whereas the production build will be used by both internal and external testers. I know there was a way years ago to append a suffix to the build number, something like 0.18.1-test, so we could specify which build specifically uses the test environment variables. However, when I try to submit a build to TestFlight with any alpha characters in the build number, App Store Connect rejects it with the error message: '0.18.1-test' is not a valid value for the attribute 'cfBundleShortVersionString'. Are there any current best practices or official guidelines from Apple on handling a scenario like this? What's the recommended approach for differentiating between test and production builds in TestFlight? Our first solution was to place all our test builds in VS App Center and production builds in TestFlight. However, Microsoft recently announced that VS App Center is being retired next year and recommends using TestFlight instead for iOS builds. So, we're looking for a solution that will work with TestFlight going forward.

When we try to add a tester or a group and submit for review, we get the error "There was an error processing your request. Please try again later."