DTiPhoneSimulatorErrorDomain Code 2

Image: iOS 26 EV-2 Burst camera settings: Camera Settings iOS 26 bracket catpure iOS 26 single photo EV-2 Camera settings iOS 26 sigle photo

Thanks for the post, can you provide a little more information about the URL you are passing or just the code you are using when that message shows in your console? As that API can be called in a thread that is not the main thread as shows in the documentation: You can call this method safely on a thread that isn’t the main thread. https://developer.apple.com/documentation/uikit/uiapplication/canopenurl(_:) Interesting to see what URL are you calling, the method should return a true or false only. Providing a focused sample and iOS version, Xcode and macOS is always a good idea. Thanks Albert Pascual
  Worldwide Developer Relations.

thank you for your reply. diffing the scene is a good idea. until now, I had no idea how to even approach the bug hunting, since it seems not connected to any interaction / changes nor code. it is most likely the serialization of scene data. I'll keep you updated and try to reproduce it. I can actually provide the project as it is not super complex and nor confidential.

In general, the notary service should include all Mach-O images in your submission in the ticket that it issues. Thus, you shouldn’t have to notarise helper independently, or Application Bundle.app for that matter [1]. However, I recommend that you check this, just to be sure. To do that: Submit your package for notarisation. On successful notarisation, fetch the notary log. See if it lists the cdhash values for helper. IMPORTANT If your helper has multiple architectures, check that both cdhash values are present. For more on cdhash values, see TN3126 Inside Code Signing: Hashes. For more background on how this stuff works, see Notarisation Fundamentals. For links to lots of other notarisation info, see Notarisation Resources. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Although it’s fine to do that if, for example, you also distribute the app via some other channel that doesn’t involve this installer package.

OK. Thanks for confirming. When you see this, is there only one user involved? That is: You’ve log in via the GUI. And are working with networking, including your VPN. Without logging out. Or fast user switching to a different user. Is that right? This matters because appex packaging only really works in the context of a single user, so if you add other users into the mix things get complicated. Also, you wrote: [quote='811887021, disinghal, /thread/811887, /profile/disinghal'] internet goes away on machine leading to a connection stuck state. [/quote] Can you clarify what this means? I see two possibilities: Networking goes away for other apps on the system but the system doesn’t start your packet tunnel provider. Alternatively, the system starts your packet tunnel provider and it attempts to connect to your VPN server and that connection acts like there’s no Internet. Is it either of these? Or something else? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail =

[quote='812219021, madsodgaard, /thread/812219, /profile/madsodgaard'] I have read most of the Background Tasks Resources here [/quote] Cool. But there are some network specific ones you should also read: Moving to Fewer, Larger Transfers Testing Background Session Code The first one is probably most relevant to your issue. Networking Resources has these links and a lot more. [quote='812219021, madsodgaard, /thread/812219, /profile/madsodgaard'] But, what if they just stay with the app in the foreground? Will it start uploading immediately? [/quote] I would expect so. However, that’s not guaranteed. The nature of background sessions is that the system gets to choose when to run the transfer, based on its global view of the device state. IMPORTANT A lot of this stuff is not documented, and deliberately so. These policies are considered to be implementation details. They’ve changed in the past and it wouldn’t surprise me if they changed again in the future. So, when you ask “Will it do X?” the only rea

[quote='865347022, zed_090, /thread/805920?answerId=865347022#865347022, /profile/zed_090'] I fixed it by updating: [/quote] Weird. Just for grins I created a tiny test app that contains your first code snippet, and it passed through the App Store Connect submission process without any problems. So I’m not sure why this is failing for you or why that change helped. If you’re feeling enthusiastic about this, you could revert the change, see if it still reproduces the problem, and then file a bug about it, making sure to attach the .ipa that you fed into Transporter. If you do that, please post your bug number, just for the record. But no pressure. I understand if you just decide to stick with your workaround. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

So one of the following must be true: You want to use the Background Tasks framework to run long-running tasks via BGProcessingTask. Or you don’t. If you do, add the BGTaskSchedulerPermittedIdentifiers property to your Info.plist and populate it with the list of background task identifiers you use. If you don’t: Remove the processing value from the UIBackgroundModes property in your Info.plist. Remove any code that uses BGProcessingTask. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

No I am using TagReaderSession only but its failing silently Did detect is not getting called for the tag mentioned above in screenshot this is how i am intiating the NFC Session is this correct way or anything is Missed public class NfcServiceIos : INfcServiceIos { private SessionDelegate _currentDelegate; private bool _sessionActive = false; private NFCTagReaderSession _currentSession; public async Task SendAsync(byte[] bytes) { var isNfcAvailable = UIDevice.CurrentDevice.CheckSystemVersion(11, 0); if (isNfcAvailable && NFCTagReaderSession.ReadingAvailable) { if (_sessionActive) { await Application.Current.MainPage.DisplayAlert(Error, NFC session is still active. Please wait., Ok); return; } _sessionActive = true; _currentDelegate = new SessionDelegate(bytes, OnSessionInvalidated); // All CoreNFC session code must be on the main thread! await Microsoft.Maui.ApplicationModel.MainThread.InvokeOnMainThreadAsync(() => { // create NFCTagReaderSession instead of NFCNdefReaderSession _currentSe