5.1.1

Seen 5.1.1 ii in the ASRGs Data Collection and Storage ...?If you can get away with a forced login, and assuming app review's privacy clauses are met, I think an opt-out newsletter is a side debate between you and your users, not Apple. >Or will it be rejected?No one here can promise what app review will/won't accept/reject, and perhaps more germane to the question, there are no pre-reviews.Good luck.

You can still use iOS 7.x as a deployment target in the store, but not w/current tools (Xcode 8.3.2). I'd wonder about doing so, however, as number of users on an iOS that far back is in low single digits.Note that according to iTunes Connect, minimum now for the store is Xcode 6, which supports iOS 4.3 or iOS 5.1.1 minimum deployment, so to reach your goal of supporting older iOSs, you'd need to use older Xcode - restrictions apply, mainly not being able to also support newer iOSs, so...

You can still use iOS 7.x as a deployment target in the store, but not w/current tools (Xcode 8.3.2). I'd wonder about doing so, however, as number of users on an iOS that far back is in low single digits.Note that according to iTunes Connect, minimum now for the store is Xcode 6, which supports iOS 4.3 or iOS 5.1.1 minimum deployment.

Might be ok, but it depends on the functionality behind the login.See the App Review Guidelines Legal 5.1.1 Data Collection and Storage ii

An Individual Developer Account is needed for distribution via the store, not Enterprise.The lowest Xcode for submittal to the store at this time is Xcode 6, which originally supported down to iOS 5.1.1 (for arch with arm64).Personally, I'd not bother below iOS 8.

Look in the right place!Here is a Crash Report for one of the Bus error: 10 incidents. I cannot figure out how to symbolicate it. Instructions say add it to XCODE organizer, but that doesn't seem to do anything. I have DSYM file and all the other Derived files. I tried to use (unfamiliar, to me) ATOS tool but no joy.Line 42 of stack reports timer callback.Line 41 then reports ??? which must be my timerTick function. That is top of call stack so error must be within that method.If that is correct analysis, the problem must be with a line entirely within that method. Am I getting closer? Process: Recipes [8505] Path: /Volumes//Recipes.app/Contents/MacOS/Recipes Identifier: PhilFenster.Recipes Version: 1.2 (1) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Recipes [8505] User ID: 501 Date/Time: 2017-01-18 00:44:31.510 -0500 OS Version: Mac OS X 10.11.6 (15G1212) Report Version: 11 Anonymous UUID: B27D61EC-2341-818F-E544-8F6B6631DDDA Sleep/Wake UUID: FC2D7386-8DD9-44EA-AB06-40861D6D31FD Time Awak

Latest Xcode 8.2.1, no.Try Xcode 5.1.1 from here: https://developer.apple.com/download/more/But keep in mind you can't use 5.1.1 to submit apps to the store.

Appears to be 5.1.1

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.

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