“Account Locked”

Thank you for your response. I understand the following point: To summarize this interpretation: Existence of a 410 status merely indicates that the token is no longer valid and should not be used anymore. However, in some cases it is difficult to associate a device token with a user account because the app does not provide a login feature or user accounts. In our case, the following scenario can occur: The user installs the app on a device (IDFV: A, DeviceToken: a) The user uninstalls the app The user reinstalls the app on the same device (IDFV: B, DeviceToken: b) Push notifications are sent using both DeviceToken: a and DeviceToken: b As a result, two push notifications are delivered to the same device If we cannot associate the device token with a user account, what would be the recommended way to prevent duplicate push notifications being delivered to the same device in this situation? I would appreciate your guidance.

Thank you for your reply, and I apologize for not providing enough detail earlier. Our app is built with React Native, and we implemented in-app purchases using an OpenIAP-related library that supports StoreKit 2. We are currently testing with a Sandbox account. The feature itself is not completely broken, but we are seeing several abnormal behaviors during testing. For example, even when a purchase is attempted only once, we sometimes receive the purchase-completed message two or three times. We have also observed other inconsistent behaviors during Sandbox testing. Because of this, we were wondering whether this might be related to instability or known issues in the Sandbox environment, rather than being entirely caused by our implementation. Has anyone experienced similar issues when testing subscriptions with StoreKit 2 in a React Native environment? If there are any known Sandbox limitations or specific points we should check first, I would greatly appreciate your advice.

Same, not sure if it's something on AppFigures side or on the Apple side. But something I noticed was that if I go to /agreements, there's a redirect back to /business. But for a split second, I saw that something was wrong with my bank account setup for paid apps. Though on the /business site, everything looks fine. Tried to get more time with simulating throttling via Chrome, but didn't gather any more information.

Hi @shirakura, Thanks for reporting the unexpected behavior you've observed in the Sandbox environment. For Apple Pay merchants using the Sandbox payment gateway, the user and device must now be a sandbox tester account. Previously, both production and sandbox tester accounts were supported. Could you please confirm you've configured the device to test against the Apple Pay & Wallet Sandbox? To confirm this, your device should be logged in with a sandbox tester account: Sandbox Testing https://developer.apple.com/apple-pay/sandbox-testing/ If your device is using a sandbox test account for Apple Pay and Wallet, the Apple Pay Server engineering team would need to investigate this issue directly via Feedback Assistant. To submit a bug report, please follow the steps outlined in the post below: Gathering Required Information for Troubleshooting Apple Pay on the Web Merchant Issues https://developer.apple.com/forums/thread/762994 Once submitted, please reply here with your

@Dimbonder was your problem resolved? I am in the same situation - app approved, non-consumable IAP 'in review'. My app will lock up and show a paywall in 14 days, so it doesn't make much sense to announce my app without IAP approval.

Hello, You can find most of the answers and details to your points by going through the Supporting offer codes in your app article, but let me give you a summary to your specific questions: You can test offer codes in the sandbox environment for all In-App Purchase product types: consumable, non-consumable, non-renewing subscription, and auto-renewable subscription. To redeem an offer code in the sandbox environment, follow these steps: On your device, sign in using a Sandbox Apple Account. On the Sandbox Account Settings page, tap Initiate Transaction. Select Offer Codes and redeem a sandbox offer code you created in App Store Connect. You can use the information contained in the transaction to identify products purchased with offer codes, you need to check the offer property of Transaction on StoreKit, or the offerIdentifier if you're using the App Store Server API or notifications. If you're not using it yet, we highly recommend using the App Store Server libraries to adopt the App Store

Thanks for your post and congratulations on having that game almost completed. About your Apple Developer Account, have you login into the account and do you see the submit button for apps? The Developer Account team does not monitor the forums very often, if you have questions about your account, I would recommend you to contact the developer account support at https://developer.apple.com/contact to make sure they are aware of the issue. Albert Pascual
  Worldwide Developer Relations.

Hi, We've managed to get subscription data in the end. :) Data for few sections were missing. Business information i.e. Tax forms, Bank accounts, Business agreements. Info under In-App Purchases was missing After filling up those forms we started to receive subscription data to our app after rebuild. Hope it helps

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. [quote='818322021, Chandrashakar, /thread/818322, /profile/Chandrashakar'] Is this the in-depth analysis path … ? [/quote] It certainly looks that way. [quote='818322021, Chandrashakar, /thread/818322, /profile/Chandrashakar'] for new accounts [/quote] It can be triggered by a variety of criteria. [quote='818322021, Chandrashakar, /thread/818322, /profile/Chandrashakar'] Any ETA … ? [/quote] Usually this clears in a few days. If you remain stuck after a week, lemme know by replying here. [quote='818322021, Chandrashakar, /thread/818322, /profile/Chandrashakar'] workaround? [/quote] No.

@Etresoft I am 100% I resolved the issues mentioned during the last review (Adding Apple Sign in method + letting access to the app content before requiring users to login/register), so I am 99% sure the app will pass. The only problem is that : when responding to the review process, I did not have a new build, so I could not do respond (by adding screenshots) + submit again when I added my new build, it went straight as a submitted item (without me able to add explanations of what was changed, although it is implied that the issues mentioned were addressed), I just sent a new build and was locked out of the item draft screenshot I showed earlier (The only option on that draft submission page was cancel the submission of course, but I did not want to cancel submission of my new build). And now look at this image, the app show at the same time as : Waiting for Review and: In Review Does that happen usually? It's been 8H30 since it's in review The first time it was in review, it was reviewed within 32