Context: We are developing an SDK to support global age verification regulations (e.g., Texas HB 18, Brazil’s LGPD). We plan to use the DeclaredAgeRange and PermissionKit frameworks. We want to verify if our proposed "Block-by-Default" sequence for non-compliant states is legally and policy-compliant according to Apple’s standards. Detailed Workflow Description: Initial Authentication: After the user logs in, the SDK calls requestAgeRange(ageGates: 13, 16, 18). Handling Sharing Status: If Declined: If the user declines age sharing (.declinedSharing), the SDK blocks app access and displays a popup guiding them to enable sharing in System Settings. Age Verification Results: Adult (VERIFIED, 18+): Immediate access to the game. Non-Regulated Region (UNKNOWN): Access to the game is allowed. Minor (SUPERVISED, 13-17): Step A (Age Gate): We check if they are 13+. If they are under 13, we block access and show an "Underage" notice. Step B (Family Sharing): If they are 13+, we check if Family Sharing is linked. If NOT linked, we block access and show a guide to set up Family Sharing. Significant Update & Parental Consent: If a "Significant App Update" requires consent (via requiredRegulatoryFeatures), we call AskCenter.shared.ask with a SignificantAppUpdateTopic. If Approved: The minor is allowed to proceed to the game. If Denied/Pending: Access is blocked, and a "Parental Consent Required" notice is displayed. Information Unavailable (REQUIRED): If age info cannot be verified, access is blocked with a guide on how to provide age information. Specific Questions for Feedback: Blocking for Non-Consent: In regions where Age Assurance is legally required, is it acceptable under App Store Review Guidelines to block app functionality for users who choose .declinedSharing? Mandatory Family Sharing: Is it permissible to require Family Sharing for 13-17-year-old minors to access the app, or must we provide alternative parental verification methods (e.g., credit card verification) for those not using Family Sharing? VPC Compliance: Does using SignificantAppUpdateTopic via AskCenter satisfy the "Verifiable Parental Consent (VPC)" requirements for regulations like Texas HB 18 or Brazil's LGPD for initial gameplay access? User Experience (UX): Does this "Strict Blocking" approach for unverified or non-consented states violate any policies regarding "App Functionality" or "Data Privacy," even if implemented for legal compliance?

I understand from the recent Apple Developer News that Korean developers are now required to register a URL to receive notifications from the Apple server when creating or modifying a Sign in With Apple Service ID. However, it is not clear whether simply registering the URL is sufficient, or if it is also mandatory to implement the real-time processing of those notifications. I am inquiring whether the processing part is also a mandatory requirement.

I've noticed that despite Apple stating Xcode 16's minimum deployment target is iOS 13, I was able to set my app's minimum target to iOS 12, build it, and successfully upload it to TestFlight. I've tested the app on iOS 12 devices, and it functions normally. Given that updating to Xcode 16 will be mandatory after April 24th, I have a few questions: Is it intentional that Xcode 16 still allows targeting iOS 12? Will Apple continue to support this capability for iOS 12 devices in the future? Are there any plans to restrict or block apps targeting iOS 12 in upcoming Xcode updates? I'm seeking clarification on whether it's safe to continue supporting iOS 12 in our apps or if we should prepare for potential changes. Any insights from the Apple development team would be greatly appreciated.

I've noticed that despite Apple stating Xcode 16's minimum deployment target is iOS 13, I was able to set my app's minimum target to iOS 12, build it, and successfully upload it to TestFlight. I've tested the app on iOS 12 devices, and it functions normally. Given that updating to Xcode 16 will be mandatory after April 24th, I have a few questions: Is it intentional that Xcode 16 still allows targeting iOS 12? Will Apple continue to support this capability for iOS 12 devices in the future? Are there any plans to restrict or block apps targeting iOS 12 in upcoming Xcode updates? I'm seeking clarification on whether it's safe to continue supporting iOS 12 in our apps or if we should prepare for potential changes. Any insights from the Apple development team would be greatly appreciated.

As verifyReceipt has been deprecated this time, I am trying to verify the receipt using Get Transaction History Endpoint. Apparently, Apple's official document says it will return the value for a single transaction if you request it to the endpoint, but it keeps returning the value by combining all the information about different Transaction IDs. If there are developers who know about this, please answer. Also, please let me know if anyone knows how to verify the receipt using this endpoint.