Hello everyone, I'm trying to create an App Clip for my existing app (it's a multiplatform app). Now Xcode can't sign my app, and the following error appears: Provisioning profile "iOS Team Provisioning Profile: xx" doesn't match the entitlements file's value for the com.apple.developer.associated-appclip-app-identifiers entitlement. If I don't add that row in my project's entitlement then I can sign my app but I can't upload it to App Store Connect, telling me that the value is missing. I've tried to delete the saved profiles in my Mac and force Xcode to download them again. I started thinking about if you can create an App Clip for a multiplatform project or even if it's a bug in Xcode 12.5 beta 3. Does anyone experienced the same or have some suggestion to try? Thank you! Aniol

A few months ago I tested App Clips with my app, but I don't plan to add them for now. The problem is that now I can't select a build in App Store Connect that does not contain an App Clip, and I receive the following error: "An error has occurred. Try again later." I've inspected the HTTP response to get more information about the error, and I got this: { "errors" : [ { "id" : "xxxxxxxxxxxxxxxxxxxxxxxx", "status" : "409", "code" : "ENTITY_ERROR.RELATIONSHIP.UNKNOWN", "title" : "The provided entity includes an unknown relationship", "detail" : "'appClipDefaultExperiences' is not a relationship on the resource 'appStoreVersions'", "source" : { "pointer" : "/data/relationships/appClipDefaultExperiences" } } ] } Does anybody know how to completely disable App Clips for one app without having to generate a new identifier? Thank you so much and have a great day/night! Aniol.

I’m running macOS 26 Beta 1 (build 25A5279m) on a 2019 Mac Pro (MacPro7,1) with a single 4K display connected via HDMI. Whenever I attempt to launch Finder, WindowServer immediately aborts and the machine reboots. Crash details: Process: WindowServer (PID 1441) Exception: EXC_CRASH (SIGABRT) triggered in thread 0 (ws_main_thread) Termination Reason: Abort trap: 6 Backtrace highlights: CA::OGL::MetalContext::draw(MTLPrimitiveType, …) hits an internal __assert_rtn in libsystem_c.dylib Subsequent calls all stem from QuartzCore’s OpenGL/Metal bridge (CA::OGL::render_layers, LayerNode::apply, etc.) Related threads: Thread 2 (com.apple.coreanimation.render-server) idle in mach_msg_overwrite Thread 1 shows AmbientDisplay and ColorSync callbacks running Hardware/Software: MacPro7,1 (2019) macOS 26.0 Beta 1 (25A5279m) 4K monitor via HDMI System Integrity Protection enabled What I’ve tried so far: Safe-boot (crash still occurs) Switching display profiles in System Settings → Displays → Color (no effect) Happy to provide any additional logs or verbose console output. Let me know if there’s any other data that would help diagnose the Metal/OpenGL integration issue in this beta.