“show when run”

@amacia See TN3186: Troubleshooting In-App Purchases availability in the sandbox identifies common configurations that make your In-App Purchases unavailable in the sandbox environment. With the production RevenueCat API key (iOS appl_..., same as the submitted build), everything works on local device but not when I download it from TestFlight....For IAP in WAITING_FOR_REVIEW, should App Review always use an Apple Sandbox account to test subscriptions until the product is fully approved? Apple reviews your In-App Purchases (consumable, non-consumable, auto-renewable subscription, and non-renewing subscription) in the sandbox, the same environment you use to test your products. TestFlight also uses the sandbox for In-App Purchases This environment uses data you configure for your app in App Store Connect when you call StoreKit APIs in your app. For Apple to review your products, they must exist in App Store Connect and you must submit them for review. Is it documented that StoreKit may not return products duri

@Gascad Your first subscription must be submitted with a new app version. Create your subscription, then select it from the app’s In-App Purchases and Subscriptions section on the version page before submitting the version to App Review. - However, I don't see a way to get to the in-app purchases and subscriptions part of the Version Page. When I see online videos they show a + button for the new versions but I don't see those for my app. As mentioned above, the In-App Purchases and Subscriptions section only appears when you have one or more products with the Ready to Submit status. For more information, see In-App Purchase statuses. Check the status of your In-App Purchases you wish to submit for review, if their status is Missing Metadata,complete any missing information. If their status is Waiting for Review or In Review, there is nothing to do. You already submitted them for review.

@selimce, @669miller , @Gascad , @slowfast , and @touchlinebet Apple reviews your In-App Purchases (consumable, non-consumable, auto-renewable subscription, and non-renewing subscription) in the sandbox, the same environment you use to test your products. This environment uses data you configure for your app in App Store Connect when you call StoreKit APIs in your app. For Apple to review your products, they must exist in App Store Connect and you must submit them for review. Same problem with non-renewable IAP. My review is rejected because of the IAP's were not seent in the sanbox environment. For us, it is seen in both xcode and testflight environments. Probably because of this bug in review view. Please follow these steps, then let me know about the outcome: Create a Sandbox Apple Account. On your testing device, sign into the above account. For more information, see Sign in to your Sandbox Apple Account for a development-signed app. Disable StoreKit Testing in Xcode in your Xcode project. Build and run

I have asked Claude - but it’s just running in circles: check Info.plist=ok, check entitlements=ok, check code (minimal)=ok, check iig=ok, check provisioning profile=ok, check build settings=ok, check ioreg=ok, check code signature=ok, start over Fair warning, I wouldn't expect AI to be all that helpful when working with DriverKit. As far as I can tell, it works well enough that it will get something to build, but small details are what tend to go wrong and that's exactly what these AI systems tend to miss. When I unplug the device, the driver process (ps aux) keeps running, causing a hard crash of the Mac with dext remove/or kill driver.dext process. Please file a bug on this and post the bug number back here. I'm sure the problem is your driver (more on that below), but we also shouldn't be panicking. In the bug, please include the following: A copy of the panic log. A copy of your DEXT project and your built and signed DEXT. Two IORegistryExplorer snapshots, one taken after your device wa

Thanks for the post. In the url you shared here shows the note: Add the CLRequireExplicitServiceSession property to your app’s Info.plist file to opt into this control behavior. You are completely correct in the documentation does not give you the type as far as I can see CLRequireExplicitServiceSession looks like indeed a Boolean, and it should be set to YES (or true) in your Info.plist. But I think a bug for that documentation should be a good idea. May I ask you to file a bug to improve that documentation? Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Is there anything you need to know besides the type? Albert
  Worldwide Developer Relations.

You are the man! Thnx Albert! Derive Mac Catalyst set to No was wat I needed. I'm running latest Xcode, so not sure what went wrong. And thank you for all the links! App is currently waiting for review. Reason for using catalyst was that it is an iOS first App, which happen to run great as a catalyst app on macOS without much tinkering.

My understanding is that software running on the host Mac is unable to connect to a server running on the VM via the public port (8000), even though you have forwarding configured in vmnet. Have you tried doing the same from some other machine on the host’s network, so X in this case? Wow. that worked. If i try to access from computer x in my host network with the ip address of the host:8000 it worked. when i try the same in the host itlsef with localhost or host ip it is not working. Is this is the way by design. Why it is not working if i do it from the host itself strange. Do i need to make some changes for this to work. Please enlighten me. thank you very much Now i know the port forwarding api is working as exected witht the limitation of not able to access the public port 8000 from the host itself.

Hello Quinn, Thank you for your response. I would like to know if there is any possible method to fetch or read certificates available on IOS system keychain from enterprise in-house app or not ? Our end goal is that the app requires the com.apple.managed-keychain entitlement to: Verify S/MIME certificate presence — confirm the MDM-pushed certificate has been successfully installed on the device keychain Read certificate expiry date — check the kSecAttrNotValidAfter attribute to determine validity and warn users of upcoming expiry Distinguish cert states — differentiate between a missing certificate, an expired certificate, and a valid certificate, in order to show the correct status and remediation action to the user If yes, kindly provide the details for further action.