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?

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).

我构建了一个新的应用程序，还未发布到应用市场，只是提交了测试，前面都是正常的 但是今天TestFlight提审时提示“你的请求无法完成请稍后再试” 内部测试包能上传，但是测试机下载测试时提示“所请求的应用不存在或不可用” 有哪位大大能帮忙解决么？急急急····

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.

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.

Title pretty much summarizes it. Submitted it for review on March 15th under an organization. Currently it is the 28th with no update. Any ideas?

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."

Dears, I have been exploring the documentation provided by Apple regarding app data management through API requests. Specifically, I am interested in the possibility of initiating the app creation process itself using a POST API request sent via Postman or similar tools. Attached is the documentation link I've been referring to: https://developer.apple.com/help/app-store-connect/create-an-app-record/add-a-new-app Could you kindly assist me in clarifying whether it's feasible to create an entire application using such API requests? If not, I would appreciate any guidance or resources you could provide on the appropriate procedures for app creation within the Apple ecosystem. Thank you very much for your time and assistance. I look forward to your response. Warm regards,

I successfully submitted my project to App Store Connect, and got it approved for external TestFlight testing. I have made updates to my project, and am trying to submit another build, but am getting the error: "The value for key CFBundeShortVersionString[1.0] in info.plist must contain a higher version.." I attempt to change both the short bundle version, and regular bundle version to 1.1.0 without any luck. I also attempted to go into the "Versioning" within build settings to change both the current project version and marketing version to 1.1.0 without any luck. I am confused what is going on, and why my build is not just incrementing as expected. Any suggestions is very appreciated.

What if I already have an app named "A" but want to upload a new application named "A" The same thing where the old app and can still be used and the new app can still be displayed? **If there are details showing that duplicate names cannot exist, please attach them to me. thank you.

I'm about to submit a react native expo app to the ios app store. Locally the app seems to be fine but when I try testing it with test flight, it crashes on start up. Please see the attached crash log. Crash Log Any help would be greatly appreciated.

In TestFlight I have the problem that I only get crash information from a small fraction of testers. I assume this is because when the application crashes, it responds "No Thanks" when asked to share information with the developer. Is this really the case? What's the point of testing if all I see is the crash counter popping up and I'm not getting any error reports? Installation can be conditioned on acceptance with a "Term of service" that says crash reports will be shared. Without accepting the conditions, the application cannot be installed. But I don't know if this consent has any effect on sending error reports. Does it have any effect on sending error messages? Can anyone advise me what I should set to get such a prompt before installation. Alternatively, how can I arrange to receive more crash reports? Or should I use another service that will give me reports of all errors? Maybe Crashlytics?

I have created a new build for my Safari web extension and distrbuted it to test flight. Test Flight says I am using the correct version - but when I go to the Setting > Extensions in Safari and enable it - it still has the old version number. App Store showing the correct version is in testing Test Flight confirming said version number Safari with the incorrect version Any idea what I am doing wrong?