Our app (Bundle ID: org.grapplermobileapp) has the In-App Purchase capability enabled in the Apple Developer portal (checkbox is grayed out and checked). However, any new App Store provisioning profile we create for this App ID is missing the entitlement: com.apple.developer.in-app-purchase We confirmed this by inspecting the .mobileprovision file directly. As a result, all iOS builds fail with the error: Provisioning profile doesn't include the com.apple.developer.in-app-purchase entitlement Steps we've already taken: Deleted and re-created provisioning profiles (both automatic via Expo/EAS and manual in Developer portal). Uploaded the profile manually into EAS and rebuilt. Verified the entitlement is missing by searching the .mobileprovision file. Opened a support case (#102688824691). Apple Developer Support escalated, but then replied that In-App Purchase is a capability and not an entitlement, and directed me to the forums. So we’re stuck. The App ID shows IAP enabled, but profiles never include the entitlement, and builds cannot proceed. Has anyone seen this issue where Apple’s system fails to embed com.apple.developer.in-app-purchase into profiles? If so, how was it resolved?

Hello, I have a couple questions about compliance with the "Account deletion within apps" requirement. My app requires an email & password to login. That information is stored inside a MySQL database. The app is sold only as a one-time payment for life-time access, not a monthly recurring payment. The user is added to the database using Zapier. Even though there is no recurring payment, Is their username, email & password still considered an "account" and therefore is subject to this requirement? If so, do I need to provide a link that automatically removes that info from the MySQL database, or can it send a notification to me so I can manually remove them? The user paid for lifetime access. However, once they are removed from the MySQL database, there will be no record of them. If they click the link to remove themselves by mistake or decide they want to access it again, there are 2 problems: We will have no record that they ever paid, so they would be required to buy it again. Is that correct? We will have no record or evidence that they removed themselves from the database (because their data has been removed), which will lead to disputes if a user denies that they removed their data. How do we handle this situation?