5.1.1

I understand that a user can delete their own Passkey through Settings, but guideline 5.1.1(v) dictates apps that support account creation must let users initiate deletion of their account within the app. As Passkeys, and thus an account, can be generated from within the app - the requirement here means we need to be able to delete them from within the app too. This means programmatically - with validation to ensure we can only delete our own passkeys, and indeed ensuring that the user wants to delete it (with a modal). Also, with the ability to delete a passkey (and presumably their only way of accessing their account) outside of the app, it leads us with orphaned accounts. Accounts which exist on the server but the user cannot access. What is the best pattern here?

I am not part of the App Review team, but the only accepted way to use a customer service flow (like contacting the user support desk) for account deletion is if your app is used in a highly regulated industry. I was told by App Review that the fields given as examples in App Store Review Guideline 5.1.1(ix) - highly regulated fields (such as banking and financial services, healthcare, gambling, legal cannabis use, and air travel) - are the only fields that Apple considers to be highly regulated. As long as Apple considers insurance to be a financial service, I would think that your plans for account deletion would be acceptable. I'd email Apple directly to confirm just in case.

Update: I now think that this is due to a serious bug affecting users with an iPhone 6 Plus. Apparently many watch apps cannot be installed from that device running iOS 12.1 to an AW4 running watchOS 5.1.1. This is exactly the combination one of my users has, and I have another review mentioning it in the Netherlands, so I no longer think it is country specific.This is a serious issue that seems to be affecting many apps, such as Spotify, Shazam, Nike Run Club, PCalc and more: https://devandartist.com/posts/apps-not-installing-on-the-apple-watch-or-error-17If anyone from Apple monitors these forums then please take a look - this is a very serious problem for watch app developers.

I can no longer submit apps with Xcode 6.4 (6E35b), which is a GM, Appstore version, Xcode7 is not installed on my system. On submit for review i get Apps and app updates submitted to the App Store must be built with Xcode 5.1.1 or later, and iOS 7 SDK.Regardless of what apple says, this has never been a problem. It doesn't even make sense, as the build system of Xcode, and the command line tools for building should be contained. If this is not a regression, developers who want to prepare for future releases we now need3 iphones (current release, 8.4 train, 9.0 trains)2 osx devices (current release, el capitan train)2 apple watch devices (current release, watch os2)😐

When the app was submitted for the first time, apple has rejected the build with the following message:Per section 5.1.1 (ix) of the App Store Review Guidelines, apps that provide services or collect sensitive user information in highly-regulated fields, such as healthcare, should be submitted by a legal entity that provides these services, and not by an individual developer.Which refers to,(ix) Apps that provide services in highly-regulated fields (such as banking and financial services, healthcare, and air travel) or that require sensitive user information should be submitted by a legal entity that provides the services, and not by an individual developer.I remembered that I have selected the Air Travel previously, which is not the Category in the App Information section because I chose Lifestyle as the main category without choosing the secondary option.

I don't use Xcode, but I know how to set the min iOS level. Mine is set to 5.1.1. I think I was wrong about armv7 affecting the min OS. I'm still not sure where I thought I saw that minimum OS version now... it wasn't when uploading via Application Loader, anyway.I use these two charts to determine device compatibility:http://iossupportmatrix.com/http://28byteslater.com/ios-compatibility/My app is unreleased. If it was released, I could visit iTunes on a Touch 4 and see if they'll let me buy it. If the Touch 4 could run TestFlight I'd also be able to tell that way. You're right that anyone can buy an app via iTunes on their computer, but I don't think they can give it a 1-star review unless it actually installs on their device.

I am in the same situation! Built a news app and got rejected for the same reason. I am constantly explaining that it does not collect any user data and I get the same response in the resolution center every time: Hello, Thank you for your information. Regarding 5.1.1, we still found that your app provides services or requires sensitive user information related to the COVID-19 pandemic. To resolve this issue, your app must be published under a seller and company name of a recognized institution. For additional details, please refer to the update on the Apple Developer website about Ensuring the Credibility of Health & Safety Information. I am sure there is no real human reviewing these apps because I did not get any real reponse yet. It all looks very automated which makes it so frustrating

Update: I now think that this is due to a serious bug affecting users with an iPhone 6 Plus. Apparently many watch apps cannot be installed from that device running iOS 12.1 to an AW4 running watchOS 5.1.1. This is exactly the combination one of my users has, and I have another review mentioning it in the Netherlands, so I no longer think it was country specific. That was either a coincidence or the Swiss user who emailed didn't like to admit they also gave me a one star review!This is a serious issue that seems to be affecting many apps, such as Spotify, Shazam, Nike Run Club, PCalc and more: https://devandartist.com/posts/apps-not-installing-on-the-apple-watch-or-error-17If anyone from Apple monitors these forums then please take a look - this is a very serious problem for watch app developers.

You are, of course, aware of the privacy guidelines in the Review Guidelines, particularly section 5.1.1:(ii) If your app doesn’t include significant account-based features, let people use it without a log-in. 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.So your statement the app is unusable without an account may be another problem for you entirely.

I'm having the same problem. I'm building against the OS X 10.8 SDK (copied from the Xcode 5.1.1 bundle). My deployment target is also 10.8.The root of the problem seems to be that clang is automatically linking in the static library /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/arc/libarclite_macosx.a. As the linker error notes, this library references the symbol objc_readClassPair. However, that function wasn't added to libobjc until OS X 10.10. Hence, when linking against an earlier version, the symbol can't be found, and linking fails.I can get my project to link successfully by building against the 10.11 SDK. However, the resulting binary is still going to reference a function that isn't present on pre-10.10 systems. If _ARCLite__load is invoked on such a system, objc_readClassPair will be NULL, so presumably the app is going to crash. For that reason, this seems like a bug.

Not sure if you are asking about App Store policy or how to implement this authorization in your application? It would help if you could expand on your question in another comment.If this a question more on the policy of using Healthkit, there are several mentions of this in the App Store Guidlines.https://developer.apple.com/app-store/review/guidelines/Specifically, HealthKit should be used for health and fitness purposes and integrate with the Health app. from section 4.2.1. Also under the 5.1.1 section, which mentions about the Health Data Collection and Storage. If you need help implementing this, please see the class reference I've posted below.Here is the class reference for the HKHealthStore:https://developer.apple.com/library/ios/documentation/HealthKit/Reference/HKHealthStore_Class/index.html#//apple_ref/occ/cl/HKHealthStoreIf you want to create a fitness application without HealthKit, that is fine. However, if you intent on using HealthKit API, you will need to implement the authorization b

Feedback is critical, Critical to you or to the user ? 2 thoughts: In Europe you have to comply with GDPR regulation on privacy See guideline 5.1.1 (ii) Permission: Apps that collect user or usage data must secure user consent for the collection, even if such data is considered to be anonymous at the time of or immediately following collection. Paid functionality must not be dependent on or require a user to grant access to this data. Apps must also provide the customer with an easily accessible and understandable way to withdraw consent. Ensure your purpose strings clearly and completely describe your use of the data. Apps that collect data for a legitimate interest without consent by relying on the terms of the European Union’s General Data Protection Regulation (“GDPR”) or similar statute must comply with all terms of that law. Learn more about Requesting Permission (https://developer.apple.com/documentation/uikit/protecting_the_user_s_privacy/).

Here is the exact reason given for the rejection: We discovered one or more bugs in your app. Specifically, when attempting to login using the email address provided an error appears on the screen. Seeing an error on the screen in this case is expected because in a previous review, they deleted the account we provided them with. Now they cannot log in with that account anymore. Yes, we have already confirmed they have deleted the account. We did not explain to them not to delete their account, but maybe this is what we need to do to prevent them from testing this part of the app? Since there is not much documentation on how 5.1.1 is supposed to be tested by Apple reviewers, I don't really understand what we're expected to provide them (new credentials every time we submit in case they test to delete?). I'm just not really sure how other developers will be solving this problem. It seems like everyone will be in the same boat as soon as they add this functionality to their app by June 30. When we asked

You're right, I could not find a way to run this, whatever version of XCode I used. It is very unfortunate.Message is slightly different, but same problem:Module compiled with Swift 5.1 cannot be imported by the Swift 5.1.1 compiler: Swift_Playgrounds_Author_Template_for_Xcode_11.1/Template/SupportingContent/PlaygroundsFrameworks/iphonesimulator/PlaygroundSupport.framework/Modules/PlaygroundSupport.swiftmodule/x86_64-apple-ios-simulator.swiftmoduleProblem is PlaygroundSupport exec in PlaygroundSupport.frameworkThat's why we need urgently Swift birai API stability, promised a long time ago…See also:https://stackoverflow.com/questions/58654714/module-compiled-with-swift-5-1-cannot-be-imported-by-the-swift-5-1-2-compilerI fear the best option is to file a bug report.I finally found an XCode version that builds it: XCode 11.0 (specifically 11.0 GM2, build 11A420a). I could select the target LiveViewTest.app to launch in simulator.Readme states:The supporting content included with this template, including

It's simple: You could just generate a random unique identifier on the user's device, and use that instead of asking the user to create an account. Because you could do that, you need to have actual account-based features. More directly, the mandate is specified in the App Review Guidelineshttps://developer.apple.com/app-store/review/guidelines/#minimum-functionality(ii)If your app doesn’t include significant account-based features, let people use it without a log-in. 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.You should notice that that's from the Privacy section, 5.1.1