Hello, I believe I'm experiecing a bug within the AppStoreConnect dev console. When I try to submit a new version of my game for review I recieve an error message stating The items below are required to start the review process: There are still leaderboard image uploads in progress. One might think that this problem should have an obvious solution: wait for the leaderboard images to load and try again. Unfortunately this is impossible, because all images are already loaded. They are also being successfully displayed in the console interface and even in my game itself. I tried to remove all images, but that didn't help. I've also noticed that leaderboard management interface in the console was updated in the past month or two. I think that might be somehow related to the problem (something from old UI got cached and now isn't affect by new UI). I've also filed a request (102270407515) to the Apple Support, but didn't get any answer (aside from the request is registered). Is there any chance I get an answer from Apple Support here on the forum?

New versions of AppKit/Mac Catalyst apps that use Google's Sign In framework are being rejected by App Store Review for the past two weeks. Reason shared was: The user is taken to the default web browser to sign in or register for an account, which provides a poor user experience. And also citing: Data Collection & Storage guidelines -> https://developer.apple.com/app-store/review/guidelines/#data-collection-and-storage Opening macOS' default web browser has been a native behavior of Mac apps when using SFSafariViewController with ASWebAuthenticationSession, which is required, since iOS 13, for securely/privately logging in users. As far as I could investigate, there hasn't been any updates to the guidelines that would indicate any required changes to developers in regards to how login works for macOS apps. Are there any steps developers need to take to get updates approved while still providing users with Google's Sign in? As reference, there is an on-going discussion on GoogleSignIn repo about this issue affecting multiple developers and apps: https://github.com/google/GoogleSignIn-iOS/issues/388

Trabalho numa empresa que presta serviço implementando, mantendo e publicando sistemas para prefeituras. Fizemos agora um app para uma prefeitura mas na hora de publicar, a Apple está rejeitando pois diz que não podemos publicar em nome de outra empresa. No primeiro envio, rejeitaram com: Guideline 4.1 - Design - Copycats The app or its metadata appears to contain potentially misleading content. Specifically, the app includes content that resembles Sistema da Prefeitura without the necessary authorization. Next Steps Please demonstrate your relationship with any third-party brand owners represented in the app. Pegamos com a prefeitura um documento assinado digitalmente informando que somos os responsáveis pelos sistemas deles, autorizando tudo etc... Fizemos um novo envio para revisão. Porém, agora foi rejeitado com: Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage The app must be published under a seller and company name that is associated with the organization or company providing the services. In this case, the app must be published under a seller name and company name that reflects the MUNICÍPIO DE *** name. The guideline 5.1.1(ix) requirements give users confidence that apps operating in highly regulated fields or that require sensitive user information are qualified to provide these services and will responsibly manage their data. Next Steps To resolve this issue, it would be appropriate to take the following steps: The app must be published under a seller name and company name that reflects the MUNICÍPIO DE *** name. If you have developed this app on behalf of a client, you may resubmit the app through their account, if they have one. You may also request an update to the company name on your account by having the Account Holder edit the account information. Please note that you cannot resolve this issue with documentation showing permission to publish this app on behalf of the content owner or institution. Ou seja, agora estão rejeitando se contradizendo no que pediram previamente. A prefeitura não possui conta de desenvolvedor na Apple. Não tem como eles publicarem isso. Alguém já passou por isso? Tem ideia do que podemos fazer? Desde já agradeço.

I am new to coding so pardon my naivety. I made a simple app for my company where customers can place orders and leave their names and phones numbers. Upon placing an order the app creates a collection in Google Firebase then generates an email with some HTML code. My app does not use any API's directly, and I believe I received the warning email solely because of the Firebase SDK like many others. I updated my app with what I believe to be proper "declaration of the data collected by my app or by third-party SDKs" according to https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_data_use_in_privacy_manifests - but I am wondering if I actually did it correctly! See Attached

Hello, I uploaded my app for review and the status is "waiting review", I have tried many things since March 28th, creating a new review, requesting support for feedback,... and nothing. Does anyone know what I should do to get feedback or a deadline for publishing my app? Thanks in advance Leonardo

Let's say I have an iOS app on the app store. Anyone can download and use it, but I would like to restrict the app from granting access to certain features to a select set of people I can personally vouch for. So, for example, to get access, the app send email to me, you have to convince me I know you, and if you do, I send you back some kind of token string which you can enter into the app. However, I'd like for that token to not be shareable, and to be locked to that device. Is there any kind of persistent ID associated with a device that I can use to tie the token I grant to that persistent ID? Or can someone suggest a way that once I trust a user, I can give them a token which will cannot be shared to anyone else? Also, does anyone know if restricting access to app features in this way is any kind of issue with regards to the app review process? The app itself is free, and there are no in-app purchases. I simply don't want certain features of the app (which end up sending push notifications) to get abused.

Hello Apple Developer Community, I am writing to request urgent support regarding the recent removal of our app, which has been available on the App Store for over a year serving a large user base. We were notified that our app violated Section 3.2(f) of the Apple Developer Program License Agreement, but we have not altered our operations recently and believe this to be a misunderstanding. We have attempted to reach out via email but have not received further details or the opportunity to rectify or discuss the alleged issue. Historically, developers are given a chance to resolve concerns before an app is removed, a courtesy we were unfortunately not extended. We seek clarity on the specific violations and an opportunity to address any issues to comply fully with Apple's guidelines. The removal has significantly impacted our users and our team, and we are committed to resolving this swiftly to restore service to our users. Thank you for your attention to this urgent matter. We look forward to your guidance and support. Below is the notification we received from Apple regarding the termination of our agreements: Apple has terminated the Apple Developer Program License Agreement and the Apple Developer Agreement with our company effective immediately. According to the notice, the reason provided for this action is an alleged violation of Section 3.2(f) of the ADP Agreement, which includes accusations of fraudulent conduct associated with our account. This has led to the immediate cessation of our status as an Apple developer and termination under both the ADP and Developer Agreements.

I find odd that the App Store Connect still requires 5.5" iPhone screenshots of the iPhone 8 Plus, given that this specific phone is no longer supported by the latest release: iOS 17. I am well aware that the iPhone SE still has a similar screen ratio, and that it is still being supported by iOS 17, but it doesn't have the same pixel requirements (1242 x 2208), which means that in order for my app to be even reviewed (which is an iOS 17+ exclusive), I'm gonna have to create images that will then be upscaled to the right dimensions. Am I missing something here, or is it Apple who missed this detail?

I added this file as Apple requested due to my app using UserDefaults, but it still complains when I upload it. This is the message: TMS-91053: Missing API declaration - Your app’s code in the “Production” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDefaults. And this is my file, what's wrong? <dict> <key>NSPrivacyAccessedAPITypes</key> <array> <dict> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategoryUserDefaults</string> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>CA92.1</string> </array> </dict> </array> </dict>

Hi everyone, I'm working on submitting my app to the App Store and need to capture screenshots for the 5.5-inch iPhone display size (iPhone 6 Plus, 7 Plus, and 8 Plus). Unfortunately, Xcode 17.4 doesn't offer simulators for these devices. I've searched Apple's support resources but haven't found any solutions. Would anyone have suggestions on how to generate the required 5.5-inch screenshots for App Store submission? Thanks in advance for your help!

We have recently rolled out a one-time-password only log in system for our app. Access to our app is by invite only and users are required to register outside of the app to set up their account (it is an app for events & conferences). The majority of users have requested this login system as it is more secure and easier than a traditional password. I submitted the app for review, but it was rejected as the Apple tester required the email access code that was sent when they entered the tester email address we have in the app description. Does anyone have any advice on how we can remedy this so that our app does not keep getting rejected for this reason? Thanks

I submitted my app to the App Store, but it keeps getting rejected based on the following issue: Guideline 5.1.2(i) - Legal - Privacy - Data Use and Sharing The primary purpose of the app is to encourage users to perform digital tasks in exchange for compensation, watch ads and/or perform other marketing-oriented tasks, which is not appropriate. Next Steps Review the app concept and incorporate different content and features. Resources Learn more about these requirements in guideline 5.1.2. Support Reply to this message in your preferred language if you need assistance. If you need additional support, use the Contact Us module. Consult with fellow developers and Apple engineers on the Apple Developer Forums. Help improve the review process or identify a need for clarity in our policies by suggesting guideline changes. I am struggling to understand why my app is continuously rejected for this reason. Could you please provide some guidance? Thank you very much! Screenshots for reference: https://ibb.co/f4cYtc7 https://ibb.co/28Wfwxf

My app is only available in some regions. During one of the review versions, the reviewer asked to remove accessibility from one of the countries or provide documents that allow to conduct activities in this country. At that time, there was no such document and I removed the availability in this country. Now - I have a document that confirms that I can conduct activities in this country. Availability is a separate section and is not related to versioning. How and where do I request app availability in a specific country?

Hello! In our applications we consume several 3rd party libraries that use one or more API from this list - https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api?language=objc. These XCFrameworks contain static frameworks (a framework with a statically linked binary inside), so after linking, the machine code inside these frameworks becomes either a part of the app's executable or a part of a dynamic library. We integrate these libraries using Swift Package Manager's ".binaryTarget" feature and have been having trouble understanding where should the privacy manifest be located in the final app, so that we can pass the App Store review process. It seems that with SPM the privacy manifest (PrivacyInfo.xcprivacy file) is lost - https://github.com/apple/swift-package-manager/issues/7317 If the static framework is linked as a part of the app's executable, does that mean we have to manually merge the app's privacy manifest with that of a 3rd party static library? If the static framework is linked as a part of a dynamic library within the app, where should the privacy manifest be located? And what should happen if there are multiple static frameworks each with a privacy manifest being linked into this dynamic library? Thank you very much!

When I try to add my app version for review I get the following error: I contacted support twice (13 days ago) and no one has fixed the issue yet. Also 5 months ago you had the same issue with Xcode 15.0.1 how is it that you don't see this coming when you release a new version?? Unbelievable... I understand that is hard for a small 2.6 trillion corporation to find the resources to address this issue but I need to submit my app update ASAP

Hello. I've tried a dozen times to upload my app, each time getting a response that the app was rejected due to 4.1 copycats. The most recent response: Guideline 4.1 - Design - Copycats. This app or its metadata appears to be misrepresenting itself as another popular app or game already available on the App Store, from a developer's website or distribution source, or from a third-party platform. On my requests to clarify what exactly was identified as copycats, no specifics were given to me. Because of this I conclude that it is not about some stock images or sound assets, but that it is specifically about my application (name and icon). I am the solo developer of the app and it has been available for 5 years on Google Play. No other platforms have my app on them, only Google Play. Since Apple has not provided me with specifics about what they need as proof of rights to the app, I have screen recorded my personal Google Play Developer Console account, which proves that I have all the necessary rights to manage my app on Google Play. To this I received the following response: Guideline 4.1 - Design - Copycats This app or its metadata appears to be misrepresenting itself as another popular app or game already available on the App Store, from a developer's website or distribution source, or from a third-party platform. Apps should be unique and should not attempt to deceive users into thinking they are downloading something they are not. We did not receive sufficient documentation. Please help me understand what documentation they are talking about if I am a solo developer with every right to my own app. Do they want me to register a company and register the naming rights to my app?

Hey, I’m updating all of my apps to target the new versions of all the plugins we use, and for some reason, I have a warning message : ITMS-91053: Missing API declaration - Your app’s code in the “*****” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryDiskSpace. ... ITMS-91053: Missing API declaration - Your app’s code in the “*****” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryFileTimestamp. ... Apple Developer Relations But in my Cordova config.xml, I have already added the <privacy-manifest> tag: <privacy-manifest> <key>NSPrivacyTracking</key> <false/> <key>NSPrivacyCollectedDataTypes</key> <array/> <key>NSPrivacyTrackingDomains</key> <array/> <key>NSPrivacyAccessedAPITypes</key> <array> <dict> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategoryDiskSpace</string> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>E174.1</string> </array> </dict> <dict> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategoryFileTimestamp</string> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>3B52.1</string> </array> </dict> </array> </privacy-manifest> I have already sent some applications to Apple, and there is no problem; they haven’t sent me back the ‘Missing API declaration’ error. So in conclusion, I don’t know what the problem is for three of my app’s pool. it’s been several days that I’ve been working on this issue. If you have a solution, please let me know. Best regards."