This occurred with iOS 13.5. Can no longer demonstrate with 13.5.1
michaelr
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
Sorry for the delay in responding. No notification of your reply!
Bug is FB8721323
Response was "Unable to diagnose with current information" which isn't very helpful.
This is an iOS 14 only issue. I can access the entire ubiquity container from Files despite the scope setting.
a) select a recently opened file
b) select information
c) select where (icloud Drive/App name)
Michael
Now seen with iOS 14. App locks while attempting to open file. [NSURL getResourceValue:forKey:error:] seems to be the culprit again.
Process:						 SamuraiSafe [14700]
Path:								/private/var/containers/Bundle/Application/01EA18D0-8D34-4B67-BAE2-F6711BA92927/SamuraiSafe.app/SamuraiSafe
Identifier:					net.samarama.SamuraiSafe
Version:						 360 (1.6.13)
AppStoreTools:			 12A7604b
AppVariant:					1:iPad8,1:14
Beta:								YES
Code Type:					 ARM-64 (Native)
Role:								Foreground
Parent Process:			launchd [1]
Coalition:					 net.samarama.SamuraiSafe [8789]
Date/Time:					 2020-11-02 08:11:58.8415 +1100
Launch Time:				 2020-11-02 08:10:50.2517 +1100
OS Version:					iPhone OS 14.1 (18A8395)
Release Type:				User
Baseband Version:		n/a
Report Version:			104
Exception Type:	EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:	EXC_CORPSE_NOTIFY
Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
Termination Description: SPRINGBOARD, <RBSTerminateContext| domain:10 code:0x8BADF00D explanation:scene-update watchdog transgression: application<net.samarama.SamuraiSafe>:14700 exhausted real (wall clock) time allowance of 10.00 seconds | ProcessVisibility: Foreground | ProcessState: Running | WatchdogEvent: scene-update | WatchdogVisibility: Background | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 6.830 (user 6.830, system 0.000), 9% CPU", | "Elapsed application CPU time (seconds): 0.099, 0% CPU" | ) reportType:CrashLog maxTerminationResistance:Interactive>
Triggered by Thread:	0
Thread 0 name:	Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0	 libsystem_kernel.dylib				 0x00000001d52ac3d0 __ulock_wait + 8
1	 libsystem_platform.dylib			 0x00000001f0a240e8 _os_unfair_lock_lock_slow + 196
2	 CoreServicesInternal					 0x00000001bf5e8444 _FSURLBeginResourcePropertyCacheAccess + 52
3	 CoreFoundation								 0x00000001a971a120 -[NSURL getResourceValue:forKey:error:] + 100
4	 UIKitCore										 0x00000001abb18bd8 +[UIDocument+ 5508056 (UIDocumentInternal) _fileModificationDateForURL:] + 96
5	 UIKitCore										 0x00000001abb0ee80 __40-[UIDocument openWithCompletionHandler:]_block_invoke.418 + 176
6	 libdispatch.dylib						 0x00000001a9432ac8 _dispatch_client_callout + 20
7	 libdispatch.dylib						 0x00000001a9440d68 _dispatch_async_and_wait_invoke + 96
8	 libdispatch.dylib						 0x00000001a9432ac8 _dispatch_client_callout + 20
9	 libdispatch.dylib						 0x00000001a944004c _dispatch_main_queue_callback_4CF + 836
10	CoreFoundation								 0x00000001a97b11e4 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 16
11	CoreFoundation								 0x00000001a97ab3b4 __CFRunLoopRun + 2508
12	CoreFoundation								 0x00000001a97aa4bc CFRunLoopRunSpecific + 600
13	GraphicsServices							 0x00000001c02bc820 GSEventRunModal + 164
14	UIKitCore										 0x00000001ac157164 -[UIApplication _run] + 1072
15	UIKitCore										 0x00000001ac15c840 UIApplicationMain + 168
16	SamuraiSafe									 0x00000001041624c8 0x10415c000 + 25800
17	libdyld.dylib								 0x00000001a9471e40 start + 4
I have the same problem with my password manager app.
Setting the NSTextContentType to NSTextContentTypeOneTimeCode may help, although in my case this makes it only slightly less annoying. What is needed is a way to disable the behaviour completely. This is now available with UIKit on iOS (UITextContentTypeNewPassword).
I have a couple of NSSecureTextFields and they don't all behave the same way. Some heuristics are in play to enable the behaviour. Better documentation from Apple would be appreciated!
I provide a solution here. It is not pretty. But it works.
Ditto. Code that works fine on iOS 12, 13, 14 and 15 (devices) fails on iOS 15 simulator.
SecItemAdd returning errSecAuthFailed.
kSecAttrAccessControl object has kSecAccessControlBiometryCurrentSet|kSecAttrAccessibleWhenPasscodeSetThisDeviceOnly
I did submit a big report with iOS 13 in 2020, but then was unable to recreate with iOS 13.5.1 to provide additional debug data.
I have not seen the issue manifest itself recently (iOS 15). So sorry, didn’t have the energy to do so for the above incident.
Same here. XCode 14.2. Crashes every 5 minutes or so, with no input.
Always: Crashed Thread: Dispatch queue: DVTSourceControlGitXPCClient :: Proxy Completion Queue
A workaround is to disable Source Control in settings. But defeats a major purpose of the editor.
Submitted. FB12084416
The app is SamuraiSafe, but it's code is not executed prior to the exception being raised (I checked in the debugger),
so I don't think it is app dependent. It is written in Objective C.
A workaround is to invoke the app dialog that allows credential selection (AppName....). That all works fine.
Ventura and XCode 14.3 is working!
Resolved in Safari 16.5 supplied with macOS Ventura 13.4.
Same problem for me - with an app extension. To change anything (including the version), I need to use XCode 14. This needs to be fixed!