User Profile

Since the release of iOS 14, I keep getting reports of this crash via Crashlytics and I have no idea how to figure out what is going wrong, because the stack trace doesn't touch my code anywhere. What can I do? How do I find the source of the problem? EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000004 Crashed: com.apple.root.user-initiated-qos 0	CoreData											 0x1b85a87ac _PFObjectIDFastHash64 + 40 1	CoreFoundation								 0x1b254e4f8 __CFBasicHashRehash + 992 2	CoreFoundation								 0x1b2552414 CFBasicHashRemoveValue + 2384 3	CoreFoundation								 0x1b2469ec0 CFDictionaryRemoveValue + 236 4	CoreData											 0x1b84f51c0 -[NSManagedObjectContext(_NSInternalAdditions) _forgetObject:propagateToObjectStore:removeFromRegistry:] + 124 5	CoreData											 0x1b84d46ec -[_PFManagedObjectReferenceQueue _processReferenceQueue:] + 860 6	CoreData											 0x1b85a0734 -[_PFAutoreleasePoolThunk dealloc] + 48 7	libobjc.A.dylib								0x1c65bb81c AutoreleasePoolPage::releaseUntil(objc_object**) + 204 8	libobjc.A.dylib								0x1c65bb6e8 objc_autoreleasePoolPop + 212 9	libdispatch.dylib							0x1b2120aa4 _dispatch_last_resort_autorelease_pool_pop + 44 10 libdispatch.dylib							0x1b21313c8 _dispatch_root_queue_drain + 1064 11 libdispatch.dylib							0x1b21318e8 _dispatch_worker_thread2 + 116 12 libsystem_pthread.dylib				0x1f9a748cc _pthread_wqthread + 216 13 libsystem_pthread.dylib				0x1f9a7b77c start_wqthread + 8

I tried to create a new version to update an app to fix something for iOS 14. When I clicked on the + to add a version I got a pop up that was missing its content. It was just a pop up with the title "Agreement Update", an empty body, and then a blue "OK" button. I figured there was an ajax error loading the message, but ok, I'll head over to Agreements and accept whatever new agreements there are... ... but that page just shows a spinner and never loads. And the browser Console shows a bunch of 404s as it tries to dynamically load content. [Error] Failed to load resource: the server responded with a status of 404 () (tidbits-popover.angular.min.js.map, line 0) https://appstoreconnect.apple.com/agreements/scripts/npm/tidbits-popover.angular.min.js.map [Error] Failed to load resource: the server responded with a status of 404 () (detail, line 0) https://appstoreconnect.apple.com/WebObjects/iTunesConnect.woa/ra/user/detail [Error] Failed to load resource: the server responded with a status of 404 () (ref, line 0) https://appstoreconnect.apple.com/WebObjects/iTunesConnect.woa/ra/ref It's really important for us to be able to submit app updates now that iOS 14 is available and users are starting to uncover issues that we weren't able to catch in our testing.

I've been spending time updating my apps to make sure they respect safe areas to avoid the notch at the top and edges.And I'm left with the question: Was this REALLY a good idea? I don't think it was.Stretching the UI under the notch at the top introduces a LOT of problems for all sorts of apps and what did we really get in return? 20 more px or so at the top? A slightly larger UI that we can't really use? And didn't we all learn the problems involved with the Samsung Edge? That driving the touch screen all the way the edge of a device that you hold in your HAND was going to have constant problems with UI interaction? The solution isn't "make the developers update all their apps so they can't use all this extra space they've been given." The solution is to leave some chrome around the edges of the device so that people can hold it in their hands. You didn't give us extra space on the screen. You gave us a bunch more work to do to make sure we DON'T use all that extra space on the screen. Please make sure the next phone abandons this stupid idea of notches in the UI and massive gutters around the UI that can't be used. Just pretend that your users are human and need to grip the phone. It's ludicrous. Kenny