We are trying to publish a peer to peer sharing app. Our T&C's require the users to be at least 18 years old since there is legality around the agreements between users. Apple keeps kicking this back and stating we should not ask them their age. How do we get around this? Here's what they keep referencing: Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage 5.1.1(v) Account Sign-In If your app doesn’t include significant account-based features, let people use it without a login. If your app supports account creation, you must also offer account deletion within the app. Apps may not require users to enter personal information to function, except when directly relevant to the core functionality of the app or required by law. If your core app functionality is not related to a specific social network (e.g. Facebook, WeChat, Weibo, Twitter, etc.), you must provide access without a login or via another mechanism. Pulling basic profile information, sharing to the social network, or inviting friends to use the app are not considered core app functionality. The app must also include a mechanism to revoke social network credentials and disable data access between the app and social network from within the app. An app may not store credentials or tokens to social networks off of the device and may only use such credentials or tokens to directly connect to the social network from the app itself while the app is in use. Issue Description The app requires users to provide personal information when registering that is not directly relevant to the app's core functionality. Apps should only require users to provide information that is necessary for the app to function. If information is useful for a non-essential feature, apps may request the information but make it optional. Examples of app concepts and inappropriate required information: A general shopping app that requires the user's marital status A rideshare app that requires the user's gender Next Steps Update the app to not require users to provide the following personal information: DoB Gender Resources Learn more about data collection and storage requirements in guideline 5.1.1. 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.

Hello, my app was rejected because deep linking doesn't work as expected according to the reviewer. I have reinstalled the app and tested it on the same device and iOS version as the reviewer, but everything still works fine for me. I also asked a few friends (three people) to test it, and they all confirmed that the deep linking works as intended. Have you ever experienced a similar issue before, or do you have any insight into why this might be happening? Thank you in advance.

I have my app already in live before the privacy manifest introduced. Now, I want to migrate from cocoapods to Swift Package Manager. Will this be considered like adding the third party SDKs as new ones or will it be considered existing ones? So far I have not received any emails from Apple regarding the privacy manifest. I do not want any issues with the privacy manifest.

In order to submit my new subscription for review I need to upload a screen. No matter what resolution image I upload it fails saying "Your file could'nt be save. Try again if the problem persists, contact us" I am using many different types of simulators (Iphone 15 - Iphone Xs) and physical devices to take a screenshot and nothing is accepted. I can see the error message being returned from apples API is "IMAGE_BAD_DIMENSIONS_SM_LESS_MIN" so assume its a resolution issue. I am following the current guidelines here: https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications

So in looking over the app review guidelines, where it reads, "They may not auto-launch or have other code run automatically at startup or login without consent" We currently present a popup to inform the user if they want to connect to our server. My question is, are we able to provide the user with a way to turn off this startup prompt (thus improving speed of app startup) It would be located within our apps own settings page, upon which the user would have the choice to turn off or leave on this startup prompt. Or would this go against apple's policy in any way?

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?

Hello, We recently encountered an issue with our app's submission to the App Store regarding missing permissions. Specifically, our app requires access to two categories called: NSPrivacyAccessedAPICategoryFileTimestamp and NSPrivacyAccessedAPICategoryUserDefaults for proper functionality. Although we've managed to resolve the immediate concern, it's important that we address this as soon as possible (to avoid any further complications with future app submissions). As I'm not entirely familiar with app development/coding, I'm reaching out to seek help with this. We also want to know if the issue we're experiencing is related to using pre-release software or our code? Any insights or help with this would be greatly appreciated. Thanks!

Apple rejected my app store submission (first submission of this app) with the following comment: Issue Description: The app exhibited one or more bugs that would negatively impact App Store users. Bug description: The app opens to a black display Steps to reproduce bug: Launch app. Review device details: - Device type: iPhone 13 mini - OS version: iOS 17.4.1 Next Steps: Test the app on supported devices to identify and resolve bugs and stability issues before submitting for review. No other details given on specific scenarios. No logs provided. We asked for more info but they refused to help any further. I just so happen to have that exact device (iPhone 13 mini), so I updated it to the iOS version that was giving problems. But no matter what I do, I cannot replicate this bug. I tried via TestFlight and via Xcode, I tried deleting and reinstalling the app, and I tried restarting my phone between installs. I tried launching the app while on airplane mode. I never got this "app opens to a black display" issue. What else can I try to replicate this bug? The app is built with Unity 2021.3.19f1.

Please can someone help out here. I have been arguing back and forth with the app review team regarding background location for my app and i guess i am not understanding something. I have a marketplace app where users can buy goods that we ship to them after. My drivers have another different app that is the admin app where if you are a driver, and ONLY a driver (you can be an employee, supplier, and seller) you will be asked to agree to provide your location permission as "always on" because i need to be able to track my packages en route to the customer location. They say they need a video and i provided this one that shows the interface for the driver who is about to deliver the package. here is the link: https://youtu.be/iLbwncBUHy8 Any help on how to reply or what they want? below is their identical reply for the 4th time now: ================================================= Hello, The issues we previously identified still need your attention. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Review Environment Submission ID: Review date: Version reviewed: Guideline 2.5.4 - Performance - Software Requirements The app declares support for location in the UIBackgroundModes key in your Info.plist file but we are unable to locate any features that require persistent location. Apps that declare support for location in the UIBackgroundModes key in your Info.plist file must have features that require persistent location. Next Steps If the app has a feature that requires persistent location, reply to this message and let us know how to locate this feature. Please provide a demo video that demonstrates the persistent location in use on an iOS device. Resources Learn more about software requirements in guideline 2.5.4. Review documentation on Starting the Significant-Change Location Service and Monitoring Geographical Regions. 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. ============================================== Thanks for your help.

App: "Nappkin" Apple ID: 639242085 Hi, We are getting several "Missing API declaration" warnings (see below) when submitting our iOS app to the AppStore. Our app doesn't not use the mentioned api's but apparently one or more of the libraries we use do. We have included a privacy manifest that states this fact (included below). Why are we still getting these warnings/errors when we have included a privacy manifest? If each framework used must have a manifest can you tell me which frameworks are in error? We have no influence on the contents of the frameworks used in our apps. How can we comply if a framework we use does not have a required manifest and is unable or unwilling to include it? Our app is a point-of-sale app used by 100's of professionals. We have been in the AppStore for more than 10 years. Our app is fully dependend on several frameworks and not being able to update our app will mean we have to close our business. Thanks! Willem Bison = Privacy manifest ==== <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>NSPrivacyAccessedAPITypes</key> <array> <dict> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategoryDiskSpace</string> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>Our app does not use this api directly but (apparently) an included framework does</string> </array> </dict> <dict> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategorySystemBootTime</string> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>Our app does not use this api directly but (apparently) an included framework does</string> </array> </dict> <dict> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>NSUserDefault is used to store and retrieve several user preferences</string> </array> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategoryUserDefaults</string> </dict> <dict> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>Our app does not use this api directly but (apparently) an included framework does</string> </array> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategoryFileTimestamp</string> </dict> </array> </dict> </plist> = Warnings ==== Hello, We noticed one or more issues with a recent submission for App Store review for the following app: Nappkin Version 179.0 Build 33854 Although submission for App Store review was successful, you may want to correct the following issues in your next submission for App Store review. Once you've corrected the issues, upload a new binary to App Store Connect. ITMS-91053: Missing API declaration - Your app’s code in the “Nappkin” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryFileTimestamp. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api. ITMS-91053: Missing API declaration - Your app’s code in the “Nappkin” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryDiskSpace. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api. ITMS-91053: Missing API declaration - Your app’s code in the “Nappkin” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategorySystemBootTime. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api. ITMS-91053: Missing API declaration - Your app’s code in the “Nappkin” file references one or more APIs that require reasons, including the following API categories: NSPrivacyAccessedAPICategoryUserDefaults. While no action is required at this time, starting May 1, 2024, when you upload a new app or app update, you must include a NSPrivacyAccessedAPITypes array in your app’s privacy manifest to provide approved reasons for these APIs used by your app’s code. For more details about this policy, including a list of required reason APIs and approved reasons for usage, visit: https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api. Apple Developer Relations ============

Hello Apple Developer Community, I am encountering an issue with my iOS app submission on the App Store Connect platform. After testing the app extensively on various devices, including iPhones and iPads using Xcode, the app appeared to be functioning correctly with all screens visible. However, upon submission, Apple rejected the app, citing that it launched a blank page specifically on the iPad Air (5th generation) running iOS version 17.4.1. I have thoroughly reviewed the app's code and conducted additional testing, but have been unable to replicate the issue on my end. I am reaching out to the community for assistance in troubleshooting and resolving this issue. Has anyone encountered a similar problem before, or does anyone have suggestions on how to address this issue effectively? Any insights or advice would be greatly appreciated. Thank you in advance for your help.

Hello everyone, I'm currently working on implementing a vaccine tracker and reminder feature for an application. As part of this feature, I plan to collect basic information about babies from their parents, such as name, gender, and date of birth, in order to create personalized profile cards and assist in tracking vaccinations. My question is regarding the gender field: Is it acceptable to ask for only 'male' or 'female' as options, or should I include other gender options as well to ensure inclusivity? Additionally, considering that I'll be asking for gender and date of birth, I'm concerned about potential rejection of the app build by Apple. Can anyone provide insight into whether this could be an issue? Thank you for your help and guidance!

I have a customer who wants to protect the REST API of their app with a private certificate. They would then distribute the client certificate to the authorized users. Their app would not work unless the client certificate is already installed on the user's phone before they run the app. I have never done this before. Is it possible to install a client certificate on an iPhone without running an app, for example if it were sent in an email message? And if it is possible, is App Review going to let such an app into the app store? Thanks, Frank

We have a food delivery app. Now we want to add a prize competition. After every three successful orders, an entry will be created for the users. User can have unlimited entries. Now I am not sure if these requirements comply with AppStore especially No purchase necessary .

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.... I have faced multiple rejections for my app due to the same issue. However, the Apple reviewer has not provided any specific information about where the issue lies, making it difficult for me to address it. In the subsequent steps, I was instructed to thoroughly review the app store review guidelines and ensure compliance with them, which I have done. I have also reached out to the app review team but have not received a response yet. It is frustrating that the email does not mention the exact content that is being considered as copied. It feels like a generic message, and I am unsure about the next course of action. If anyone has been in a similar situation or has insights into what might be happening, I would greatly appreciate your input. Thank you.

Hi, I developped an app which is an alcohol level calculator (cf image for few screens). I did lots of modification to the app is accepted, but none works. I also asked to the verification team, but they can't help me more. However similar app already exists like https://apps.apple.com/fr/app/alcootel-by-maaf/id6444157056 or https://apps.apple.com/fr/app/%C3%A9thylom%C3%A8tre/id688242393. I even copy the description of the first app. So, could you help me about what I can change in order to the app is validated, or do the new rules make my app "out of the Apple laws". Thank you

Your app or its metadata does not appear to include complete and final content. Specifically, your app description needs to describe in-app features and functionality. App Store users expect the apps they download to be ready for public use. Apps on the store shouldn't include placeholder or incomplete content or information. Next Steps To resolve this issue, please revise your app and metadata so that all of its content is complete and final. For example: Your app binary or metadata should not include "lorem ipsum" text. App metadata should not include placeholder screenshots, such as "screenshot coming soon." Provide an engaging app description that highlights the features and functionality of your app. I received this mail, I made required changes still getting this

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.... For the past four years, my app has been live on the Play Store and is also accessible on several other platforms. Despite this, my attempts to publish it on the App Store have been consistently rejected citing Guideline 4.1 - Design - Copycats. Apple has not specified the exact proof of rights they are looking for. To address this, I have recorded my personal Google Play Developer Console account to showcase that I possess all the required rights to manage the app on Google Play. I am seeking advice on the best course of action to resolve this issue.

I'm extremely frustrated with Apple's unfair app review process. To make a long story short, for every app I've ever submitted, Apple has made false accusations about problems with my apps. Some of their feedback has absolutely been legitimate and correct, which I appreciate, but I would say about 50% of all "feedback" I've ever received has turned out to be objectively wrong. In some cases, the App Review team's gaslighting has been so strong that I have had to submit screenshots of code as proof that their accusations were completely wrong, after which they have had to accept the app. In one instance, they have claimed that one of my apps would not be allowed on the App Store at all, and when I link to multiple other apps that works EXACTLY the same way, the App Review team love to point out that you are not allowed to compare yourself to other apps. To be clear, I'm an indie developer and I'm not even comparing myself to apps from large corporations or any popular apps at all (since it's well known they get the VIP treatment), all apps I have compared myself to are from small, unknown indie developers such as myself - so I'm only comparing myself to developers in the same category as me. Telling developers that they are not allowed to compare themselves to other developers is VERY ethically problematic, imagine doing that to minorities in real life. I'm a minority in multiple ways, and I'm very worried about the ethics and moral at the App Review team. When I ask why they reject my app, but approve many apps that were recently released that works EXACTLY the same way as my app, I either get no reply at all or they tell me that I can't compare myself to others. Submitting appeals to the App Review Board doesn't help either. To be completely transparent with you, it has been very hard and draining on my mental health to have this invisible wall consisting of gaslighting that the App Review team has set up for me. It just doesn't make sense... The app review process is unfair, inconsistent and problematic, and it should be a serious eyebrow-raiser when Apple's App Review team can't explain why some small indie developers get approved easily while others get rejected. Especially since it seems like the pattern is that those who get rejected are humans in various kinds of minorities, as evidences by some other threads on this topic.