Navigate the App Store landscape. Share strategies for app submission, distribution, marketing, and user acquisition. Discuss best practices for getting your app discovered and downloaded.

All subtopics

Post

Replies

Boosts

Views

Activity

The status of "waiting for review" has been waiting for almost 2 weeks
Dear App Review: We are an image processing software that undergoes regular iterations and updates with new features every month. At present, our updated version has been waiting for almost 2 weeks in the "waiting for review" state. During this waiting process, we have made the following actions but are unable to enter the review process: We requested an expedited review and informed that it was successful, but no progress was made; Contacted "App Review Status" via email; Please inform us that everything is normal and wait for the review; Refused by oneself, resubmit for review; Our users have been anxiously asking us when to update the new features, and they are very eager to use them. Apple ID of the App:6447539504 Looking forward to your reply, thank you!
3
0
161
4d
documentation to demonstrate that you are currently authorized by the rights holder to represent the products For My Own App on Google Play Store
Apple Rejected my Game which is published on my Google Play Account. It Requires me to Send the documentation to demonstrate that you are currently authorized by the rights holder to represent the products. I have sent them My Google Play Console Screenshot for the proof But they are requiring to submit documentation for that. Can you please guide me how can I prove them that I own that game in third party store? It has same package name and website/Privacy Policy links etc.
1
0
40
1d
App refused by Apple with error ITMS-90338: Non-public API usage
Hi, we were able to migrate our solution from Xamarin to MAUI (.net 8). After a 2 weeks fight, the app is finally working on my dev devices. Unfortunately, after sending the app to review, it gets rejected because of the following: ITMS-90338: Non-public API usage - The app references non-public symbols in [Our app name]: _SCDynamicStoreCreate, _SCDynamicStoreCreateRunLoopSource, _SCDynamicStoreKeyCreateNetworkServiceEntity, _SCDynamicStoreSetNotificationKeys. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ From what I understand, this is because the 4 methods (_SCDynamicStoreCreate, _SCDynamicStoreCreateRunLoopSource, _SCDynamicStoreKeyCreateNetworkServiceEntity, _SCDynamicStoreSetNotificationKeys) exists in the generated Mach-O binary. Those methods are not used directly by our application but because of HttpClient we are using to request our business API The methods are implemented in the System.Net.NetworkInformation assembly which is referenced in the System.Net.Http assembly Given to the MAUI Team those methods are public and should not be rejected (https://github.com/dotnet/maui/issues/23210#issuecomment-2186038540) Kind regards
24
25
841
4d
Apple Appstore Summary Sales Report API updates historical reports without notification
I've had several internal users note that the Summary Sales report API has started to have updates to historical reports. As an example - a subscription quantity might be 1 when the API is queried for 1/15/24, but then if the API is queried and reconciled against itself it might be quantity of 3 when pulled 3/15/24. This only started after 1/1/24, so I am wondering if there was a change to the report logic, or a new policy that Apple has started to allow that is making backdated changes to the summary sales report. This is causing a lot of potential missed revenue and manual effort for our accounting teams. Is there any guidance that Apple team or others can provide on this topic?
2
0
116
1w
Is it possible to return someone's APP info (not mine) from "List All Customer Reviews for an App" API?
Hi, is it possible to use the "List All Customer Reviews for an App" API to get the reviews for someone else's app (not ours)? Or is it only possible to get reviews for our own app? https://developer.apple.com/documentation/appstoreconnectapi/list_all_customer_reviews_for_an_app We're considering to join Developer Program if it is possible to return SOMEONE(not ours)'s APP review data as well. Thank you in advance.
1
0
75
3d
Enrollment Process Takes Months NO UPDATE
I have been trying to complete my enrollment for the past three months, but I keep encountering an issue when uploading my payment information. Despite using three different cards (debit and credit) and a Revolut card, all valid and with sufficient funds, I still see this message: "To continue your enrollment, complete your purchase now. Your purchase may take up to 48 hours to process." I have opened support tickets weekly but have not received any response. Additionally, the person who was previously assisting me has stopped responding. Can someone please help resolve this issue urgently? Thank you,
0
0
57
2d
App Store - Web site subscription
Hi, I read the requirements for the App Store. Specifically the subscription section. I understand for app subscriptions that there are Apple requirements around that with Apply Pay and such. However, the subscriptions are web site subscriptions for workout videos. The payments are done on the web site and the user will log in via the app to view the video. They can only sign up if they make a purchase on the web site. Is this going to be denied from the app store? All payments are done on web site and the app is to log in and view the content.
1
0
92
5d
App Stuck "In Review" for Critical Bug Fix
Hello, We are seeking urgent assistance with our app, which has been stuck "In Review" for 2-3 days now despite an expedited review request. Our app is currently experiencing a critical issue where the subscription screen crashes due to the app being approved while the associated subscription product IDs were rejected without our knowledge. We have since created new subscription product IDs (which have now been approved) and updated our binary to include these updated IDs. However, we just can't get the review for the app to be finalized. This subscription is for a new feature we spent months building and aimed to monetize out of the gate. Instead, we are now faced with many frustrated users who can't subscribe to this feature, which also has a financial impact on our business. After being "In Review" for 36 hours, we removed the app from review and resubmitted it since it seemed to be stuck, but it has been back "In Review" again for the past 20 hours. We have spoken with several Apple Developer Support reps by phone and email, but there hasn't been any change in status. Could anyone provide advice on how to escalate this issue further or any other steps we might take to get urgent assistance? Thank you so much in advance for your help.
7
0
299
3w
Parent Gfit In-App Subscription to their Child
Our app has a parent account that can view their child's account activity for the free version but we have in-app subscriptions and trying to figure out how the parent can choose to purchase or pay for their child's in-app subscription from their apple Id account. Gifting? Family Sharing? Redeem Code? All keep showing up in my research but I am struggling with how to best execute this? Any advie or insight is helpful!!
1
0
80
1w
The status of version x.x.x has changed to Invalid Binary
We have developed a software called xxxxxxxxxx, using the "react-native-star-io10" library (version 1.3.0) to communicate with Star Micronic printers. In older versions, we utilized this library solely for local network printer communication. In an unreleased test version, we attempted to add Bluetooth printer connectivity to the project. However, due to prolonged validation and approval processes by Star Micronic, we opted to remove this feature from the current version of the project. Currently, we are facing a major issue: when we remove the Bluetooth permission keys from the Info.plist file and archive the project, upon upload, we encounter the error "The status of version x.x.x has changed to Invalid Binary." However, when we add the Bluetooth permission keys back to the application, archive the file, and upload it, the software ultimately gets rejected during the In Review phase. We are not utilizing Bluetooth in this version of the software and wish to deliver this version to our users. We plan to add the Bluetooth feature in a future release. Please advise on how we can resolve this issue or if there are specific changes needed in our project asap. Thank you for your attention.
0
0
78
2d
Can't transfer my apps
Hello, I had an active Apple development account, and after several unsuccessful attempts from your end to pull the money from my account, it is now disabled. I've created a new personal Apple development account and am now trying to transfer my apps to my personal account, but I'm getting the following error: *Internal failure Something went wrong with your request. Try again later. Any suggestions on how I can solve this issue and transfer my apps to my new account? Thank you!
0
0
56
2d
TestFlight not working with In-app purchases
Environment react-native-iap: 12.12.2. react-native: 0.72.12. Platforms (physical & simulator): iPhone 11 - OS version 17.4 /// iOS Simulator iPhone 15 Pro Max - OS version 17.4 Description Hello, I am trying to test the purchase of a subscription and an in-app product within my react native app. I have setup the necessary Sandbox account in App Store Connect, created a Store kit file in Xcode that I also synced with the products I created in the App Store Connect dashboard. If I use Xcode to run the app on a physical device (after logging into the sandbox account), I am able to purchase a subscription/in-app product without any issues. If I purchased a subscription on the physical phone I can go into Settings > App Store > Sandbox Account Management and see the purchased subscription, change renewal rate, clear purchase history etc.. If I use the TestFlight build with a physical phone (logging in with the sandbox account) the in app purchases stop working correctly. After purchasing a subscription it is not shown in the Sandbox Account Management, so I am unable to cancel it. Upon trying to purchase another subscription the apple service keeps returning the same exact subscription that I "originally" purchased. How am I supposed to cancel that subscription if it not shown in the sandbox account subscription list? Adding a different sandbox account does not help either, trying to purchase another subscription returns the same subscription that I am unable to cancel. Is there a step in the TestFlight environment that I am missing on setup? Expected Behavior Upon purchasing a subscription in the TestFlight environment on a physical device I should be able to cancel that subscription. Here's an example of what function I am calling on purchasing a subscription: const product = { productId: 'example_monthly_subscription' }; subscribe(product.productId); Any help would be appreciated.
1
0
177
2w
TestFlight build upload with error ITMS-90338: Non-public API usage
Hello, today when we uploaded a new TestFlight Mac Catalyst build we received an email about the build being invalid: TMS-90338: Non-public API usage - The app references non-public symbols in {app name}: _AVCaptureDeviceTypeBuiltInTelephotoCamera, _AVCaptureDeviceTypeBuiltInTrueDepthCamera, _AVCaptureDeviceTypeBuiltInUltraWideCamera, _AVCaptureSessionInterruptionReasonKey, _AVCaptureSessionInterruptionSystemPressureStateKey, _AVCaptureSystemPressureLevelCritical, _AVCaptureSystemPressureLevelFair, _AVCaptureSystemPressureLevelNominal, _AVCaptureSystemPressureLevelSerious, _AVCaptureSystemPressureLevelShutdown. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. For further information, visit the Technical Support Information at http://developer.apple.com/support/technical/ We've been uploading builds the same way for months, using the same Xcode 15.2 and dependency versions, and have checked our most recent commits since the last release and nothing was updated around AVFoundation, archiving, etc. Did anything change on Apple's side recently? We use Xcode 15.2 to build/archive/upload and xcodebuild to run all commands.
2
3
222
3d
App Review Rejection for Guidelines 3.1.1
Hi all, Our app has been rejected several times without any clear explanation of what we need to do. The latest rejection reason is as follows: Guidelines 3.1.1 - In-App Purchase and 3.1.3(c) - Enterprise Services We noticed in our review that your app offers enterprise services that are sold directly to organizations or groups of employees or students. However, these same services are also available to be sold to single users, consumers, or for family use without using in-app purchase. When an organization or group buys access to your app's enterprise services, you don't need to use in-app purchase. But when providing access to an individual user, consumer, or for family use, you should use in-app purchase. To which we responded with: We would also like to clarify our app and business model: 1) Our app is a free app intended for companies, organizations, and business owners. Individual users can sign up for our app, but with some restrictions. We designed it this way so that users can try our app before registering their company or business. 2) In the previous app version, we enabled users to subscribe and unlock more features within our app using our own mechanism. Hence, the review referred to Guidelines 3.1.1. In this version, we have removed the feature so that users cannot purchase any subscriptions. Since users cannot purchase anything from our app, we believe Guidelines 3.1.1 should no longer apply for the app review. But our app is still not approved. Instead, they replied with: We are not able to provide feedback on app concepts or features, but we recommend evaluating your suggestions against the App Review Guidelines, as well as the Apple Developer Program License Agreement, and the Human Interface Guidelines. Can anyone enlighten us why does the reviewer still referring to Guidelines 3.1.1 when there isn't anything that user can purchase from our app? And what do they actually want us to do?
3
0
180
1w