“apple pencil charging”

Had the same problem, testing an iOS app on macOS via TestFlight which previously worked, did recently stop working. But I found a setting in App Store Connect, under each testing group, that says Test iPhone and iPad Apps on Apple Silicon Macs. Enabling this setting made testing on macOS work again.

[quote='880896022, kthchew, /thread/819456?answerId=880896022#880896022, /profile/kthchew'] FB22286320 [/quote] Thanks for filing that. [quote='880953022, kthchew, /thread/819456?answerId=880953022#880953022, /profile/kthchew'] is it possible that your work Mac has access to an internal software update server … ? [/quote] It’s certainly possible, but I usually keep a tight reign on this Mac to prevent that sort of thing. Anyway, based on the fact that multiple folks on this thread are reporting this issue, I think it warrants investigation by the Virtualization team. If you’re hitting this, please file a bug with the details and then post the bug number here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880826022, alexfs123, /thread/819160?answerId=880826022#880826022, /profile/alexfs123'] Shouldn't unmount attempt to close it automatically … ? [/quote] Well, sure, if that’s what’s actually going on here. My hope was that lsof would provide evidence either way. [quote='880826022, alexfs123, /thread/819160?answerId=880826022#880826022, /profile/alexfs123'] I already unmounted it [/quote] So repeating the same steps doesn’t reproduce the issue? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880876022, akshit_ak, /thread/814494?answerId=880876022#880876022, /profile/akshit_ak'] Based on the code you linked to, there might be a bug [/quote] OK. In that case my advice is that you file a bug with your evidence so that the relevant engineers can look at this. Please post your bug number, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for those crash reports. Are you able to find a JSON crash report (.ips) for this? If so, please post it, because it may allow me to learn more about the issue. In the absence of that then, yeah, at first blush this is looks like an Apple problem rather than a problem with your code. Consider the crashing thread from your first crash report: Thread 22 name: Thread 22 Crashed: 0 CoreFoundation … __CFCheckCFInfoPACSignature + 4 (CFRuntime.c:559) 1 CoreFoundation … CFRunLoopSourceSignal + 28 (CFRunLoop.c:4312) 2 Foundation … performQueueDequeue + 484 (NSThread.m:1063) 3 Foundation … __NSThreadPerformPerform + 88 (NSThread.m:1077) 4 CoreFoundation … __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 (CFRunLoop.c:1970) 5 CoreFoundation … __CFRunLoopDoSource0 + 172 (CFRunLoop.c:2014) 6 CoreFoundation … __CFRunLoopDoSources0 + 332 (CFRunLoop.c:2059) 7 CoreFoundation … __CFRunLoopRun + 840 (CFRunLoop.c:2969) 8 CoreFoundation … CFRunLoopRunSpecific + 572 (CFRunLoop.c:3434) 9 Foundation … -

Ah, I see you reanimated two different threads about this issue. I’ll respond over on the other one. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] Here's the direct download link to the installer package: [/quote] That link doesn’t work for me (I get a 404). This: [quote='880810022, kappie, /thread/817887?answerId=880810022#880810022, /profile/kappie'] The productbuild --sign does emit Warning: unable to build chain to self-signed root [/quote] is very concerning. It suggests that the signature was created without the full certificate chain, which could easily cause problems like this. When signing code, rather than an installer package, this is actually a hard failure. I talk about it in detail in Resolving errSecInternalComponent errors during code signing and the associated Fixing an untrusted code signing certificate. So: You should definitely do what you can to investigate and resolve the unable to build chain to self-signed root warning. If that doesn’t pan out, reply back here with a download link that works and I’ll take a look. Share and Enjoy — Quinn “The

[quote='880858022, KayleeSC, /thread/791352?answerId=880858022#880858022, /profile/KayleeSC'] added to the same bug [/quote] I see that. Thanks! Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='880992022, shara7, /thread/818906?answerId=880992022#880992022, /profile/shara7'] Could you tell me whether these log entries … ? [/quote] No, sorry. I have limited time to spend on the forums, and I prefer to spend that time helping folks with code-level problems. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='881033022, robonaren, /thread/819553?answerId=881033022#881033022, /profile/robonaren'] Here are the specific requirement i've tried [/quote] So anchor apple generic is definitely wrong. Consider this quote from Code Signing Requirement Language: For Apple’s own code, signed by Apple, you can use the short form anchor apple For code signed by Apple, including code signed using a signing certificate issued by Apple to other developers, use the form anchor apple generic If your goal is security, you don’t want to mix these up! [quote='881053022, robonaren, /thread/819553?answerId=881053022#881053022, /profile/robonaren'] Here are the specific requirement i'm using from the Authorization Plugin (xpc client) [/quote] From the client? Maybe I’ve misunderstood this, but that seems backwards. You want to apply these constraints on the server for connections coming from the client. Consider this: % csreq -r '=anchor apple and (identifier