Hi,Our company integrates third party sign ins (e.g. Facebook) so we have added support for Sign in with Apple as well. However, when testing emails sent from our registered domains (verified on developer.apple.com) the emails are bouncing with the error code 550 5.1.1 bad mailbox name. Our domain is verified and our emails are sent using SendGrid from those domains.Do you have a timeline on when 3rd party email services will be supported? If it's after the public release of iOS 13, can we get confirmation on whether or not the next version of our app must support Sign in with Apple to be approved?Thanks,Tony
Search results for
5.1.1
395 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Having the same issue on SDK42. { name: APPNAME, version: 0.0.1, description: , author: , private: true, main: node_modules/expo/AppEntry.js, scripts: { start: expo r -c, eject: expo eject, android: expo start --android, ios: expo start --ios, test: jest }, dependencies: { @bugsnag/expo: 6.5.1, @expo/vector-icons: ^12.0.0, @react-native-community/slider: 3.0.3, @react-navigation/bottom-tabs: ^5.11.2, @react-navigation/material-top-tabs: 5.3.17, @react-navigation/native: ^5.8.10, @react-navigation/stack: ^5.12.8, crypto-js: ^4.0.0, expo: ^42.0.0, expo-ads-admob: ~10.1.2, expo-av: ~9.2.3, expo-blur: ~9.0.3, expo-contacts: ~9.2.5, expo-device: ~3.3.0, expo-facebook: ~11.3.1, expo-file-system: ~11.1.3, expo-firebase-analytics: ~4.1.0, expo-firebase-core: ~3.1.0, expo-firebase-recaptcha: ^1.3.0, expo-font: ~9.2.1, expo-image-manipulator: ~9.2.2, expo-image-picker: ~10.2.2, expo-keep-awake: ~9.2.0, expo-linking: ~2.3.1, expo-location: ~12.1.2, expo-network: ~3.2.0, expo-permissions: ~12.1.1, expo-secure-store: ~10.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
Hi guys,In order to use CloudKit methods like fetchUserRecordID the end user has to enable Look Me Up feature. But recently Apple App review board told us that asking the user to enable Look Me Up does not comply with the App Store Review Guidelines. 5.1.1, below.What is App Store compliant way to use CloudKit?Legal - 5.1.1The app requires users to enable Look Me Up access in iCloud in order to access non account-based features. Apps cannot require personal information prior to allowing access to app content and features that are not associated specifically to the user.Thanks
Ours is a video camera app. Our app displays the following prompt in Microphone Usage permission (Privacy - Microphone Usage Description):The app needs Microphone Access to record Audio But now Apple seems to be rejecting it. Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage We noticed that your app requests the user’s consent to access their microphone but does not clarify the use of the microphone in the applicable purpose string. Wondering what is not obvious here. A video recorder app needs microphone access to record audio, nothing more, nothing less! How do I fix it? It has been 8 years now and no such concern was raised before.
Topic:
App Store Distribution & Marketing
SubTopic:
App Store Connect
Tags:
App Review
App Store Connect
Hello all, I have an app on app store but when I am trying to submit a new version , itunes connect doesnt find the new build. I archived the build from xcode 6.4 (6E35b) and uploaded to itunes connect . In the prerelease section I can see my new builds but when I want to select the build for submit for review it only says Submit your builds using Xcode 5.1.1 or later, or Application Loader 3.0 or later.I also tried with Application Loader and same problem.It worked in the past, I already updated my app several times, for some reason it stopped working now, maybe the new itunes connect is the problem or maybe I am doing something wrong.Anyone faced this issue ?
Hi, My app was rejected by IOS, based on Guideline 5.1.1: we still find the permission request for camera and photos is not sufficient. To resolve this issue, it would be appropriate to revise these and ensure that they sufficiently explain why the app needs this access. It was my 2nd time already, I am frustrated. I asked IOS to give suggestion and it refuses. Can anyone help me if I modified my message as below: AppName would like to access your Camera. Allow AppName to take your photo as profile picture. And this photo will be used in-app messaging only. AppName would like to access your Photos Library. Allow AppName to capture image from your Photo Library. This image will used as your profile picture and for in-app messaging only. Thanks your help in advance
Hi, My app was rejected by IOS, based on Guideline 5.1.1: we still find the permission request for camera and photos is not sufficient. To resolve this issue, it would be appropriate to revise these and ensure that they sufficiently explain why the app needs this access. It was my 2nd time already, I am frustrated. I asked IOS to give suggestion and it refuses. Can anyone help me if I modified my message as below: AppName would like to access your Camera Allow AppName to take your photo as profile picture. And this photo will be used in-app messaging only. AppName would like to access your Photos Library Allow AppName to capture image from your Photo Library. This image will used as your profile picture and for in-app messaging only. Thanks your help in advance
Morning all, Hoping for a little technical advice here, got an iOS app to test... think I've code signed it correctly using an enterprise Dev account which my team has added me too. I seem to be able to install the app on a simulator and as soon as IOS driver opens the app is closes... I found this guide online http://dentedghost.blogspot.co.uk/2015/06/appium-testers-perspective-for-ios.html?m=1 and followed it all the way through to Xcode 5.1.1 part, however due to my version of macOS I cannot complete. I have a call with developers today, can anyone help me out with what exactly I should ask them for? A Dev build of the app?? Spent literally all of yesterday on this :( Thanks Arjun
We published an app for iOS which accidentally stores a ton of photos in Data & Documents. The app is live on the App Store, but currently the only way for a user to delete this bloat is to uninstall and re-install the app. Updating does not delete it. We fixed the bug, and put in a notice on the App Store page, but we'd rather take care of this on our end. The app was developed using Unreal Engine 5.1.1. The bloat is caused by Apple ARKit having had the should_write_camera_image_per_frame turned on (see https://docs.unrealengine.com/5.0/en-US/PythonAPI/class/AppleARKitSettings.html). The images are saved to Container/Documents/CameraImages. How can we make it so the next version we push to App Store will delete the contents of this folder upon launch?
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
Hi All,I recieved below feedback on my app.. I worked with a developer who cannot work right now and I need someone to help me with the feedback.. it is really small issues but because I don't have enough knowledge to fix in Xcode..Hello,Thank you for providing this information.Regarding 5.1.1, when collecting information from the user, that information needs to have a direct benefit to the user and contribute to your apps core functionality. Apps that request information that do not provide a direct benefit to the user when signing up are not compliant with the App Store Review Guidelines.Regarding 4.0, apps should be optimized to support the device screen size or resolution it is run on. Your app displayed text and buttons overlaid onto each other. To resolve this issue, it would be appropriate to revise your app.
I received the mail below. Starting June 30, 2022, apps submitted to the App Store that support account creation must also include an option to initiate account deletion. We noticed this app may support account creation. If it already offers account deletion or you’re working to implement it, we appreciate your efforts to follow the App Store Review Guidelines. Apps submitted after June 30 that do not comply with the account deletion requirements in guideline 5.1.1(v) will not pass review. https://appleid.apple.com/auth/revoke However, the revoke api is not working properly. Even if you throw an incorrect key value, 200 is always returned. Is the API working properly? What should I do?
Hi, we have built an App which aprroval has been rejected because we ask to enter some registration personal data that is neccesary for some material gathering during a social event. There is a data gathering agreement screen where the users accept that data gathering. It seems this is not valid for Apple because they say we break 5.1.1 policy about collecting non essential data for the core functionality... we are considering to just require the user to enter his email in order to log in and we would supply a link to an external registration web page so that the users register themselves in that website, outside the App. Is it possible to require to be registered in an external website to be able to use an App? would that be allowed by Apple policies? Has anybody any similar experience with this kind of issue? Thank you very much!
Hello, I have been stumped on this issue for a week and am looking for guidance on how to resolve it. I am aware of Guideline 5.1.1 Legal: Privacy - Data Collection and Storage and have read through it. The core functionality of our app is a Message Chatbot. This is the only feature we have, and we require user registration to limit the number of messages that can be sent on the free tier. However, despite explaining why we need user registration and pointing to a number of very similar apps that have the exact same registration system, we are not able to get approval from the App Reviewers. Their message is: To resolve this issue, please revise the app to let users freely access the app's features that are not account-based. The problem is that we do not have any other features in our app, so we are stuck. I was wondering if anyone else had similar issues and what they did to fix it? Thank you!
Hello all,I'm using SDK 8.0 and Swift, and my app compiles fine, but when its being sent for submission in iTunes Connect, I get a red-warning saying Apps and app updates submitted to the App Store must be built with Xcode 5.1.1 or later, and iOS 7 SDK.This is obviously a problem, because if I revert Xcodes SDK to 7.0, Xcode refuses to compile it saying iOS targets using Swift cannot be built against an SDK older than 8.0, but the effective SDK is 7.1. I should mention that this is an update to an existing application, not a new one, and I am using Xcode 6.4, not Xcode 7 (nor is it installed on my machine). I am, however, on El Capitan.Has anyone else run into this loop? Any fixes in the pipeline?Thankyou!