“Visual Studio Maui IOS”

Hello there, Can i rely on the following mapping: generateKey — local only, two possible errors: featureUnsupported (simulator, iOS < 14) unknownSystemFailure (Secure Enclave fault). attestKey — contacts Apple servers, possible errors: featureUnsupported (simulator, iOS < 14) unknownSystemFailure (Secure Enclave fault) invalidInput (one time challenge is not hashed properly) invalidKey (key already attested) serverUnavailable (no network, Apple service down, rate limiting in action). generateAssertion — local only, possible errors: unknownSystemFailure((Secure Enclave fault)) invalidInput (one time challenge is not hashed properly) invalidKey (key deleted from Secure Enclave).

Thanks for the post, and welcome to Xcode and iOS development! To download iOS Simulators for Xcode 26.2, use the Components settings within Xcode. Navigate to Xcode > Settings, from the menu bar, then select the Components tab. The Platform Support section displays the latest available platform and Simulator runtimes. To obtain a previously released Simulator runtime, click the Add button (+) in the lower-left corner, select a platform, and then choose the desired version. Click Download & Install to proceed. Xcode 26.2 includes SDKs for iOS 26.2, iPadOS 26.2, macOS 26.2, tvOS 26.2, visionOS 26.2, and watchOS 26.2. These SDKs are necessary for developing and testing applications for their respective platforms. There are other methods to download simulators but if you are in Xcode, will be easier if you just use that tool to download the simulators as they should be downloaded after installation. I would also recommend to update Xcode to the latest release. More information h

I had the same issue on a M1-Max Studio (with installations of 26.4 beta 3, beta 4, and the RC). I finally solved it and reported the following as a appendix to FB22153797: SUCCESS!! First, what didn’t work — I booted in Safe Mode and tried to install Tahoe 26.4. This failed just as reported above. Then, I DEINSTALLED the F-Secure security suite (which came with my Spectrum Business ISP account). Then attempted the installation (in NORMAL mode, not Safe Mode). The installation worked. So it is clear that the install problem was related to something that F-Secure did to my system that was undone by de-installation.

I found a solution my putting the intent into a shared framework and linking it with public struct SharedIntentsPackage: AppIntentsPackage to the app and the widget so iOS will propagate it into the metadata. It works but looks to unintuitive to me compared to the usual apple system integration apis.

Thanks for the post. I don’t think you have provided much information to be able to help you. Can you provide a focused sample of how you use App Clips? Are you using Xcode, can you create a new sample project that reproduces the issue using the steps below? App Clips are built as a separate target within your existing iOS app project. Open your project in Xcode. Go to File > New > Target. Select App Clip under the iOS tab. Name your App Clip and ensure it is embedded in your main application target. App Clips rely heavily on Universal Links to securely verify the relationship between your website and your app. Add the Associated Domains capability to both your main app target and your App Clip target. Add your domain using the appclips: prefix. Example: appclips:example.com Update the apple-app-site-association (AASA) file on your web server to include an appclips dictionary. { appclips: { apps: [..Clip] } } Please follow this great documentation: https://developer.apple.com/design/hu

Thanks so much with the post. Can I ask you what’s your “cloud-based device testing environment”? Because Universal Links rely on cryptographic trust between the app and the web server, the re-signing process inherently could breaks this trust? The platform signs the app with their own provisioning profile, which does not contain your com.apple.developer.associated-domains entitlement? Apple's security model intentionally prevents unauthorized third parties from claiming your domain. Therefore, there is no native Apple provisioning flag that tells iOS to ignore AASA validation for re-signed builds. Can you provide more details? However, please understand that Universal Links will only work on physical devices with the entitlement. Albert Pascual
  Worldwide Developer Relations.

iOS 26 still doesn't work lol

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.

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 … -[NSRunLoo