Building for iOS Simulator, but the linked and embedded framework ‘XX.framework‘ was built for

Still crashing on Xcode 16.2 with iOS 18.2, macOS 15.2 and visionOS 2.2

Thank you for the update and for working on this issue. RealityKit is like SceneKit, both are 3D frameworks that use ARKit as the AR framework. So this may actually help isolate the issue to the ARKit/Game Center interaction. Plus I swear it was all working for me months ago. However I also just realize this is breaking a SceneKit AR app I already have in the store. Granted, not a very popular one. Still an annoying mess. I'll file the TPS.

I just started running into this a few days ago and I'm not sure why. Same behavior as described above. Everything is working fine, then I need to connect to a VPN for work and when I disconnect from the VPN and try to build the app again and deploy it to the phone, it fails with: Warning: unable to build chain to self-signed root for signer Apple Development: {redacted} (redacted) Command CodeSign failed with a nonzero exit code There is also mention of errSecInternalComponent. If I open keychain on my Mac, I see that my development certificate now says that it's not trusted. And indeed, as julian99 stated, if I change the trust settings to Always Trust, close that window, re-open the certificate again, change the trust settings back to Use System Defaults and then close the window again, it fixes the problem. For added fun, I have to connect and disconnect from the VPN a lot during the work day because the VPN configuration blocks all IPv6 traffic (including link-local traffic) so

I wanted to update this post with resources I found. It appears the automation for persistent anchors and world data maps has been configured as WorldAnchors. Currently, it looks like this is only supported in visionOS. https://developer.apple.com/documentation/visionos/tracking-points-in-world-space It appears that by simply adding a WorldAnchor that visionOS automatically tracks the world map, unloading and loading based on your location automatically in the background. This is amazing. Though, I'm not sure why this wouldn't be supported on iOs and iPadOS as well. Perhaps in the future it will be implemented as a core ARKit feature as well. To the best of my limited knowledge, it appears we will have to continue to use the previous methods for persistent data, which can be found here: https://developer.apple.com/documentation/arkit/arkit_in_ios/data_management/saving_and_loading_world_data However, I still have to try and implement this with RealityView. As it is my understanding that only RealityV

I know this is an old post, but I just came across this error on an DEP device that is running iPadOS 15.8.3. In case someone else has the same problem, iOS/iPadOS supports only UserEnrollment prior to iOS 16.

Also seeing this regression on iOS 18.0—I haven't tested other versions yet.

Also started getting this after updating to iOS 18.2

Thanks to the iOS Developer Support team, we were able to identify the root cause of the issue. They pointed us toward the Apple App Site Association (AASA) file, which is required for Universal Links to function. It appears that this file is downloaded asynchronously after app installation, leading to the observed delay in executing the deep link. With this insight, we implemented a URL scheme deep link instead of relying on a Universal Link. Since URL schemes work immediately after installation, this resolved the problem entirely. I would suggest adding a hint or recommendation in the Custom Product Pages deep link input field in App Store Connect to encourage the use of URL scheme links instead of Universal Links, particularly for scenarios where immediate link execution is critical.