“testflight the requested app is not avaliable”

Please review details using the below link: https://developer.apple.com/in-app-purchase/advanced-commerce-api/#determine-eligibility Technical Resources: https://developer.apple.com/documentation/advancedcommerceapi/ https://developer.apple.com/documentation/advancedcommerceapi/creating-your-purchases

Now i am honestly scratching my head. I just managed to submit an update for another one of my Apps, however the one that the DAC7 problem initially still fails with the same error. There is no difference. Both apps are new and first-time submissions, same global availability. How can this DAC7 compliance be an issue for just one app but work for another, this sounds like some backend issue at Apple. Again i would be happy if anyone else can just confirm this as well. Thanks! Robert

We have a VoIP app with more call features. Sometimes, we received some feedback about call ended. After checking the log file, it shows there are user actions (e.g., from func provider(_ provider: CXProvider, perform action: CXEndCallAction)), If you want to look into this in depth, then the best approach is to get the user to capture a sysdiagnose and use the console log to see if you can determine what's going on. A few notes on that: The log doesn't need to be captured immediately after the issue. Even logs captured a few hours later are often quite useful. It IS critical that the device NOT have been rebooted since the problem occurred. If it has been rebooted, so much log context is lost that the log is generally useless. You can find instructions for triggering and collecting a sysdiagnose here. Having said that, one comment on this: But the user said no user actions. So we doubt if there is a system-level event or error that will end this call. Then the details of the end ca

@itsme_joris The engineering team needs the sysdiagnose from the device to investigate what is going on with this app along with a matching screen recording if possible. Would you be able to provide that into the feedback assistant FB21867922? For more details on when you'll see updates to your report, please see What to expect after submission. Albert Pascual
  Worldwide Developer Relations.

Via a reply to FB22286320 last Friday I was told to verify it is fixed in macOS 26.4 (25E246). Not sure if they meant to make the VM on a 26.4 host or using the 26.4 restore image, but the latter still doesn't work on a Sequoia host without manually installing the mobile device support package (they still don't auto-download from the software update server). If they meant the former, well, I don't think that was under dispute ;) although given that 26.4 is released by now I suppose it really is only affecting Sequoia hosts at this point.

I'm seeing exactly the same crash, same source code, same Xcode version two weeks ago did not have the issue. I've pushed a new build 2 days ago and users with iOS 12 are getting a crash on launch.

Thank you so much Quinn, The documentation about uniqueness in the keychain, and the reset keychain function were extremely helpful in debugging my issues. I will lay them out here for other users who may end up in my prediciment. The import of the pk12 file was not putting keys in the keychain, the identity was leftover from previous testing, and was causing me more issues than I would like to admit. The posts you linked should be official documentation because they are more helpful than anything else I could find on my own. Once I was sure that I was adding the identity correctly, I found I was getting rejected for missing entitlements. I triple checked that everything was correct ( my plist info file was correctly adding my AppIdentifierPrefix ) I found something very frustrating in the official apple developer documenation: https://developer.apple.com/documentation/networkextension/nehotspoteapsettings/setidentity(_:)#Discussion $(TeamIdentifierPrefix)com.apple.networkextensionsharing. The entitl