I am facing iOS app crash on app start, below is stack trace of crashed thread OS Version: iOS 18.3.2 (22D82) Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Crashed Thread: 28 Application Specific Information: *** -[__NSDictionaryM setObject:forKey:]: key cannot be nil Thread 28 Crashed: 0 CoreFoundation 0x323b575fc 1 libobjc.A.dylib 0x31e649244 objc_exception_throw 2 CoreFoundation 0x323b3f224 3 libloader 0x10651eba4 4 libloader 0x10653f3b4 5 libdispatch.dylib 0x3336a8248 6 libdispatch.dylib 0x3336a9fa8 7 libdispatch.dylib 0x3336b15cc 8 libdispatch.dylib 0x3336b2124 9 libdispatch.dylib 0x3336bd38c 10 libdispatch.dylib 0x3336bcbd8 11 libsystem_pthread.dylib 0x43965d680 _pthread_wqthread 12 libsystem_pthread.dylib 0x43965b474 start_wqthread

Within Xcode's settings location section is a drop down menu to switch between setting the derived data location to be default, relative or custom. However its a global setting. I work on more than one project simultaneously, and for one of them I want the location set to relative, but default for all the others. Is there any way of achieving that?

I have multiple web views of the same domain that share the same local storage, as expected. One of them though, is loading a .webarchive file. The web archive is of the same domain, and is loaded using the same base URL. For some reason, in most cases, the local storage is not shared with this web view when loading the web archive, although if I make that same web view load the actual live web page it does share local storage. I say in most cases, because for some users it works as expected, but for a significant portion of users it isn't sharing local storage. I think that the main difference between working and not is iOS version. iOS 17 seems to be able to share the local storage but iOS 18 does not. I can't find anything related in the release notes of iOS 18 versions. There is nothing in the documentation for load(_:mimeType:characterEncodingName:baseURL:), or the header file, that explains anything specific about local storage and webarchive loading. Does anyone know for sure how local storage is handled when a webarchive is loaded into a web view, and did something change with iOS 18 in regards to this?

I'm trying to schedule a background task that will run on an iPhone and I'm looking into creating a task request using BGProcessingTaskRequest and scheduled it using BGTaskScheduler.shared.submit(). Per earliestBeginDate documentation, this property can be used to specify the earliest time a background task will be launched by OS. All clear here. However, the question is: how is the value interpreted with respect to timezone ? Is the specified date in device timezone ? Is GMT ? Is something else ?

I've seen other similar posts with no clear answers and solutions. My Unity app has been rejected several times with this message: The UIRequiredDeviceCapabilities key in the Info.plist is still set up in such a way that the app will not install on the device used in review. Review device details: Device type: iPhone 13 mini OS version: iOS 18.4 Next Steps Please check the UIRequiredDeviceCapabilities key to verify that it contains only the attributes required for the app features or the attributes that must not be present on the device. Attributes specified by a dictionary should be set to true if they are required and false if they must not be present on the device. I have made sure the submitted app has only one value for UIRequiredDeviceCapabilities, arm64, which is required by Unity. Initially Metal was listed as well, but I've removed it in trying to fix this problem. Additionally, I've ran the app through TestFlight and it functions fine. I'm not sure what else to try to fix this issue, though I've seen from other posts that indicate this type of rejection could possibly be a bit of a red herring and the real issue could be something else. Any help would be appreciated

Hello everyone, I’m experiencing a crash in my iOS application that’s occurring predominantly on devices running iOS 16.6.0. The crash seems to happen on the main thread during a UI operation, specifically within the UIKitCore framework. Crash Log Summary Thread 0 Crashed: 0 libsystem_kernel.dylib 0xca4 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x13b74 mach_msg2_internal + 80 2 libsystem_kernel.dylib 0x13e4c mach_msg_overwrite + 540 3 libsystem_kernel.dylib 0x11e8 mach_msg + 24 4 CoreFoundation 0x79024 __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x7a250 __CFRunLoopRun + 1208 6 CoreFoundation 0x7f3ec CFRunLoopRunSpecific + 612 7 GraphicsServices 0x135c GSEventRunModal + 164 8 UIKitCore 0x39cf58 -[UIApplication _run] + 888 9 UIKitCore 0x39cbbc UIApplicationMain + 340 10 MyApp 0x24050 main + 51 (AppDelegate.swift:51) 11 ??? 0x1d3594dec (Missing) I’ve attached the full crash crashlog.txt and would appreciate any insights or recommendations on how to resolve this issue.

On iOS17, UIDevice.current.batteryLevel is returning values rounded to 0.05, such as 1, 0.95, 0.9. Which used to be a 1% granularity in iOS16. Is this a bug or a new feature?