Hello, could we have an update on the bug referred here: 28265677. Do we know if it is fixed in iOS 11 or later? thanks

after 2 years and with iOS 14, it looks like there is a solution in SwitUI for this: https://www.createwithswift.com/creating-a-custom-app-launch-experience-in-swiftui-with-deep-linking/

thank you for your answers. back on nearly the same topic: @eskimo we are using BGProcessingTask and NSURLSession with URLSessionConfiguration.background(withIdentifier:) for our uploads. the system will split the time allocated to our app to run in the background between BGProcessingTask and NSURL Session or will it consider time allocated for those 2 separately?

Hello, we are seeing occurrences of the same kind of crash while working with collection in Swift. crash stack of the crash is as below: 0 libsystem_kernel.dylib 0x1d810e974 __pthread_kill + 8 1 libsystem_c.dylib 0x197b57b80 abort + 179 2 libswiftCore.dylib 0x18e85a690 swift::fatalErrorv(unsigned int, char const*, char*) + 135 3 libswiftCore.dylib 0x18e85a6b0 swift::fatalError(unsigned int, char const*, ...) + 31 4 libswiftCore.dylib 0x18e85f4dc swift_deallocClassInstance + 307 5 libswiftCore.dylib 0x18e85f36c _swift_release_dealloc + 55 6 libswiftCore.dylib 0x18e860488 bool swift::RefCounts<swift::RefCountBitsT<(swift::RefCountInlinedness)1> >::doDecrementSlow<(swift::PerformDeinit)1>(swift::RefCountBitsT<(swift::RefCountInlinedness)1>, unsigned int) + 135 crash message: # Cause: Object 0x12d4e8000 of class _DictionaryStorage deallocated with non-zero retain count 3. This object's deinit, or something called from it, may have created a strong reference to self which outlived deinit, resulting in a dangling reference.