Post

Replies

Boosts

Views

Activity

Reply to About Guideline 2.1 - Performance in-app purchase functionality is not present
Latest progress: As I expected, I used Storekit1 and the App passed the review. I will change to Storekit2 later. DTS gave me a new reply, still asking me to look through TN3186. And mentioned that IAP will become "In review" during the review, which is obviously not the case. This is the key problem. DTS still did not read my post in the forum.
Jul ’25
Reply to About Guideline 2.1 - Performance in-app purchase functionality is not present
Regarding the issue of in-app purchase labels showing Arabic in the US, it is because after the in-app purchase is rejected, Apple will display the first localized label by default, which is Arabic. This is also consistent with my guess. After testing, it was found that it was like this (I modified a localized label and it became "Ready to Submit"), and then the in-app purchase information was not displayed in Arabic. Because the communication time with DTS was tooooooo long, I could no longer wait. So, today I changed the in-app purchase function to Storekit1 and submitted it for review.
Jul ’25
Reply to About Guideline 2.1 - Performance in-app purchase functionality is not present
Day 9 of waiting for DTS. Summarize yesterday's communication with the reviewer. Yesterday, the in-app purchase information of the app quietly became "Developer Action Needed", and the reviewer replied with a message a few hours later. The reviewer said that the in-app purchase information can be displayed, but the Arabic label is displayed on the machine with the US language setting. And after pressing the purchase button, the in-app purchase is not completed. Users still cannot purchase IAP. I replied: My language has also become Arabic, but the purchase can be made. I asked: I did not submit a new binary file, nor did I do anything on AppStore Connect. Why can the reviewer see the in-app purchase information now? Instead of the original null (null). The reviewer replied that they were not sure what the problem was, and since I contacted DTS, I would wait for a response.
Jul ’25
Reply to About Guideline 2.1 - Performance in-app purchase functionality is not present
A few minutes after I responded to the reviewer, the reviewer sent a new response. He said that the in-app purchase information can be seen, but it is in Arabic. I guess it may be that Arabic starts with A and is listed in the first line of AppStore Localization. I did not submit a new binary file or do anything on appstoreconnect.
Jul ’25
Reply to App rejected for - Guideline 2.1 - Performance - App Completeness
2025 year I have encountered this problem twice in a row (the first time I didn't know the reason and it passed the review). I don't know what to do. This time, everything was normal in Xcode and TestFlight, but the reviewer couldn't see the in-app purchase information, saying it was null. They kept telling me that there was a 2.1 problem. In fact, it was just one line of code: try await Product.products(for: [productId]), which returned 0 products to the reviewer, but 1 was returned here.
Topic: App & System Services SubTopic: StoreKit Tags:
Jun ’25
Reply to Sandbox: Testing in app purchase issue (no products retrieved from app store connect)
I have encountered this problem twice in a row (the first time I didn't know the reason and it passed the review). I don't know what to do. This time, everything was normal in Xcode and TestFlight, but the reviewer couldn't see the in-app purchase information, saying it was null. They kept telling me that there was a 2.1 problem. In fact, it was just one line of code: try await Product.products(for: [productId]), which returned 0 products to the reviewer, but 1 was returned here.
Jun ’25