User Profile

In my latest app update I have a few users complaining about crashes and I managed to get my hands on a crash report. Here's the crash reason from the symbolicated crash log. Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d Triggered by Thread: 0This happens when I call `[NSPersistentStoreCoordinator addPersistentStoreWithType:configuration:URL:options:error:]`Here's the complete stacktrace: Thread 0 name: Dispatch queue: SQLQueue 0x12fecca10 for .database.db.migrationdestination_41b5a6b5c6e848c462a8480cd24caef3 Thread 0 Crashed: 0 libsystem_kernel.dylib 0x0000000180640164 __fcntl + 8 1 libsystem_kernel.dylib 0x0000000180625660 fcntl + 84 2 libsqlite3.dylib 0x0000000181ba3f90 0x181b3d000 + 421776 3 libsqlite3.dylib 0x0000000181bb9e50 0x181b3d000 + 511568 4 libsqlite3.dylib 0x0000000181bcdf34 0x181b3d000 + 593716 5 libsqlite3.dylib 0x0000000181bcdd98 sqlite3_wal_checkpoint_v2 + 492 6 libsqlite3.dylib 0x0000000181ba41b0 0x181b3d000 + 422320 7 libsqlite3.dylib 0x0000000181b7b288 sqlite3_step + 976 8 CoreData 0x000000018391b194 _execute + 164 9 CoreData 0x000000018394ffd8 -[NSSQLiteConnection commitTransaction] + 312 10 CoreData 0x0000000183a6ced8 __43-[_NSSQLiteStoreMigrator performMigration:]_block_invoke + 2784 11 CoreData 0x0000000183a36cbc __37-[NSSQLiteConnection performAndWait:]_block_invoke + 40 12 libdispatch.dylib 0x00000001804fe9a0 _dispatch_client_callout + 16 13 libdispatch.dylib 0x000000018050bee0 _dispatch_barrier_sync_f_invoke + 84 14 CoreData 0x0000000183a36c08 -[NSSQLiteConnection performAndWait:] + 144 15 CoreData 0x0000000183a6c35c -[_NSSQLiteStoreMigrator performMigration:] + 184 16 CoreData 0x0000000183a63db0 -[NSSQLiteInPlaceMigrationManager migrateStoreFromURL:type:options:withMappingModel:toDestinationURL:destinationType:destinationOptions:error:] + 1912 17 CoreData 0x00000001839ee814 -[NSMigrationManager migrateStoreFromURL:type:options:withMappingModel:toDestinationURL:destinationType:destinationOptions:error:] + 556 18 CoreData 0x0000000183a5f090 -[NSStoreMigrationPolicy(InternalMethods) migrateStoreAtURL:toURL:storeType:options:withManager:error:] + 324 19 CoreData 0x0000000183a5e3ec -[NSStoreMigrationPolicy migrateStoreAtURL:withManager:metadata:options:error:] + 120 20 CoreData 0x0000000183a5fb08 -[NSStoreMigrationPolicy(InternalMethods) _gatherDataAndPerformMigration:] + 2440 21 CoreData 0x00000001839fc188 __91-[NSPersistentStoreCoordinator addPersistentStoreWithType:configuration:URL:options:error:]_block_invoke + 4160 22 CoreData 0x0000000183a08630 gutsOfBlockToNSPersistentStoreCoordinatorPerform + 168 23 libdispatch.dylib 0x00000001804fe9a0 _dispatch_client_callout + 16 24 libdispatch.dylib 0x000000018050bee0 _dispatch_barrier_sync_f_invoke + 84 25 CoreData 0x00000001839f7d70 _perform + 200 26 CoreData 0x000000018390d5e4 -[NSPersistentStoreCoordinator addPersistentStoreWithType:configuration:URL:options:error:] + 388I don't have more details on the crash. Only that it happens for a few users and not all. I have no idea how to reproduce it for a proper fix. The user reported that the app started, was "frozen" for some time and then it crashed. And it keeps doing so.I had a look at the last version of the core-data model since I shipped the app and this file is still the exact same. During development I added 5 more versions in-between but that shouldn't be a problem right? The version shipped in the app before the update is untouched...The changes I made to the model were simply adding some new properties on existing entities. But if auto-migration would fail, it would fail for everybody, right? Not only for a few users?!?So I was hoping somebody here already might had the same issue and a solution on how to fix it. Or at least a way on how to detect the problem without the app crashing. Then I could just recreate the DB for those users...Thanks,Georg

In my design I have a widget that shows the last x rows of content from my app, but the height of the whole list is of course limited by the widgets height. I'd like all my items to be able to have max 2 lines, but only if needed. Also, the List should only display as many items, as will fit in it. Not more... So upfront I can't say how may items I will be able to display because it will depend on the content, font ect... How can I achieve that? I haven't found a good solution to figure out how much height a view will need with a given width?!?

Is it possible to add icons to items in an INObjectCollection? Like e.g. the reminders app has the Icon of the List it displays?!? And then bonus question: If my icons aren't stored locally but are an URL to an image. Would that work as well? Couldn't find an answer using the docs... but as the Reminders-Widget-Configuration can do it, maybe we developers can add that as well :)

In the last update of my app I added a CloudKit sync and now I have a user telling me that sync isn't working. He sent me his device logs and I found the following. I tried to google the error message about the same batch didn't have chain PCS data on it for record error message, but found nothing. Does anybody have an idea what causes the problem? And how do I fix it?Here's a part from the log: (there are many many more lines like these)E3025D29-4C92-46EE-AB90-9C821B7B5824:(***:__defaultOwner__) = in the same batch didn't have chain PCS data on it for record "> 27D87174-F296-4BEE-9C20-66CB040EF8B3:(***:__defaultOwner__) = in the same batch didn't have chain PCS data on it for record ">Any help is greaty appreciated!!!

Hello,I'd love to try out the new Xcode 11 Beta but when I try to open it, it immediatly crashes all the time.Here's the output from the console:default 08:40:21.346289 +0200 loginwindow -[PersistentAppsSupport applicationReady:] | App: Xcode-beta, ready, updating active tracking timer default 08:40:21.346338 +0200 loginwindow -[ApplicationManager checkInAppContext:refCon:eventData:] | checked in app : Xcode-beta default 08:40:21.503611 +0200 launchservicesd CHECKIN:0x0-0x6f06f 1720 com.apple.dt.Xcode default 08:40:21.504250 +0200 loginwindow -[ApplicationManager checkInAppContext:refCon:eventData:] | checked in app : Xcode default 08:40:21.562715 +0200 Xcode Current system appearance, (HLTB: 2), (SLS: 1) default 08:40:21.566234 +0200 Xcode Post-registration system appearance: (HLTB: 2) default 08:40:21.585111 +0200 Xcode [MT] DVTAssertions: ASSERTION FAILURE in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-14831.16/DVTFoundation/Assertions/DVTSoftAssertions.m:121 Details: No path for file: LibrariesExemptedFromTriage.plist Function: NSArray *_PlistDataFromFile(NSString *__strong) Thread: <NSThread: 0x7fea5a71b620>{number = 1, name = main} Hints: default 08:40:21.592282 +0200 Xcode [MT] DVTAssertions: Backtrace: 0 -[IDEAssertionHandler handleFailureInFunction:fileName:lineNumber:assertionSignature:messageFormat:arguments:] (in IDEKit) 1 _DVTAssertionHandler (in DVTFoundation) 2 _DVTAssertionFailureHandler (in DVTFoundation) 3 _PlistDataFromFile (in DVTFoundation) 4 __DVTSoftAssertions_Initialize_block_invoke (in DVTFoundation) 5 _dispatch_client_callout (in libdispatch.dylib) 6 _dispatch_once_callout (in libdispatch.dylib) 7 DVTSoftAssertions_Initialize (in DVTFoundation) 8 IDEInitialize (in IDEFoundation) 9 -[IDEApplicationController applicationWillFinishLaunching:] (in IDEKit) 10 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ (in CoreFoundation) 11 ___CFXRegistrationPost_block_invoke (in CoreFoundation) 12 _CFXRegistrationPost (in CoreFoundation) 13 ___CFXNotificationPost_block_invoke (in CoreFoundation) 14 -[_CFXNotificationRegistrar find:object:observer:enumerator:] (in CoreFoundation) 15 _<…> default 08:40:21.635821 +0200 loginwindow -[PersistentAppsSupport applicationQuit:] | for app:Xcode, _appTrackingState = 2 default 08:40:21.635854 +0200 loginwindow -[PersistentAppsSupport applicationQuit:] | App: Xcode, quit, updating activs tracking timer default 08:40:30.915547 +0200 ReportCrash Saved crash report for Xcode[1720] version 11.0 (14855.18) to Xcode_2019-06-05-084030_MacBox-4.crashHere's a link to the mentioned crashlog file:https://www.dropbox.com/s/wg057zrgk6itssj/Xcode_2019-06-05-084030_MacBox-4.crash?dl=0Appreciate your help!Cheers,Georg

In my app I don't want to use the Apple-Default iCloud Share-Sheet as it does not at all match the style of my app.That's why I create CKShares manually and let others users then scan a QR-Code from the owners phone to accept a share.Everything is working nicely... but...Now I want the owner to be able to remove a certain participent.A CKShare has a participants property, but for all my invited users I don't see anything. No name, email, nothing. I guess that's because of privacy reasons and it's fine to me. But not even the default UICloudSharingController will display names for me?!?What would be suggested ways of fixing the problem? Is it ok, if I'd require a user to enter his Username when accepting or even creating a share? I'd prefer not having to do this?!?Cheers,Georg

I am trying around with the new Siri Shortcuts and would like to provide a location to my custom Intent.I found that there is this API for creating a CLPlacemark yourself: https://developer.apple.com/documentation/corelocation/clplacemark/2132103-initBut when I do so, Xcode tells me, that the Type of expression is ambiguous without more contextI've added Intents and CoreLocation as imports and my deployment target is iOS 11... So I guess it should work?!?Fun fact is that instantiating a CLPlacemark like so works in Xcode 9, but not in the Xcode 10 beta?!?Is there a way to get it working with Xcode 10 as well?Cheers,Georg

Hello,while seaching for this problem I already found the following thread here: https://forums.developer.apple.com/message/283572#283572 but then mainly focus on the horizontal accuracy. I haven't made that observation so far (or at least none of our users complained about is yet...) but what we have a lot of problems with is vertical accuracy. We have a hiking app where the user wants to know his ascent as accurate as possible. We use the Barometer for a more reliable result, but still need the GPS to from time to time recalibrate.Is this a known Hardware-Issue that Apple admits? We only see those Problems in iPhone X and 8. Not all of the devices, but when users complain it's either the one or the other device. We then ask them to send us debugging Information and those look like the following. The red-line is altitude reported by the GPS and the blue one is the far more accurate one.If there is any known software-tweak we could do, I'd me super happy to know.Would be cool to hear something from somebody who is familiar with the matter.Cheers,Georg