DTiPhoneSimulatorErrorDomain Code 2

You didn't attach any screenshots here. Did you report this in the Feedback Assistant and just copy it to here? These are the Developer Forums, where developers of third-party apps for Apple's platforms ask each other for hints and tips on coding. You're basically speaking to other third-party developers like you. If you need to get in touch with Developer Support, go here: https://developer.apple.com/support/

Hey @jasonknebel we were able to fix it using the new format. Someone replied at Feedback Assistant to try the new format again and it finally worked! We had to change these two arguments from 'EN' to '${EN}': // Before 'data.relationships.localizations.data.0.id' => 'EN', 'included.0.id' => 'EN', // Now 'data.relationships.localizations.data.0.id' => '${EN}', 'included.0.id' => '${EN}', If that helps, do you mind sharing a URL of one of your app clips or just manually check this thing scanning an NFC card with a URL that uses your app clip host but random path that's not associated with an app clip? https://developer.apple.com/forums/thread/803187

Thanks for attaching a sysdiagnose log to your bug (FB21334477). I took a look at the enclosed spin dump and I see this: Thread 0x222f6b 180 samples (216-395) priority 31 (base 31) cpu time 0.016s (43.3M cycles, 111.3M in… 180 thread_start + 8 (libsystem_pthread.dylib + 7080) [0x19ea8cba8] 180 _pthread_start + 136 (libsystem_pthread.dylib + 27656) [0x19ea91c08] 180 ??? (XojoFramework + 1309844) [0x10569bc94] 180 ??? (XojoFramework + 2624740) [0x1057dcce4] … redacted … 180 -[NSAppleScript compileAndReturnError:] + 136 (Foundation + 9808488) [0x1a0c7da68] 180 OSACompile + 52 (OpenScripting + 78068) [0x1bffa30f4] 180 SecurityPolicyTestDescriptor + 152 (OpenScripting + 8836) [0x1bff92284] 180 _SecurityPolicyTest(char const*, void const*, unsigned long) + 332 (OpenScripting + 8472) … 180 InterpreterSecurity_ScanBuffer + 112 (libInterpreterSecurity.dylib + 4868) [0x298e39304] 180 -[InterpreterSecurity scanData:withSourceURL:] + 164 (libInterpreterSecurity.dylib + 3… 180 -[XProtectScan beginAnalysisWithFeedback:] +

Had the same problem. The problem is in unfinished transactions. They should be finished (if it make sense). We did two things to fix this issue: Call transaction.finish() for inside loop for await transaction in Transaction.updates Not all non-finished transactions exist in Transaction.updates. So we also finish transactions from Transaction.unfinished. This fixed the issue.

[quote='871291022, AbsurdFish, /thread/811481?answerId=871291022#871291022, /profile/AbsurdFish'] Revoke and regenerate the Installer certificate? [/quote] Do not do that. Developer ID signing identities are precious. See The Care and Feeding of Developer ID for a lot more background on that issue. [quote='871291022, AbsurdFish, /thread/811481?answerId=871291022#871291022, /profile/AbsurdFish'] Download and install intermediate certificates? [/quote] Yes. The majority of unable to build chain to self-signed root problems are caused by a missing intermediate. I talk about this in detail in Fixing an untrusted code signing certificate. Its focus is on code-signing certificates, but the same logic applies to installer-signing certificates as well. Note It’s perfectly feasible for your Developer ID Application and Developer ID Installer certificates to be issued via different intermediates, and that would explain the behaviour you’re seeing here. Share and Enjoy — Quinn “The Eskimo!” @ Developer

Looking at the code you posted, the only way [1] that preferences can be nil at line 15 is if your decoded object code fails. You didn’t show that code, so it’s hard to tell what’s going on there. It sounds like you can reproduce this reasonably reliably. Given that, you can debug this using logging. I have general advice on that topic in Testing and Debugging Code Running in the Background. IMPORTANT It’s time to stop using NSLog habitually. Rather, use print(…) for transient debugging and Logger for debugging that you want to keep in your codebase (or for cases like this, where you need to debug without Xcode being attached). Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Well, not the only way. You could be dealing with an issue that’s outside of the scope of the Objective-C / Swift execution models, like a memory corruption problem. However, let’s rule out the easy things first (-: