“testflight the requested app is not avaliable”

Has this been an issue for ten years? I am still in a rejection loop, can't see the IAP/Sub section in the version. After creating a new sub product, re-building to change the product code the IAP/Sub section appeared, I linked the sub product to the app, added new build submitted for review and the link went away and of course because the product wasn't approved with the binary the in app purchase can't ever work

I signed up and paid on the 25th. After no response I called apple tech support. 2 hours later. The response is they can’t help me but would push my request up the chain. I just paid a second time thinking it may be a glitch. Honestly this is unacceptable. When my app had a million users will it take three weeks to reach apple when something goes wrong?!?!

Hi, App crashes on launch on iOS 26.3.1 after building with Xcode 26.4. dyld: Symbol not found: MetricKit.mxSignpost Works fine on iOS 26.4+. FB: FB22384135 Anyone else seeing this or any workaround? Thanks.

Referenced from: /private/var/containers/Bundle/Application/FF873B01-8EA2-4C96-9DBE-D2FDE6BD6B42/MyApp.app/MyApp.debug.dylib Expected in: /System/Library/Frameworks/MetricKit.framework/MetricKit Symbol not found: _$s9MetricKit10mxSignpost_3dso3log4name10signpostID__ySo03os_H7_type_ta_SVSo03OS_j1_F0Cs12StaticStringV0J0010OSSignpostI0VALSays7CVarArg_pGtF Referenced from: /private/var/containers/Bundle/Application/FF873B01-8EA2-4C96-9DBE-D2FDE6BD6B42/MyApp.app/MyApp.debug.dylib Expected in: /System/Library/Frameworks/MetricKit.framework/MetricKit dyld config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/usr/lib/libLogRedirect.dylib:/usr/lib/libBacktraceRecording.dylib:/usr/lib/libMainThreadChecker.dylib:/usr/lib/libRPAC.dylib:/usr/lib/libViewDebuggerSupport.dylib:/System/Library/PrivateFrameworks/GPUToolsCapture.framework/GPUToolsCapture Symbol not found: _$s9MetricKit10mxSignpost_3dso3log4name10signpostID__ySo03os_H7_type_ta_SVSo03OS_j1_F0Cs12Sta

I have sent an email through contact us, but there was no response. So frustrating! Let's hope God can help me.

Ziqiao, will this be fixed in 26.4.1? My app has been completely broken for over a week because of this which seems insane

Thank you again for your previous response. I'd like to follow up on one specific aspect: are there any special enterprise programs or partnerships (for example, for medical device manufacturers or healthcare institutions) that allow an app to obtain additional background execution capabilities or enhanced HealthKit access beyond what is available to a standard Apple Developer Program member? I understand that for a typical developer, continuous background execution is not permitted. However, I'm trying to determine whether there is any alternative path that would enable more persistent background health data monitoring for medical-grade applications. If such programs exist, I'd appreciate any guidance on how to explore or apply for them. Thank you for your time and insight.

I tested Xcode 26.5 beta 1 (build 17F5012f), released on 2026-03-30, and the issue remains unchanged: app-hosted unit tests still fail on the same physical iOS 16 device with Logic Testing Unavailable.

Distribution through the App Store requires a minimum deployment target of iOS 15. You can find this information listed on the Xcode Support webpage.

An iOS app can't continuously run in the background. For more information about iOS background execution limits, see here. For using HealthKit in background, see here. (The latter is about HealthKit in watchOS, but the situation is pretty much the same in iOS.) Emergency Contacts is a user feature. For privacy reason, there is no API to access the information. Given that the answer to your question 1 and 2 is no, you can't achieve the automated alerting either. Best, —— Ziqiao Chen  Worldwide Developer Relations.