Posts

Post not yet marked as solved
39 Replies
0 Views
We are observing the same issue on an app that was working fine before the latest release of iOS 14.6 For us ,the responsible code is : [NSManagedObjectContext _disposeObjects:count:notifyParent:] which is triggered when a user logs out of the app, and we reset every objects of our CoreData stack. Hope there will be a fix some day, until then, we are going to go down the -com.apple.CoreData.ConcurrencyDebug 1 road and try to nest every CoreData call into a [NSManagedObjectContext performBlockAndWait:] block.
Post not yet marked as solved
12 Replies
0 Views
There is a workaround (thanks stackoverflow):Right after archiving your app, before uploading to the appstore :Go to OrganizerRight-Click on your app archive -> show in FinderRight-Click on the .xcarchive -> Show package contentGo to Products/Applications/"AppName".app/Open the info.plistFind the BuildMachineOSBuild and change it to the latest public MacOS release (18F132 for macOS 10.14.5)Go and upvote this kind sir :Source : https://stackoverflow.com/a/56623421/4483047