Process: Xcode [1316]Path: /Users/USER/Downloads/Xcode.app/Contents/MacOS/XcodeIdentifier: com.apple.dt.XcodeVersion: 8.0 (11246)Build Info: IDEFrameworks-11246000000000000~3Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Xcode [1316]User ID: 501Date/Time: 2016-10-20 14:52:43.202 +0800OS Version: Mac OS X 10.11.6 (15G31)Report Version: 11Anonymous UUID: E921A8AF-B1D2-0BE8-6A07-E7441EB437ECTime Awake Since Boot: 71000 secondsSystem Integrity Protection: disabledCrashed Thread: 0 Dispatch queue: com.apple.main-threadException Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFYApplication Specific Information:ProductBuildVersion: 8A218aUNCAUGHT EXCEPTION (NSInternalInconsistencyException): Error getting value for key 'strategyClass' of extension 'KSImageNamed.CompletionStrategy.ImageNamed' in plug-in 'com.ksuther.KSImageNamed'UserInfo: { NSUnderlyingError = Error Domain=DVTPlugInErrorDomain Code=2 Loading a plug-in failed. UserInfo={DVTP
Search results for
5.1.1
400 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
My application rejects the rule 5.1.1.In order to use Facebook for authentication even if it is optional, your app must include significant account-specific functionality from Facebook. Using users’s Facebook for account creation/authentication do not fall in to significant about specific features.What is meant by account-specific functionality from Facebook ?Thx.
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
Is the (OS X) iTunes App Store app Information on Compatibility set from the project minimum Deployment Target, or from somewhere else?I see one of my apps with an App store description saying Requires iOS 6.1 or later..., but in Xcode the Deployment Target setting for the submitted build says iOS 9.3. And one of the new reviews today says that a customer tried to run it on iOS 5.1.1 (and it crashed, as the app depends on several APIs that require iOS 9 or later).
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
Topic:
Developer Tools & Services
SubTopic:
Developer Forums
Tags:
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.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
)HiI'm creating my first app and need to implement a user/auth model. I need some help understanding 5.1.1 of guidelines so I minimize the time I waste implementing different solutions. I've googled / read apple forums a bit on this and I'm not sure what is OK, and what isn't.I originally wanted to just use Facebook for login, as the only thing I will need is a unique userID (e.g. .public_profile premission only) and some authentification. I did not want to roll my own security since 1) no need to invent it again; there are so many other places that I can use for user auth (OAuth, Facebook, Google+ etc.) and 2) most likely my own implementation would be less secure and 3) yet _another_ password?!However it seems that Apple does not allow you to use social platforms for authentification alone as per the guidelines section 5.1.1 (ii). And from how I read 5.1.1 (ii) OAuth wouldn't be allowed either, since I need to use one or more providers (i.e. social networks) and then we are essent
Appears to be 5.1.1
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Recently I use XCode Instruments to analyze my app, but after I chosed 'Leaks' and clicked 'Record',My app lanuched normally, and then after a while Instruments will crashed. This can be reproduced each time, it seems that it crashed till it found memory leak and tried to symbolize it, this is what I guessed.And below is the Instruments crash log, anyone can helps? Thanks!Process: Instruments [46792]Path: /Applications/Xcode.app/Contents/Applications/Instruments.app/Contents/MacOS/InstrumentsIdentifier: com.apple.dt.InstrumentsVersion: 7.3 (60134)Build Info: Instruments-60134000000000000~1Code Type: X86-64 (Native)Parent Process: ??? [1]Responsible: Instruments [46792]User ID: 501Date/Time: 2017-01-12 20:39:23.329 +0800OS Version: Mac OS X 10.11.4 (15E65)Report Version: 11Anonymous UUID: CA4AA308-AC41-6B20-CA25-1BC7F62FF091Sleep/Wake UUID: E5DD0799-FD20-4E75-A494-CA0A2A42DA6FTime Awake Since Boot: 91000 secondsTime Since Wake: 33000 secondsSystem Integrity Protection: enabledCrashed Thread: 12 Dispatch queue:
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.
Topic:
Programming Languages
SubTopic:
Swift
Tags:
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
Topic:
Programming Languages
SubTopic:
Swift
Tags:
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.
Topic:
Developer Tools & Services
SubTopic:
General
Tags:
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
Topic:
Developer Tools & Services
SubTopic:
Developer Forums
Tags:
We have an application whose main functionality is to provide users subscription-based content. The user can set their preferences and then gets content based on those settings. Currently the app doesn't have any login features but we're interested in adding them, so we could provide the usersa possibility to store their settings in an account (i.e. they're available in all devices they use), andperks for registration, like free content.In reference to submission guidelines 5.1.1 Data Collection and Storage...(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
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.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags: