Debugging

RSS for tag

Discover and resolve issues with your app.

Pinned Posts

Posts under Debugging tag

475 Posts
Sort by:
Post not yet marked as solved
1 Replies
137 Views
Hi, I'm trying to get IMessage to display a video as part of a link preview with specific dimensions. The video appears, however the dimensions are incorrect. I've set the following tags: <meta property="og:video:url" content={url} /> <meta property="og:video:secure_url" content={url} /> <meta property="og:video:width" content="600" /> <meta property="og:video:height" content="982" /> The video in question is 600x982, 1.1MB in size and an mp4. I've also tried setting the og dimensions to 390x736 since a separate working example url has those, but no luck. Does anyone know what may be the issue?
Posted
by
Post not yet marked as solved
0 Replies
174 Views
Hello, my production app is experiencing some crashes according to app store analytics. I cannot seem to reproduce it. According to Xcode Orginzer the app is crashing 10 SwiftUI 0x000000018ec372a0 PlatformViewHost.updateNestedHosts(_:colorSchemeChanged:) + 332 (PlatformViewHost.swift:699) Distributor ID: com.apple.AppStore Hardware Model: iPhone13,4 Version: 2.0.3 (86) AppStoreTools: 15E204 AppVariant: 1:iPhone13,4:16 Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] OS Version: iPhone OS 17.4.1 (21E236) Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: SIGNAL 6 Abort trap: 6 Triggered by Thread: 0 Kernel Triage: VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter Thread 0 name: Thread 0 Crashed: 0 libsystem_kernel.dylib 0x00000001d1bd6974 __pthread_kill + 8 (:-1) 1 libsystem_pthread.dylib 0x00000001e56590ec pthread_kill + 268 (pthread.c:1717) 2 libsystem_c.dylib 0x0000000191627c14 __abort + 136 (abort.c:159) 3 libsystem_c.dylib 0x0000000191627b8c abort + 192 (abort.c:126) 4 libswiftCore.dylib 0x000000018832a690 swift::fatalErrorv(unsigned int, char const*, char*) + 136 (Errors.cpp:387) 5 libswiftCore.dylib 0x000000018832a6b0 swift::fatalError(unsigned int, char const*, ...) + 32 (Errors.cpp:395) 6 libswiftCore.dylib 0x0000000188324a08 getNonNullSrcObject(swift::OpaqueValue*, swift::TargetMetadata<swift::InProcess> const*, swift::TargetMetadata<swift::InProcess> const*) + 256 (DynamicCast.cpp:144) 7 libswiftCore.dylib 0x0000000188326510 tryCastToObjectiveCClass(swift::OpaqueValue*, swift::TargetMetadata<swift::InProcess> const*, swift::OpaqueValue*, swift::TargetMetadata<swift::InProcess> const*, swift::TargetMetadata<swift::InPro... + 88 (DynamicCast.cpp:510) 8 libswiftCore.dylib 0x0000000188324068 tryCast(swift::OpaqueValue*, swift::TargetMetadata<swift::InProcess> const*, swift::OpaqueValue*, swift::TargetMetadata<swift::InProcess> const*, swift::TargetMetadata<swift::InProcess> const*&, sw... + 992 (DynamicCast.cpp:2281) 9 libswiftCore.dylib 0x0000000188323b14 swift_dynamicCast + 208 (CompatibilityOverrideRuntime.def:109) 10 SwiftUI 0x000000018ec372a0 PlatformViewHost.updateNestedHosts(_:colorSchemeChanged:) + 332 (PlatformViewHost.swift:699) 11 SwiftUI 0x000000018ec36bf4 PlatformViewHost.updateEnvironment(_:viewPhase:) + 412 (PlatformViewHost.swift:690) 12 SwiftUI 0x000000018ec37bf8 PlatformViewHost.init(_:host:environment:viewPhase:importer:) + 808 (PlatformViewHost.swift:132) 13 SwiftUI 0x000000018ec36cf8 PlatformViewHost.__allocating_init(_:host:environment:viewPhase:importer:) + 92 (PlatformViewHost.swift:0) 14 SwiftUI 0x000000018ec0132c closure #1 in closure #1 in closure #4 in closure #1 in PlatformViewChild.updateValue() + 444 (PlatformViewRepresentable.swift:559) 15 SwiftUI 0x000000018ec06c58 partial apply for closure #1 in closure #1 in closure #4 in closure #1 in PlatformViewChild.updateValue() + 24 (<compiler-generated>:0) 16 SwiftUI 0x000000018ea26910 RepresentableContextValues.asCurrent<A>(do:) + 156 (RepresentableContextValues.swift:43) 17 SwiftUI 0x000000018ec01124 closure #1 in closure #4 in closure #1 in PlatformViewChild.updateValue() + 176 (PlatformViewRepresentable.swift:558) 18 SwiftUI 0x000000018ec0104c closure #4 in closure #1 in PlatformViewChild.updateValue() + 128 (PlatformViewRepresentable.swift:557) 19 SwiftUI 0x000000018ec06b2c partial apply for closure #4 in closure #1 in PlatformViewChild.updateValue() + 24 (<compiler-generated>:0) 20 SwiftUI 0x000000018de7b7d0 closure #1 in _withObservation<A>(do:) + 44 (ObservationUtils.swift:26) 21 SwiftUI 0x000000018ec06b50 partial apply for closure #1 in _withObservation<A>(do:) + 24 (<compiler-generated>:0) 22 libswiftCore.dylib 0x0000000187fd0068 withUnsafeMutablePointer<A, B>(to:_:) + 28 (LifetimeManager.swift:82) 23 SwiftUI 0x000000018ebffbdc closure #1 in PlatformViewChild.updateValue() + 3040 (PlatformViewRepresentable.swift:556) 24 SwiftUI 0x000000018d5ecbf8 partial apply for implicit closure #1 in closure #1 in closure #1 in Attribute.init<A>(_:) + 32 (<compiler-generated>:0) 25 AttributeGraph 0x00000001b2150240 AG::Graph::UpdateStack::update() + 512 (ag-graph-update.cc:578) 26 AttributeGraph 0x00000001b2146f38 AG::Graph::update_attribute(AG::data::ptr<AG::Node>, unsigned int) + 424 (ag-graph-update.cc:719) 27 AttributeGraph 0x00000001b2146810 AG::Graph::input_value_ref_slow(AG::data::ptr<AG::Node>, AG::AttributeID, unsigned int, unsigned int, AGSwiftMetadata const*, unsigned char&, long) + 720 (ag-graph.cc:1429)
Posted
by
Post not yet marked as solved
1 Replies
170 Views
i am attaching crash logs would be really appreciated for any kind of help :) Review Environment Submission ID: f7cb438c-5784-44e7-abcf-4a787c9398ff Review date: April 30, 2024 Version reviewed: 1.0 Guideline 2.1 - Performance - App Completeness We were unable to review your app as it crashed on launch. We have attached detailed crash logs to help troubleshoot this issue. Review device details: Device type: iPad Air (5th generation) and iPhone 13 mini OS version: iOS 17.4.1 crashlog-639DEF1C-6DE4-437F-BEFE-E0DA6F31FFD8.txt crashlog-4EC7F1AA-18A9-4057-B1AD-9677FEA6981F.txt
Posted
by
Post not yet marked as solved
0 Replies
135 Views
Apple rejected my app store submission (first submission of this app) with the following comment: Issue Description: The app exhibited one or more bugs that would negatively impact App Store users. Bug description: The app opens to a black display Steps to reproduce bug: Launch app. Review device details: - Device type: iPhone 13 mini - OS version: iOS 17.4.1 Next Steps: Test the app on supported devices to identify and resolve bugs and stability issues before submitting for review. No other details given on specific scenarios. No logs provided. We asked for more info but they refused to help any further. I just so happen to have that exact device (iPhone 13 mini), so I updated it to the iOS version that was giving problems. But no matter what I do, I cannot replicate this bug. I tried via TestFlight and via Xcode, I tried deleting and reinstalling the app, and I tried restarting my phone between installs. I tried launching the app while on airplane mode. I never got this "app opens to a black display" issue. What else can I try to replicate this bug? The app is built with Unity 2021.3.19f1.
Posted
by
Post not yet marked as solved
2 Replies
184 Views
Hello, We recently encountered an issue with our app's submission to the App Store regarding missing permissions. Specifically, our app requires access to two categories called: NSPrivacyAccessedAPICategoryFileTimestamp and NSPrivacyAccessedAPICategoryUserDefaults for proper functionality. Although we've managed to resolve the immediate concern, it's important that we address this as soon as possible (to avoid any further complications with future app submissions). As I'm not entirely familiar with app development/coding, I'm reaching out to seek help with this. We also want to know if the issue we're experiencing is related to using pre-release software or our code? Any insights or help with this would be greatly appreciated. Thanks!
Posted
by
Post marked as solved
4 Replies
167 Views
Hi everyone ! This post is a following of this one. I'm trying to make a .pkg out of two bundles that lands in two different folders, namely : ~/Library/Audio/Plug-Ins/VST3 ~/Library/Audio/Plug-Ins/Components I am still using the script described in the previous post. The installer works fine on the computer that builds the package, on another computer in installs successfully but the aforementioned folders remains empty. My main computer is a MPB M1 (Ventura), I also have a 2015 MBA (Monterey). I tried to make the package on the air and the problem is the same : works on the machine that makes it, not on the receiver. When I try to install to Desktop for test purposes : The MPB correctly ask me for password / touch ID to install permission to use desktop permission to access file in the downloads (which are the extracted file of the .pkg I guess). But nothings happens. The package correctly indicate an installation of ~30Mo so it is not empty. I also tried using the mid process package for one of the two files with the same problem. I tried to use the CLI installer in verbose mode but it doesn't gave much information on what it is actually doing. My two main guess would be : already existing package ID permissions stuff But I don't really know how i could test for this... I would be grateful for any insights, Have a nice day ! -Thomas PS : I haven't found a "package" or "distribution" tag so I used the debugging one, feel free to modify if something seems more appropriate
Posted
by
Post not yet marked as solved
1 Replies
150 Views
Hello! Recently, the following crash issue began to occur. 0 libswiftCore.dylib 0x000000019ffaa3c8 closure #1 in closure #1 in closure #1 in _assertionFailure+ 238536 (_:_:file:line:flags:) + 228 1 libswiftCore.dylib 0x000000019ffaa2a0 closure #1 in closure #1 in _assertionFailure+ 238240 (_:_:file:line:flags:) + 332 2 libswiftCore.dylib 0x000000019ffa9c2c _assertionFailure+ 236588 (_:_:file:line:flags:) + 184 3 libswiftCore.dylib 0x000000019ffac4fc specialized BidirectionalCollection._index+ 247036 (_:offsetBy:) + 1280 4 libswiftCore.dylib 0x00000001a016d630 String.UTF16View._indexRange+ 2086448 (for:from:) + 184 5 libswiftCore.dylib 0x00000001a018561c __StringStorage.getCharacters+ 2184732 (_:range:) + 112 6 libswiftCore.dylib 0x00000001a0185720 @objc __StringStorage.getCharacters+ 2184992 (_:range:) + 36 7 CoreFoundation 0x00000001a16893e0 __CFStringEncodeByteStream + 1864 8 Foundation 0x00000001a0527c94 -[NSString+ 208020 (NSStringOtherEncodings) getBytes:maxLength:usedLength:encoding:options:range:remainingRange:] + 260 ... It seems like assert is being called. Can you tell me a case that could be the cause? Also, this is a code I have been using for a long time, but recently it started crashing. Have there been any internal changes recently? Please understand that the entire crash log cannot be attached for security reasons. Any help would be greatly appreciated!
Posted
by
Post not yet marked as solved
0 Replies
210 Views
Both view and modifier versions of the FamilyActivityPicker crash randomly when selecting some items (usually the other option) throwing these in the console: [com.apple.FamilyControls.ActivityPickerExtension(1150.1)] Connection to plugin invalidated while in use AX Lookup problem - errorCode:1100 error:Permission denied portName:'com.apple.iphone.axserver' PID:22091 ( 0 AXRuntime 0x00000001c603b0fc _AXGetPortFromCache + 800 1 AXRuntime 0x00000001c603cce0 AXUIElementPerformFencedActionWithValue + 700 2 UIKit 0x0000000230de3ec8 DDE6E0C5-2AC3-3C73-8CFE-BC88DE35BB5F + 1453768 3 libdispatch.dylib 0x0000000103ef0b98 _dispatch_call_block_and_release + 32 4 libdispatch.dylib 0x0000000103ef27bc _dispatch_client_callout + 20 5 libdispatch.dylib 0x0000000103efa66c _dispatch_lane_serial_drain + 832 6 libdispatch.dylib 0x0000000103efb408 _dispatch_lane_invoke + 408 7 libdispatch.dylib 0x0000000103f08404 _dispatch_root_queue_drain_deferred_wlh + 328 8 libdispatch.dylib 0x0000000103f07a38 _dispatch_workloop_worker_thread + 444 9 libsystem_pthread.dylib 0x00000001f0824f20 _pthread_wqthread + 288 10 libsystem_pthread.dylib 0x00000001f0824fc0 start_wqthread + 8 ) This also happens in production apps like the Opal. The questions are: At least how to detect it to be able to manually reload the sheet (like what Opal does and shows an alert when this happens) How to prevent it in the first place? I really appreciate any help you can provide.
Posted
by
Post not yet marked as solved
2 Replies
193 Views
hi, in the settings in the application settings, how do I put a button there to allow the use of the camera?
Posted
by
Post not yet marked as solved
0 Replies
241 Views
After upgrading to iOS 17, Thread Performance Checker is complaining of priority inversion when converting a CVPixelBuffer to UIImage through a CIImage instance. It might be a false-positive or an issue? - (UIImage *)imageForSampleBuffer:(CMSampleBufferRef)sampleBuffer andOrientation:(UIImageOrientation)orientation { CVPixelBufferRef pixelBuffer = CMSampleBufferGetImageBuffer(sampleBuffer); CIImage *ciImage = [CIImage imageWithCVPixelBuffer:pixelBuffer]; UIImage *uiImage = [UIImage imageWithCIImage:ciImage]; NSData *data = UIImageJPEGRepresentation(uiImage, 90); } The code snippet above, when running in a thread set to the default priority results in the message below: Thread Performance Checker: Thread running at User-interactive quality-of-service class waiting on a lower QoS thread running at Default quality-of-service class. Investigate ways to avoid priority inversions PID: 1188, TID: 723209 Backtrace ================================================================= 3 AGXMetalG14 0x0000000235c77cc8 1FEF1F89-B467-37B0-86F8-E05BC8A2A629 + 2927816 4 AGXMetalG14 0x0000000235ccd784 1FEF1F89-B467-37B0-86F8-E05BC8A2A629 + 3278724 5 AGXMetalG14 0x0000000235ccf6a4 1FEF1F89-B467-37B0-86F8-E05BC8A2A629 + 3286692 6 MetalTools 0x000000022f758b68 E712D983-01AD-3FE5-AB66-E00ABF76CD7F + 568168 7 CoreImage 0x00000001a7c0e580 3D2AC243-0880-3BA9-BBF3-A214454875E0 + 267648 8 CoreImage 0x00000001a7d0cc08 3D2AC243-0880-3BA9-BBF3-A214454875E0 + 1309704 9 CoreImage 0x00000001a7c0e2e0 3D2AC243-0880-3BA9-BBF3-A214454875E0 + 266976 10 CoreImage 0x00000001a7c0e1d0 3D2AC243-0880-3BA9-BBF3-A214454875E0 + 266704 11 libdispatch.dylib 0x0000000105e4a7bc _dispatch_client_callout + 20 12 libdispatch.dylib 0x0000000105e5be24 _dispatch_lane_barrier_sync_invoke_and_complete + 176 13 CoreImage 0x00000001a7c0a784 3D2AC243-0880-3BA9-BBF3-A214454875E0 + 251780 14 CoreImage 0x00000001a7c0a46c 3D2AC243-0880-3BA9-BBF3-A214454875E0 + 250988 15 libdispatch.dylib 0x0000000105e5b764 _dispatch_block_async_invoke2 + 148 16 libdispatch.dylib 0x0000000105e4a7bc _dispatch_client_callout + 20 17 libdispatch.dylib 0x0000000105e5266c _dispatch_lane_serial_drain + 832 18 libdispatch.dylib 0x0000000105e5343c _dispatch_lane_invoke + 460 19 libdispatch.dylib 0x0000000105e524a4 _dispatch_lane_serial_drain + 376 20 libdispatch.dylib 0x0000000105e5343c _dispatch_lane_invoke + 460 21 libdispatch.dylib 0x0000000105e60404 _dispatch_root_queue_drain_deferred_wlh + 328 22 libdispatch.dylib 0x0000000105e5fa38 _dispatch_workloop_worker_thread + 444 23 libsystem_pthread.dylib 0x00000001f35a4f20 _pthread_wqthread + 288 24 libsystem_pthread.dylib 0x00000001f35a4fc0 start_wqthread + 8
Posted
by
Post not yet marked as solved
1 Replies
169 Views
{"app_name":"Lama","timestamp":"2024-04-24 17:53:43.00 +0800","app_version":"3.4.2","slice_uuid":"e6cfc88e-7676-3714-8064-92cf92277f05","adam_id":0,"build_version":"126","platform":0,"bundleID":"love.wenext.lama","share_with_app_devs":0,"is_first_party":0,"bug_type":"109","os_version":"iPhone OS 14.8.1 (18H107)","incident_id":"6D0C72BF-1838-4DBD-888F-18B7BD1FD905","name":"Lama"} Incident Identifier: 6D0C72BF-1838-4DBD-888F-18B7BD1FD905 CrashReporter Key: 3324822a0132dd746e7f222aa15b4e29af10d61f Hardware Model: iPhone10,1 Process: Lama [17804] Path: /private/var/containers/Bundle/Application/4866DEE0-0897-411C-B0BA-7F4634AB86B9/Lama.app/Lama Identifier: love.wenext.lama Version: 126 (3.4.2) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: love.wenext.lama [393] Date/Time: 2024-04-24 17:53:42.8357 +0800 Launch Time: 2024-04-24 17:53:42.1537 +0800 OS Version: iPhone OS 14.8.1 (18H107) Release Type: User Baseband Version: 6.71.01 Report Version: 104 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Subtype: KERN_INVALID_ADDRESS at 0x8010000105ab861b Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [17804] Highlighted by Thread: 0 Backtrace not available Unknown thread crashed with ARM Thread State (64-bit): x0: 0x0000000105ab8000 x1: 0x0000000000000008 x2: 0x000000016b6756ef x3: 0x0000000000000000 x4: 0x0000000000000000 x5: 0x0000000000000000 x6: 0x7473696c7373616c x7: 0x0000000000000bc0 x8: 0x000000016b6757c0 x9: 0x000000016b675778 x10: 0x00000001057860b8 x11: 0x000000000000000b x12: 0x0000000000ff0006 x13: 0x0000000000007810 x14: 0x0000000000000003 x15: 0x000000016b676150 x16: 0x000000011788c3a8 x17: 0xbd656ebe86d736b6 x18: 0x0000000000000000 x19: 0x000000016b675890 x20: 0x0000000121b90238 x21: 0x8010000000000623 x22: 0x801000000000063b x23: 0x000000016b676000 x24: 0x8010000105ab861b x25: 0x000000016b6757e8 x26: 0x000000016b696878 x27: 0x000000016b6762d0 x28: 0x000000010578c1bc fp: 0x000000016b675840 lr: 0x000000010574a5c0 sp: 0x000000016b6757c0 pc: 0x000000010574a5f0 cpsr: 0x60000000 esr: 0x00000000 Address size fault Binary images description not available Error Formulating Crash Report: Failed to create CSSymbolicatorRef - corpse still valid ¯_(ツ)_/¯ EOF
Posted
by
Post not yet marked as solved
3 Replies
154 Views
We have an C++ app which runs on multiple platforms and is build using the Qt framework. For a while we had issues with unexplainable stack traces reported by testflight users. Now I found out that if I just put throw std::runtime_error("something"); at the start of my main method the resulting crash call stack would not point to my main method. Is there something I can do (compiler flags/variables/code etc) to have the call stack from the actual throw show up in XCode and testflight?
Posted
by
r64
Post not yet marked as solved
4 Replies
287 Views
We've been working on a SwiftUI app that randomly crashes with an exception. When navigating from one view to another, a rare exception is thrown, maybe every 1 / 200 times or so: <SwiftUI.UIKitNavigationController: 0x109888400> is pushing the same view controller instance (<_TtGC7SwiftUI32NavigationStackHostingControllerVS_7AnyView_: 0x10792d400>) more than once which is not supported and is most likely an error in the application : com.<companyName>.<appName> We haven't coded anything to directly push an instance of a view controller outside of what SwiftUI is doing. It seems to happen when the user taps on a NavigationLink view. It happens both in simulator and on device. Does anyone know what might cause this?
Posted
by
Post not yet marked as solved
3 Replies
263 Views
Starting from Xcode 15.3, previously set custom fonts can no longer be found in XIB files. Sometimes they reappear after deleting and setting the font again, but after a while, they disappear again. Can Xcode please be more stable and considerate of the user experience we developers are trying to create? I'm really frustrated.
Posted
by
Post not yet marked as solved
0 Replies
171 Views
Hi everyone! Anyone else seeing crashes like this: Fatal Exception: NSInvalidArgumentException. -[_UISnapshotWindow actualSceneBounds]: unrecognized selector sent to instance I'm encountering a crash within 3-4 seconds of launching my iOS app specifically on devices running iOS 14. The crash log indicates an NSInvalidArgumentException with the following message: `Fatal Exception: NSInvalidArgumentException 0 CoreFoundation 0x129754 __exceptionPreprocess 1 libobjc.A.dylib 0x287a8 objc_exception_throw 2 CoreFoundation 0x2cc3c -[NSOrderedSet initWithSet:copyItems:] 3 UIKitCore 0xc01ea0 -[UIResponder doesNotRecognizeSelector:] 4 CoreFoundation 0x12c2ac ___forwarding___ 5 CoreFoundation 0x12e5b0 _CF_forwarding_prep_0 6 UIKitCore 0xa918cc -[UIUndoGestureInteraction didMoveToView:] 7 UIKitCore 0x11099b4 _setInteractionView 8 UIKitCore 0x11098bc -[UIView(Dragging) addInteraction:] 9 UIKitCore 0xe9d678 -[UIEditingOverlayViewController _addInteractions] 10 UIKitCore 0x4a73e4 -[UIViewController _setViewAppearState:isAnimating:] 11 UIKitCore 0x4a7910 __52-[UIViewController _setViewAppearState:isAnimating:]_block_invoke 12 CoreFoundation 0xa75bc __NSARRAY_IS_CALLING_OUT_TO_A_BLOCK__ 13 CoreFoundation 0x2410 -[__NSArrayI enumerateObjectsWithOptions:usingBlock:] 14 UIKitCore 0x4a75ac -[UIViewController _setViewAppearState:isAnimating:] 15 UIKitCore 0x4a7dc0 -[UIViewController __viewDidAppear:] 16 UIKitCore 0x4a9964 __64-[UIViewController viewDidMoveToWindow:shouldAppearOrDisappear:]_block_invoke 17 UIKitCore 0x4a873c -[UIViewController _executeAfterAppearanceBlock] 18 UIKitCore 0xbda7c4 _runAfterCACommitDeferredBlocks 19 UIKitCore 0xbc903c _cleanUpAfterCAFlushAndRunDeferredBlocks 20 UIKitCore 0xbfcf10 _afterCACommitHandler 21 CoreFoundation 0xa25e0 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ 22 CoreFoundation 0x9c704 __CFRunLoopDoObservers 23 CoreFoundation 0x9ccb0 __CFRunLoopRun 24 CoreFoundation 0x9c360 CFRunLoopRunSpecific 25 GraphicsServices 0x3734 GSEventRunModal 26 UIKitCore 0xbca584 -[UIApplication _run] 27 UIKitCore 0xbcfdf4 UIApplicationMain 28 JobLogic 0x1d9ac4 main + 14 (main.m:14) 29 libdyld.dylib 0x1cf8 start` Here's what I've observed: The crash consistently occurs within 3-4 seconds of app launch on iOS 14 devices. I'm seeking assistance with: Understanding the Cause: Any insights into potential causes of this crash, particularly related to _[_UISnapshotWindow actualSceneBounds] and its interaction with iOS 14, would be greatly appreciated. Replication Steps: If possible, guidance on how to reliably replicate the crash on a development device would be extremely helpful for debugging purposes. Solutions: Any suggestions or known workarounds to address this specific crash or similar issues in iOS 14 would be invaluable.
Posted
by
Post not yet marked as solved
2 Replies
234 Views
I'm trying to use some files within my application without transfering them to the app's file system, I've managed to do that and by using a bookmark (https://developer.apple.com/documentation/professional_video_applications/fcpxml_reference/asset/media-rep/bookmark/using_bookmark_data) I can access the same directory automatically on every new app laucnh. But if the external device gets disconnected and connected again, or the mobile device is restarted, I've noticed a change in the external device's URL and I also get an error retrieving the bookmark Error Domain=NSFileProviderErrorDomain Code=-2001 "No valid file provider found with identifier ‘com.apple.filesystems.UserFS.FileProvider’." UserInfo={NSLocalizedDescription=No valid file provider found with identifier ‘com.apple.filesystems.UserFS.FileProvider’., NSUnderlyingError=0x302a45a40 {Error Domain=NSFileProviderErrorDomain Code=-2013 "(null)"}} Is there a way that I can automatically regain access to the external device directory, or is using the UIDocumentPickerViewController the only way to access it again? Thanks!
Posted
by