5.1.1

Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage To resolve this issue, it would be appropriate to take the following steps: If you are authorized to provide this service in the app, please provide evidence of your relationship with the institutions or organizations associated with the app. If you do not have authorization, the app needs to be published under a seller name and company name that reflects the app 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. Resources Learn how to transfer apps between accounts. Request a fee waiver for nonprofit organizations, accredited educational institutions, or government entities. 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 develop

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 th

Team, We are trying to publish new app (Under new brand label) for newly acquired company. app update is rejected for the reason: 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 institution name. Any suggestions??

I have add my domani and email address to Configure Sign in with Apple for Email Communication (https://developer.apple.com/account/resources/services/configure) and it pass SPF already but when it send from server that i setup is had Error Description : Permanament error. Please do not try again, according to the information returned by the other party to confirm the specific cause of the error. Cause:550 5.1.1 : unauthorized sender a mail service is on Alibaba Cloud the email that i want to sending to is ending with @privaterelay.appleid.com it that have any solve problem or i missing any thing else ?

I’m building an iOS app that collects user PII (emails, names) and stores it in my backend database. I already use HTTPS for data transfer, but I’m unsure if Apple requires server-side encryption for stored data. For example: If a user’s email is stored in plain text on my server (but transmitted securely via HTTPS), will this violate App Store guidelines? Does Apple explicitly mandate encryption-at-rest for PII, or is it just a recommendation? Are there exceptions for non-sensitive data like usernames? I checked App Store Review Guidelines §5.1.1, which says data must be stored securely, but it’s unclear if this requires encryption. Context: The app targets U.S. users (no GDPR/CCPA concerns). No financial/health data is involved. Is plain-text server storage of emails/names acceptable, or will this risk rejection? Thanks for any clarity!

Hi everyone, I recently received a Pending Termination Notice for my very first iOS application, and I’m extremely worried about losing my developer account. My app submission was initially rejected due to: The app may contain hidden features, functionality, or content. Specifically, the app may contain financial transactions without the necessary authorization. Apps that provide financial transactions without the necessary authorization do not comply with guidelines 3.2.2 and 5.1.1(ix). Users should never be misled about the apps they download. Attempting to hide features, functionality, or content in the app may lead to removal from the Apple Developer Program. I sent an appeal immediately, but after 13 days (March 14 – March 27), I received a Pending Termination Notice stating that my app violated section 3.2(f) of the Apple Developer Program License Agreement due to dishonest or fraudulent activity. I was shocked because my app is a simple Objective and Key Results (OKR) tracking application. Aft

Hi,My app is in production and was published with a deployment target set to 5.0 and with armv7 and armv7s architecture, 32bits compatible.Apple warned us by email by February 2015 that publishing binary-compatible 32 and 64 bits will be mandatory. Since we also updated Xcode 6.3.1.Today I want to publish an update of my app, but if I use the same configuration described above, I get a publication error : ”Missing 64 bits support. Beginning on February 1, 2015 new iOS apps submitted to the App Store must include 64 bits support and be built with the iOS 8 SDK”.To correct the error, I added the arm64 architecture like Apple recommends it. But I get a new publication error: “Apps that include arm64 architecture cannot have MinimumOSVersion set to less than 5.1.1”Therefore, I changed the deployment target to 5.1.1 but I still get once a new error: “This bundle » does not support one or more of the devices supported by the previous app version. Your app update must continue to support all device

Below is the response we received from app store reviewer -Legal - 5.1.1We noticed that your app uses Facebook login for authentication purposes but does not include account-based features offered by that site.In order to use Facebook for authentication, your app must include significant account-specific functionality from Facebook.Question :What account-specific functionality from Facebook should we implement to fulfill the requirement ?

I'm trying to figure out why my application keeps crashing and could use some help in understanding the crash report so I know where to look for the problem. Here's the report:Process: Adobe InDesign CC 2015 [1334]Path: /Applications/Adobe InDesign CC 2015/Adobe InDesign CC 2015.app/Contents/MacOS/Adobe InDesign CC 2015Identifier: com.adobe.InDesignVersion: 11.4.1.102 (11410)Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Adobe InDesign CC 2015 [1334]User ID: 2115166540Date/Time: 2016-11-07 08:52:14.392 -0700OS Version: Mac OS X 10.11.4 (15E65)Report Version: 11Anonymous UUID: E1C64908-5CE2-7A89-F534-5CF580D4B2C2Time Awake Since Boot: 6700 secondsSystem Integrity Protection: enabledCrashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_BAD_ACCESS (SIGSEGV)Exception Codes: KERN_INVALID_ADDRESS at 0x0000005b00000018Exception Note: EXC_CORPSE_NOTIFYVM Regions Near 0x5b00000018: mapped file 0000000151a5c000-000000015210f000 [ 6860K] r--/rwx SM=COW --> JS JIT generated code 000

Hi there!Any time I generate a certificate to use for iOS development or distribution, it shows me no root cert issue (This certificate has an invalid issuer) that I was unable to overcome. I've installed Apple WWDR CA which expires on 7th of February 2023, but I'm not sure if and how it's used when generating Requesting a Certificate from a CA via Keychain Access...Yes, if needed, I'm using Mac OS X 10.10.5 and xCode 5.1.1.Please help me if possible.Thank you,Yana

Hello. I examine App Store ReviewGuidelines - https://developer.apple.com/app-store/review/guidelines/ and subdivision item 5.1.1 Data Collection and Storage, item (vii) says that: (vii) SafariViewController must be used to visibly present information to users; the controller may not be hidden or obscured by other views or layers. Additionally, an app may not use SafariViewController to track users without their knowledge and consent. This rule applies only to SafariViewCntroller or to WKWebView too? I ask this because both have the same technology and used for the same things. Regards, Ihor.

We are currently developing a new iOS application, and we plan to use Sign in with Apple for user authentication. We have a few questions related to this. We understand that Sign in with Apple is compliant with OpenID Connect. However, in our service, the use cases for access_token and refresh_token are limited. Therefore, even if we do not use these tokens, is there a possibility that we will receive a rejection in the Apple Store Review process? Specifically, we are thinking of saving the user's identifier, which can be obtained at the time of authentication, on our server and using it to identify the user. ASAuthorizationAppleIDCredential According to Apple's guidelines (5.1.1 Data Collection and Storage), we need to invalidate the user's tokens when the account is deleted. Does this requirement apply even if the token has already expired? App Store Review Guidelines 5.1.1 Revoke tokens Thank you in advance for your help!

We are a development team that has developed an application for an oral and maxillofacial surgery clinic. The developer account from which the application is published is registered to a consulting firm that works with this clinic. We were denied publication due to the fact that the developer's account and its name did not reflect the essence of the application. We opened an individual entrepreneur with the same name as the name of the application, but as a legal entity we are not allowed to register, since it is an individual entrepreneur. Support responds to this question by asking us to register the developer's account as an individual entrepreneur and try to send it for verification, and only then will they give an answer based on the verification results. If we register as a regular individual entrepreneur, will the application be allowed for publication? Has anyone encountered this?

Good afternoon, I wanted to comment something to see if you can help me find a solution. The apple review team tells us the following “Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage We noticed that your app requires users to register with personal information to purchase in-app purchase products that are not account based” To use our applications you have to buy them but we want users to be able to try it for free for a few days before buying it. Therefore, to avoid that they can use it during the trial days and then uninstall and reinstall it we have put a register at the beginning. This way when the trial days are over they will only have the option to click on the Unlock button which will take them to the App Store to buy it. But I see that in Apple's Best practices it says: “Delay sign-in for as long as possible. People often abandon apps when they’re forced to sign in before they can do anything useful. To help avoid this situation, give people a chance to get a sense of what yo

I'm building an AR app for iOS using UE 5.1.1 (and Xcode 14). Using ARKit. When our build made it to Test Flight, we're not getting camera feed for the AR, and the app doesn't ask for permission to access camera. How do we fix this? Is this in Xcode or UE? Do we need to set something up also on App Store Connect / Profiles / etc ? Thanks!