I am unable to create a private key to access APNs services from the Developer Portal (developer.apple.com). I take the following steps: Sign in to developer.apple.com Go to Keys (https://developer.apple.com/account/resources/authkeys/list) Click "Create a key" Check the enable box in front of "Apple Push Notifications service (APNs)" A message in red shows up in the same table row: "This service must have one identifier configured.". A "Configure" button appears. Click on the configure button A new page loads at the following URL (https://developer.apple.com/account/resources/authkeys/add) displaying an error dialog with the text: "Unexpected error occurred An unexpected error occurred. Please try again. If the problem persists, please contact Apple Developer Program Support. https://developer.apple.com/support" I contacted support but that might take ages. Error in browser console is as below for this URL: https://developer.apple.com/services-account/QH65B2/account/auth/key/realms/list { "responseId": "a204b125-f8c2-44f2-82f3-269a2e35265c", "resultCode": -1, "resultString": "Unexpected error occurred", "userString": "An unexpected error occurred. Please try again. If the problem persists, please contact Apple Developer Program Support. https://developer.apple.com/support", "creationTimestamp": "2024-10-16T11:51:41Z", "protocolVersion": "QH65B2", "userLocale": "en_US", "requestUrl": "https://developer.apple.com/services-account/QH65B2/account/auth/key/realms/list", "httpCode": 200 }

I am seeing call stacks originating from UIKit code crashing in _UIGetCurrentFallbackTraitCollection with a memory issue. Crash logs are attached. What could this be? My app uses UIAppearance, I suspect this to be related, but I cannot trace the crash logs back to app-specific code. report-2517277966970009999-a5c0cdc9-6616-4f57-87ba-3abe0a16d1dc (1).txt report-2517282597380009999-69132756-a7c8-4b56-9d4c-66742a73e294.txt report-2517281480860009999-0e385e9c-5f69-4ee2-af18-47f180fa814d.txt

We are experiencing crashes in NSManagedObjectContext's mergeChangesFromContextDidSaveNotification:. They seem to have started surfacing in iPadOS 15.7. Three sample crash logs are attached. Is there anything we can do in our app to prevent this issue, or is it an OS-level bug? We also filed feedback item FB11588564. report-2517298112530009999-5bdb464f-7d92-4501-ab77-d90f68644ae7.txt report-2517296133750009999-7e9a09f3-4369-4963-b424-9ed069c3b2e3.txt report-2517290813850009999-1e9e09bf-59d5-4048-9c52-0e1a7fd743d6.txt

Since iPadOS 15.7 was released we are receiving crash logs from customers running iOS 15.7. The crash occurs after calling mergeChangesFromContextDidSave: on a private queue NSManagedObjectContext. Code as below, the crash occurs on the mergeChanges line. We have not seen this crash on earlier iOS releases, which suggests that a (threading?) bug was introduced in Core Data in iOS / iPadOS 15.7. Four crash logs are attached. Unfortunately symbolication failed using symbolicatecrash + Xcode 14.0.1 RC1, but I'm sure Apple's internal symbolication tool will succeed :-)  @objc func mainContextChanged(notification: Notification) {         guard let ctx = notification.object,               ctx as? NSManagedObjectContext != backgroundContext else {             return         }         let ctxt = backgroundContext         ctxt?.perform { [weak ctxt] in             ctxt?.mergeChanges(fromContextDidSave: notification)         }     } report-2517386478470009999-8fe66b99-6808-4a26-97f0-b79979134459.txt report-2517382876410009999-b93d87b6-4510-4579-9e12-6b669e4e02d5.txt report-2517382360450009999-e354e72d-f07e-4d2a-a99d-4576378e3d56.txt report-2517382047060009999-f21995c5-8c9e-48d8-b7d2-c1700fb8757b.txt

Our customer uses our app in circumstances where the hardware could be receiving a lot of sunlight, up until the point where the hardware could become overheated and iOS shuts it off to cool down. We want to proactively monitor this to prevent this situation. Is there a possibility to read the CPU / hardware temperature from within a native Swift/Obj-C app?

I have received two strange crash reports from an iPad11,7 running iPadOS 15.1 and an iPad11,2 running iPadOS 15.2. On both occasions, the crashed thread calls CFURLRequestSetMainDocumentURL, which in turn calls _dispatch_source_set_runloop_timer_4CF in libdispatch, after which the application crashes with SIGSEGV and SEGV_MAPERR. The crashed thread's call stack is displayed below. Full crash logs are attached as well. What could this be? Exception Type: SIGSEGV Exception Codes: SEGV_MAPERR at 0x21d Crashed Thread: 20 Thread 20 Crashed: 0 libdispatch.dylib 0x00000001829e1784 _dispatch_source_set_runloop_timer_4CF + 36 1 CFNetwork 0x00000001834fc824 CFURLRequestSetMainDocumentURL + 2240 2 CFNetwork 0x00000001836b89a8 _CFNetworkErrorGetLocalizedDescription + 693652 3 CFNetwork 0x00000001834fdb1c CFURLRequestSetMainDocumentURL + 7096 4 CFNetwork 0x00000001834f3c34 CFURLRequestSetURL + 9668 5 libdispatch.dylib 0x00000001829ca914 _dispatch_call_block_and_release + 28 6 libdispatch.dylib 0x00000001829cc660 _dispatch_client_callout + 16 7 libdispatch.dylib 0x00000001829d3de4 _dispatch_lane_serial_drain + 668 8 libdispatch.dylib 0x00000001829d498c _dispatch_lane_invoke + 440 9 libdispatch.dylib 0x00000001829d5c74 _dispatch_workloop_invoke + 1792 10 libdispatch.dylib 0x00000001829df1a8 _dispatch_workloop_worker_thread + 652 11 libsystem_pthread.dylib 0x00000001f1eea0f4 _pthread_wqthread + 284 12 libsystem_pthread.dylib 0x00000001f1ee9e94 start_wqthread + 4 second_crashlog.txt report-2517628380750009999-e4d7ea06-6f22-4b7e-b129-045599e1dee5.txt