“eskimo”

Have you filed a bug about this already? If so, what was the bug number? If you haven’t filed a bug, I recommend that you do so now. It looks like you can reproduce this without Xcode, that is, from the command line using just Swift Package Manager. If so, I recommend that you file your bug against the Swift open source. That way you’ll have more insight into the issue’s state (or you could fix it yourself). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='844288021, waterwave, /thread/844288, /profile/waterwave'] I'm consistently encountering an error. [/quote] I’ve seen a bunch of problems like this. I believe it’s tied to a credential timeout, but I don’t definitive evidence for that. Still, if you encounter this again I recommend that you try logging out and logging back in again. I suspect that’ll clear the problem. [quote='844288021, waterwave, /thread/844288, /profile/waterwave'] UX-wise I wish my unpublished comment doesn't disappear upon errors. [/quote] Indeed. We are actively working to improve that situation for the reply editor (r. 186443626), but I don’t know if that improvement will apply to comments. I don’t want to sound like I’m blaming the victim here — this stuff should Just Work™, obviously — but IMO you shouldn’t use comments for anything significant. Personally I treat them like reactions in Slack, so I only use them when it doesn’t really matter whether the other person sees my comment. I explain more about this in Quinn’s Top Te

[quote='903683022, DTS Engineer, /thread/842766?answerId=903683022#903683022'] I’m still researching options and I’ll reply here when I know more. [/quote] So it’s hard to say how I came to this conclusion, but I suspect that the majority of your crashes will have a backtrace that leads into SQLite: 0 libsqlite3.dylib … wherePathSolver + 952 1 libsqlite3.dylib … sqlite3WhereBegin + 2988 2 libsqlite3.dylib … sqlite3Select + 16536 3 libsqlite3.dylib … yy_reduce + 5136 4 libsqlite3.dylib … sqlite3Parser + 36 5 libsqlite3.dylib … sqlite3RunParser + 796 6 libsqlite3.dylib … sqlite3Prepare + 548 7 libsqlite3.dylib … sqlite3LockAndPrepare + 224 8 BRFree … … 29 BRFree … 30 libswift_Concurrency.dylib … completeTaskWithClosure(swift::AsyncContext*, swift::SwiftError*) + 1 This is from thread 11 of your first crash report, btw. This suggests you’re hitting the 0xdead10cc termination, as explained in EXC_CRASH (SIGKILL). It would be nice if MetricKit included that code in its MXCrashDiagnostic, and I encourage you to fil

Sorry this took so long; I got the answer a while back but I was OOO last week and so I’ve only now found time to reply. Unfortunately I don’t come bearing good news. The behaviour you’re seeing in 27.0b6 and later is intended. Remote media extensions are expected to interact with servers on the wider Internet, not with local peers. Sadly, there were technical limitations that prevented us from applying that contraint in earlier beta seeds, which is why things worked on earlier seeds. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='843748021, cometothed4rkside, /thread/843748, /profile/cometothed4rkside'] that approved in the CloudKit console is not the same thing as successfully onboarded [/quote] Right. That matches my understanding: The Approved state indicates that your request has been approved but isn’t yet configured. The Successfully Onboarded state indicates that everything is ready to go. You included your request UUID in your other thread (693155e2-b8ba-4b47-9b6c-64fd97677386) and from that I was able to confirm that you’re in the first state. [quote='843748021, cometothed4rkside, /thread/843748, /profile/cometothed4rkside'] What we cannot explain is how a provider is supposed to discover this. [/quote] Good question. I’m not actually sure what the developer side of this looks like, so I’m going to research that and get back to you. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’ll respond on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

the extension consistently terminated after about 5 seconds I asked about this internally and it seems that we changed the timeout during the iOS 27 beta cycle (r. 174030263), so the 5 second value you’re seeing matches our expectations. If you need a longer timeout, I’d appreciate you filing a bug with the details. Please post your bug number here, just for the record. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I’m confused. You mentioned that you’re using a Personal Team but my view of your records indicate that you’re using a paid (Individual) team (Team ID P________4). Did you join the programme in the interim? Or are you using a Personal Team that’s unrelated to the Apple Account you’re using for forums? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='902495022, PaulTBT, /thread/840500?answerId=902495022#902495022, /profile/PaulTBT'] the UX doing that has been weird for some time [/quote] Indeed. I’ve encountered similar problems and filed my own internal bug about them (r. 183435509). As to your main issue (FB24136873, FB23918943), I’m still digging into that (delayed because I was OOO last week). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

OK, I have a plan (-: Please file a bug requesting that we transfer the configuration from the current team to your organisation team. Make sure to include: The old Team ID The new Team ID The original request UUID Once you’re done, please open a DTS code-level support request, making sure to reference this thread. I’ll use that to do some checks and then make sure you bug gets routed to the right folks. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Well, that’s exciting. First up, let’s get Flutter out of the mix. Try this: Use Xcode to create a new test project, giving it the same bundle ID as your real app. Do a Product > Archive. In the Xcode organiser, export the .ipa from that archive. Re-run your codesign test. Does it have the same problem? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='902580022, zeeqeeng, /thread/842864?answerId=902580022#902580022, /profile/zeeqeeng'] do they live in memory since boot just like kernel XNU too? [/quote] No. The dynamic linker shared cache is actually a giant file with all the system share libraries glommed together. This isn’t all held in memory, but rather the contents of that file gets mapped into processes are necessary. There’s a bunch of complexity involved. I’m not going to go deeper into this because these are all implementation details and have changed over the time. But on current versions of macOS you should feel free to rummage around in /System/Cryptexes/OS/System/Library/dyld/. WARNING This stuff has changed in the past and I fully expect it to change in the future. Don’t encode knowledge about these implementation details into a shipping product. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for sharing. I’ve made sure that the folks looking at FB24377808 are up-to-speed on this. And with that, I’m gonna step out of this particular loop. If and when things change, I expect you’ll hear about it via FB24377808. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Thanks for those. Both crashes show that the main thread crashed with a backtrace like this: 0 libsystem_kernel.dylib 0x24929dcd4 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x2492a130c mach_msg2_internal + 76 2 libsystem_kernel.dylib 0x2492a122c mach_msg2 + 4 3 libsystem_kernel.dylib 0x2492a122c mach_msg_overwrite + 424 4 libsystem_kernel.dylib 0x2492a1078 mach_msg + 24 5 CoreFoundation 0x1998cc344 __CFRunLoopServiceMachPort + 160 6 CoreFoundation 0x199896310 __CFRunLoopRun + 1188 7 CoreFoundation 0x19989554c _CFRunLoopRunSpecificWithOptions + 532 8 GraphicsServices 0x23f87d498 GSEventRunModal + 120 9 UIKitCore 0x19f5c9670 -[UIApplication _run] + 796 10 UIKitCore 0x19f534158 UIApplicationMain + 332 11 BRFree 0x1028d5b78 12 dyld 0x1964a1c1c start + 6928 This is pretty standard for crashes that aren’t really crashes, for example, when your app is terminated by the watchdog. In most such cases MetricKit captures relevant info in the terminationReason field, but that hasn’t happened here )-: I’m still researchin

[quote='903236022, Ray-87, /thread/842911?answerId=903236022#903236022, /profile/Ray-87'] they are independent checkboxes [/quote] Yeah, that’s a trick one. [quote='903236022, Ray-87, /thread/842911?answerId=903236022#903236022, /profile/Ray-87'] an Apple DTS engineer describes this exact one-of-two trap in thread 835229 [/quote] Hey, that’d be me (-: For the benefit of those following at home, here’s a link to my reply. It has screenshots! (-: Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com