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

In order to have ads on Meta that link to the App Store directly (instead of to a website) Meta requires that I install the FB SDK. Now: Apple requires an ATT permission popup if a user is being tracked. I've installed the SDK but turned all tracking off by default (so it behaves as though the user said "no" to the ATT popup) and it's still not passing review. Any ideas as to what I could try next?

Our submitted binary app version has been approved by Apple reviewers. It's currently pending Developer Release. However, our in-app purchase, which was submitted at the same time, is still under review. Since the newly added in-app purchase hasn't been approved yet, we've decided to hold off on releasing the binary app version. Should we just wait for Apple to approve the in-app purchase, or are there any other recommended actions? Thank you.

Hello everyone, I have a question, can anyone help me answer it? Thank you very much! I am developing a health application for my company’s employees, which has a large number of employees (more than 1000 employees). Once it is completed, I want to publish it on the Apple Store. Our employees are provided with login accounts, so there is no account creation function. Will my application be approved?

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.

I'm unable to reproduce an issue which only seems to occur on App Review devices. It's mainly stuck at a loading screen when trying to sign in with GameCenter. I'm using Microsoft Azure PlayFab as a game backend. I've tested my game on two iPads and three different iPhone models. They're all able to connect to the server. No debug build was installed on those devices via Xcode. I used the same build which was rejected, freshly installed via TestFlight on the internal test track. Looking at my server logs, I can't even find one single request sent from the App Review device. This can only mean that there is some connectivity issue between their device and the server (e.g. a firewall or proxy). I've also implemented a retry mechanism so in case the request times out, it would try it again and after three retries it would eventually display an error message and further details. How shall I figure this issue out, if the only thing the reviewers provided me is a screenshot of the loading screen?

I have recently launched a new app that replaces an older app and I want to grandfather all old app users to the new app for free. I no longer have access to the source code of the old app and it is not authenticating users so there is no way to turn off access to users to get them to switch to the new app. Would I be able to publish a new version of the "old" app with just a static screen that would say something along the lines of "this app is no longer available, download app xyz for free access to the new material" or would Apple not allow that as technically this static screen doesn't do anything?

I have a question regarding app publishing. I am a developer creating applications for my clients. I want to publish an application I developed for a client using my own Apple Developer account. The content of the application consists of data provided by my client. Can I do this? Are there any examples of applications that have been published under similar circumstances?

Hi everyone, can someone tell me what kind of documents mentioned below do I need to provide? I submitted everything I could: design documents, our workspace on bitbucket, trello but still got rejected.

Hello, Apple community and support team. We would like to get your input on a recent rejection we got in our latest app submission. The app uses public APIs in an unapproved manner, which does not comply with guideline 2.5.1. Specifically, your app utilizes the NEVPNManager APIs for non-approved uses. Since there is no accurate way of predicting how an API may be modified and what effects those modifications may have, unapproved uses of public APIs in apps is not allowed. We are currently uncertain about the specific ways in which the NEVPNManager APIs are being misused in our app, as we have diligently followed the instructions documented on Apple’s website. Our app uses a Packet Tunnel Provider and configures it to use a local proxy server for reducing network traffic, especially for video streaming services. We initially don't send any of the received traffic to a VPN server and instead, traffic is only handled by the Proxy Server. We are committed to ensuring our app complies with all guidelines and appreciate your assistance in resolving this matter. Your guidance will be invaluable in helping us make the necessary adjustments. Thank you for your support.

Recently, our app was rejected by App Store, reason is : "The app still uses public APIs in an unapproved manner, which does not comply with guideline 2.5.1. Specifically, your app is using NEVPNManager APIs without using VPN APIs. Since there is no accurate way of predicting how an API may be modified and what effects those modifications may have, unapproved uses of public APIs in apps is not allowed." Our app uses VPN to connect our company-internal network only. so what should we do next? i need update some options with Xcode or apply for some kinds of permission

In our application, we have a 'sign up' link that directs users to a URL (which is shared by our website) where they can create an account on our platform. Users can create an account either through traditional sign-up methods (providing their name, email, phone number, and password) or by using social sign-up options such as LinkedIn or Google. Our application was rejected after we introduced the Google and LinkedIn social sign-up options. As a temporary measure, we have removed the link to the sign-up page from the application. Currently, users can only sign in to the app if they already have an existing account using email and password. From guideline 4.8 we have: 4.8 Login Services Apps that use a third-party or social login service … must also offer as an equivalent option another login service with the following features: the login service limits data collection to the user’s name and email address; the login service allows users to keep their email address private as part of setting up their account; and the login service does not collect interactions with your app for advertising purposes without consent. This guideline clearly specifies that the three listed features are only applicable to the equivalent (non social sign-up) option, they are not relevant to the third party login options. Furthermore, the two third party login options which we have added to the page in question (Google and Facebook) are listed as third-party or social login service options in guideline 4.8, so these are not options which are unfamiliar to Apple and are clearly separated from what the guideline defines as an equivalent option, thereby clarifying that they are not needed to be reviewed for adherence to the three features listed. I have communicated with the review team multiple times, seeking more details or a resolution to the issue, but the responses have been vague, pointing us to guideline 4.8 without providing detail on what aspect we are not adhering to. What would be the best approach to resolve this issue and reinstate the sign-up functionality in the app? Based on my research, it seems that adding Apple Sign In as a third social sign-in option might be a solution, but this sign-up method would be out of place on the website and it does not feel like Apple will strong-arm developers in such a way.

Hello everyone! By the guidelines we have to use IAP because actual service happens in the application itself: it is an app for scheduling actions. The business problem is that IAP does not allow the refund functionality which is important in-app in case the actual scheduled action will not happen. Is there a way to use Stripe still exactly cos we need to implement refunds in the app?

Hello I have a question about my web app release. I have built a web app including Apple Music MusicKitJS. Now I would like to release it. Do I need to confirm this with Apple? If yes, what can I do next?

Guideline 2.1 - Performance - App Completeness Your app did not load its contents and the activity indicator spun indefinitely when we tapped "Don't Allow" when prompted for permission to use current location. If location information is required, it is necessary to display a notification or alert indicating this requirement. Next Steps To resolve this issue, please revise your app to either enable functionality when a user opts out of providing location information or include an alert that this information is required. Resources For more information on Location Services, please review the section, "Determining Whether Location Services are Available" in the Location and Maps Programming Guide. For a networking overview, review About Networking. Guideline 2.1 - Information Needed We’re looking forward to reviewing your app, but we were unable to sign in with the following demo account credentials you provided in App Store Connect: User name: 8015965494 Password: 8015965494 To avoid delays in App Review, it is essential to provide the App Review team with access to your app's full features and functionality with every submission. Next Steps Please provide the username and password for a valid demo account on the App Review page of App Store Connect that provides full access to your app's features and functionality or include a demonstration mode that shows all of the features and functionality available in your app. Note that we cannot use a demo video showing your app in use to continue the review. Resources Watch a video from App Review with tips for preventing common rejections. Learn how to share information with App Review when submitting your app for review. Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage The app encourages or directs users to allow the app to access the location. Specifically, the app directs the user to grant permission in the following way(s): A custom message appears before the permission request, and to proceed users press a "Configure Location Access" button. Use words like "Continue" or "Next" on the button instead. Permission requests give users control of their personal information. It is important to respect their decision about how their data is used. Next Steps To resolve this issue, please revise the permission request process in the app to not display messages before the permission request with inappropriate words on buttons. If necessary, you may provide more information about why you are requesting permission before the request appears. If the user is trying to use a feature in the app that won't function without access to the location, you may include a notification to inform the user and provide a link to the Settings app.

app在审核人员那里登录不成功，但我测试是成功的，请问应该如何去做

Good Afternoon Apple .... I am developing a takeway app, which allows business owners to register their takeway, then allow customers and staff, and allow their staff access to the account they have created. I would use IAP subscription to allow tiered monthly access, ie $10 for 1 user, $20 for 2, etc. I have a server back-end which would be used to record the IAP subscription to allow the extra staff to log in via web or android. The complication comes in with the case of a 'serial entrepreneur'. I use the model of '1 company, 1 email'. so, my entrepreneur registers 2 accounts, for 2 separate take-aways. Company A has 1 user, company B has 2 users. In this scenario, I would want the entrepreneur to log into company A, purchase a 1-user mobthly subscription, switch to company B, and then purchase a 2-user supscription. the subscriptions would therefore be separate. The registration would use my own login mechanism, so the entrepreneur would be using the same apple Id on the same iPhone. i wish to avoid the scenario 'entrepreneur registers company B, purchases a 2-user monthly subscription, then registers company A, and automatically gets another 2 users. Whilst I could likely code this to work, my questino is whether the app store would accept it ? the guidelines don't really seem to elaborate on this scenario. if necessary i could make the entrepreneur purchas a 3-user monthly subscription that is shared across his 2 logins, but I would like to avoid this if possible. regards, Phil

A regular update to our game have been in review for almost two weeks. These updates normally take a day or less. Is this a general problem or just our game? We have iOS users complaining about the lack of new content. They are comparing to their friends on other platforms. Other platforms now have almost 3 weeks worth of updates that iOS have not gotten. iOS users are slowly losing faith and there is nothing we can do. When can we expect for review times to return to normal?

We use CoreNFC feature for few clients. For clients who don't use NFC or add NFC related permission, the app is rejected on App Store. is there a way to make CoreNFC optional in the library and not lead to app store rejection for parent app who do not use this feature?

I am using an older Adobe product (Director) with extensions that my programmer created to allow us to continue creating IPA's, successfully! Well, for the most part ;-) We added a new app Product (and ID), got many successful Transporter uploads of builds, had all requirement ready. But when we click on Add for Review, we are told that we need a 1024x1024 PNG icon image for marketing. We have tried many different ways now to include such an image. However, we still get that error! BUT...Transporter tells us they were successful uploads and TestFlight is showing the build as Ready to Submit! Anyone else stuck at this juncture?