Overview

How to make RCP start playing Timeline from scratch when receiving OnNotification. At present, I have only played the timeline once after receiving the OnNotification, and cannot replay it again after receiving the OnNotification again.

Is there any restriction in File system renaming using shove from sandboxed to runtime path?? failed _relinkFile(/Library/InstallerSandboxes/.PKInstallSandboxManager/EFFC026D-F5AD-4F2D-8EB1-E73B78E51E1A.activeSandbox/Root/Library/Application Support/McAfee/MSS/Applications/Trellix Agent Status Monitor.app/Contents/_CodeSignature/CodeResources, /Library/Application Support/McAfee/MSS/Applications/Trellix Agent Status Monitor.app/Contents/_CodeSignature/CodeResources): Operation not permitted 2026-05-27 12:20:37-04 OSX-CG46R0630R installd[8236]: PackageKit: releasing backupd 2026-05-27 12:20:37-04 OSX-CG46R0630R installd[8236]: PackageKit: allow user idle system sleep 2026-05-27 12:20:37-04 OSX-CG46R0630R installd[8236]: PackageKit: Install Failed: Error Domain=PKInstallErrorDomain Code=120 "An unexpected error occurred while moving files to the final destination." UserInfo={NSLocalizedDescription=An unexpected error occurred while moving files to the final destination., This is immediately followed by: PKInstallErrorDomain Code=120 NSPOSIXErrorDomain Code=1 "Operation not permitted" Based on the installer logs reviewed so far, the failure appears to occur during a PackageKit file relink operation and is accompanied by "Operation not permitted" errors, which suggests a permissions enforcement issue during installation.

I'm trying to test my StoreKit package using local "Consumable.storekit" configuration added to test target as a .copy() resource. I receive various errors. On purchase attempts I receive StoreKitError.unknown. In the console I see this diagnostic messages: [SKTestSession] Error saving configuration file: Error Domain=SKInternalErrorDomain Code=3 "(null)" [SKTestSession] Error setting value to 1 for identifier 2 for com.apple.dt.xctest.tool: Error Domain=SKInternalErrorDomain Code=3 "(null)" I these last two cases product loading failed. It feels like session require mutable .storekit file? Also, some people mention that Host Application must be selected, but it's related to Xcode projects. What is the correct way to test StoreKit within a Swift Package?

I am currently working on mdm.push-token status item subscription via the DDM User Channel while testing on Beta OS 27. I have observed that the User Channel subscription consistently returns the device's push token rather than a unique user-specific push token. This behaviour is persistent across both macOS and Shared iPad environments. Before I conclude that this is a bug, I would like to clarify if this is the expected behaviour for the DDM User Channel. If so, could anyone provide guidance on the correct or alternative method to retrieve a unique, user-specific push token within the DDM framework to ensure proper notification routing? I have submitted a detailed report with a sys diagnose log via the Feedback Assistant (FB ID:FB23214856). Any insights or documentation references would be greatly appreciated.

When I trying to disable sip it just says csrutil: Failed to update security configuration for "Macintosh HD": Manifest verification failed

Hi, I’m running into an issue when importing a .usdz asset into Reality Composer Pro 3. The exact same asset was working perfectly in Reality Composer Pro 2, and it also works correctly when previewed in Xcode 27.0 beta or loaded directly in RealityKit from code. However, in Reality Composer Pro 3, the asset does not import correctly: The material appears completely broken and looks different from the original asset. The animations are not working. The same .usdz works as expected in Reality Composer Pro 2, including materials and animations. The same .usdz also works as expected in Xcode / RealityKit. I also noticed that the Preview app does not seem to import the asset correctly either. In Preview, the asset has the wrong orientation and it looks like the skeleton and animations may not be recognized properly. Here are a few screenshots showing how the asset appears in each app: Reality Composer Pro 2: asset works correctly, including materials and animations. Xcode 27.0 beta preview: asset works correctly, including materials and animations. Reality Composer Pro 3: material is broken and animations are not working. Preview app: wrong orientation, possible skeleton / animation import issue. I filed a ticket FB23214120 that contains an example Xcode project and RCP2 & RCP3 projects. Is there anything specific that changed in the USDZ import pipeline in Composer Pro 3 that could explain this behavior? Thanks!

Before WWDC I had built a fairly simple tap-to-open suitcase where you could tap on an object inside to activate it. (Play audio, no are, etc) all of this was managed in the timeline, which no longer exists. This was really nice because the usdz file was easily shared as a storytelling tool. in the new version… do I really need a model with a closed state, an open state and an opening and closing animations to do something like this? Is there a transform I can perform on an object with a tap instead of creating a specific animation separately? And then using script graphing and animation graphing? I appreciate the in-depth tutorials to showcase the awesomefeatures, but I’m finding it hard to take the information for something as basic like this out of them. even a simple description of how to tap and open a door would make things easier to understand.

▿ DeviceKit.(unknown context at $1058036ec).ErrorDescription title: "The developer disk image could not be mounted on this device." errorClass: "CoreDeviceError" errorCode: "12040" DeviceIdentifier: 0DFB4363-6028-52E1-8C03-17D79DAxxxx #0 super: NSMutableString super: NSString super: NSObject ▿ underlyingErrors: 1 element ▿ DeviceKit.(unknown context at $1058036ec).ErrorDescription - title: "Personalization of the Cryptex-based developer disk image failed." - errorClass: "NSError" - errorCode: "12051" - DDIBuildUpdate: 27A5194q (developerTools) #1 - super: NSMutableString - super: NSString - super: NSObject - DDIPath: /Library/Developer/DeveloperDiskImages/iOS_DDI #2 - super: NSMutableString - super: NSString - super: NSObject - DDIPlatform: iOS #3 - super: NSString - super: NSObject - DDIVariant: external #4 - super: NSString - super: NSObject - DeviceBoardID: 4 #5 - super: NSNumber - super: NSValue - super: NSObject - DeviceChipID: 33040 #6 - super: NSNumber - super: NSValue - super: NSObject - DeviceFusing: prod #7 - super: NSString - super: NSObject - DeviceIdentifier: 0DFB4363-6028-52E1-8C03-17D79DA5E159 #8 - super: NSMutableString - super: NSString - super: NSObject - NSLocalizedFailureReason: An error occurred while personalizing the developer disk image. #9 - super: NSMutableString - super: NSString - super: NSObject - NSLocalizedRecoverySuggestion: Ensure the device is running a supported version of the operating system. If the issue persists, gather a diagnostic report by running 'devicectl diagnose' from Terminal and file a bug report at https://bugreport.apple.com. #10 - super: NSMutableString - super: NSString - super: NSObject - NSURL: file:///Library/Developer/DeveloperDiskImages/iOS_DDI/ #11 - super: NSObject - UseCredentials: 0 #12 - super: NSNumber - super: NSValue - super: NSObject ▿ underlyingErrors: 1 element ▿ DeviceKit.(unknown context at $1058036ec).ErrorDescription - title: "The operation couldn’t be completed. (CryptexKitHost.TatsuError error 4.)" - errorClass: "NSError" - errorCode: "4"

When building our project for Mac Catalyst with Xcode 26.2, we get this warning almost a hundred times, once for every object file: directory not found for option '-L/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.3.48.0.UZtKea/Metal.xctoolchain/usr/lib/swift/maccatalyst' Somehow, every Link <FileName>.o build step got the following parameter, regardless if the target contained Metal files or not: -L/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.3.48.0.UZtKea/Metal.xctoolchain/usr/lib/swift/maccatalyst The toolchain is mounted at this point, but the directory usr/lib/swift/maccatalyst doesn't exist. When building the project for iOS, the option doesn't exist and the warning is not shown. We already check the build settings, but we couldn't find a reason why the linker is trying to link against the toolchain here. Even for targets that do contain Metal files, we get the following linker warning: search path '/var/run/com.apple.security.cryptexd/mnt/com.apple.MobileAsset.MetalToolchain-v17.3.48.0.UZtKea/Metal.xctoolchain/usr/lib/swift/maccatalyst' not found Is this a known issue? Is there a way to get rid of these warnings?

Hi, I wanted to reach out about an issue we're seeing in PTT Framework. We have been investigating reports from some users that our app would run without issue for a day or so and then they would suddenly be unable to transmit audio but playback continued to work normally. After doing some digging and internal testing I was able to reproduce this by triggering a media services reset while PTT Framework was active (we had joined a channel). When this occurs everything appears to work correctly, all normal callbacks are received and the audio session is activated, but the data from the tap on the input node of our audio engine returns only silence regardless of whether the app is in the foreground or background. I'm able to reproduce this with 100% reliability using the following steps: Activate PTT Framework by joining a channel. Navigate to Settings -> Developer, tap Reset Media Services, and select Reset All Media Services. Return to the app and attempt to transmit. I've validated this behavior both in our app as well as in a separate minimal test app we use internally to validate interactions with the framework. Once we end up in this state it persists through tearing down and recreating our audio engine, deactivating and re-activating the audio session, killing the app and restarting it, etc. The only way we have found to recover from this state is to either reboot the device or leave the framework's channel and join again (basically toggle PTT Framework off and back on). Based on what I was able to find I believe this is the known CallKit issue (r.157725305) referenced in this forum post and does extend to PTT Framework. As mentioned above, we currently haven't found a good way to deal with this. Our current solution to this is to programmatically "toggle" PTT framework. This partially solves the problem but it has a couple issues: It causes the PTT Framework activation and deactivation sounds in quick succession. This is expected but not ideal UX. Because attempting to join a channel when the app is not in the foreground results in a failure with PTChannelError.appNotForeground we can only recover when in the foreground. The second issue is the more serious of the two as our users commonly rely on external wired or BLE devices to trigger PTT calls while the device is locked or the app is in the background. In this scenario we can't automatically recover so they won't know something is wrong until they realize they are only transmitting silence. We can identify when this occurs via the internal media services reset notification but again we only receive this while the app is active. Additionally, if the app was suspended when the reset occurred but then becomes active it is received after a 2-4 second delay so if the app wakes up to start a call, we commonly don't receive it until the user is already in the middle of a call trying to transmit. Is there anything we can do here other than posting a notification telling the user that there is an issue and they need to on-screen the app to resolve it? I've tried to provide as much information as possible but if there's anything else that would be helpful let me know.

Hello, I am unable to install my app from TestFlight even though the build appears valid and is in internal beta testing. The build was uploaded successfully to App Store Connect and shows as Testing / Internal Testing. The build metadata looks valid: processingState: VALID internalBuildState: IN_BETA_TESTING qcState: BETA_INTERNAL_TESTING usesNonExemptEncryption: false minOsVersion: 15.0 deviceFamilies: IPHONE supportedArchitectures: arm64 However, TestFlight installation fails, and the App Store Connect API returns: ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Beta contract is missing for the app. My App Store Connect agreements are all active. I checked Business > Agreements and both Paid Apps Agreement and Free Apps Agreement are Active. Bank accounts, tax forms, and compliance also appear Active. This also happens with a newly created app and a fresh build, so it looks like the TestFlight beta contract may be missing or detached on Apple’s backend. Has anyone seen this before, or is there a way to force App Store Connect to refresh the TestFlight beta contract state?

This is truly upsetting that this feature is gone. While I don’t always use it as often as I’d like it’s still a feature that my whole enjoys. Sometimes we just need to get a hold of each other and say a few choice things and leave it be without having to send a text or make a call. This is one of my biggest reason for staying with Apple. It was always a free and very convenient app to use. My kids alone quite enjoy it and love knowing that they. A get a hold of me. I’d like to keep this app, ots low usage shouldnt be a reason to remove it now of no Apple member was not using it I would understand. But it’s still a great feature that I’d like back!

I am porting a project from the now deprecated dns_util api to use the DNS Service Discovery api. With dns_util I am able to specify a DNS name server to use for resolving queries. This is useful for testing new servers or propogation when changes have been made to DNS records. Is it possible to specify the nameserver to use with DNS Service Discovery?

PROVIDE TRACKS OF THE CREATION OF ILLEGAL PERSONALIZATION PRIVACY AND DEVPOLOVER PLATFROM BUSINESS COMMUNITY WHERE IT WAS CREATED AND WHEN IT WAS CREATED. PROVIDE A VERY ACCURATE DATE, TIME, DEVICE, LOCATION AND DO NOT LOSE THE TRACKS OF THE PERPETRATOR WHO IS CLAIMING TO BE THE OWNER OF THE RIGHTS OF THE ACCOUNT OWNER OF MY DATA THAT WAS OBTAINED, THANK YOU.

Hi everyone, Thanks in advance to anyone who shares their experience.

Never do that giving their data source the exact location time of the device used by hackers and accurate signals and giving a human-like form, which is in the name of someone personalization theft of data rights hacking illegal Privacy in the name of my privacy rights thank you.

Our app is a curated short-film streaming app. All content is either produced by us or licensed directly from the independent creators who own it — we do not aggregate, embed, or proxy YouTube, Vimeo, or any third-party streaming/catalog/discovery service. We were rejected under Guideline 5.2.3, with Apple asking for "documentary evidence that you have all necessary rights or permissions to the third-party audio or video streaming, catalogs, and discovery services in the app." We prepared signed documentation (a content rights declaration from our company, the executed creator distribution agreement, the signed consent record for the specific title they flagged, and a sworn authorship/ownership declaration from the creator). We attached these in the Resolution Center reply and got back the identical 5.2.3 template asking us to "attach documentary evidence in the App Review Information section." A few questions for anyone who's been through this: For a documentation-only 5.2.3 issue, does the evidence need to go specifically in the App Review Information → Attachment field (on the version page), versus a Resolution Center reply? Does the reviewer actually read Resolution Center attachments? Does replying in the Resolution Center without tapping "Submit for Review" trigger an actual re-review, or do you have to resubmit (same build, no new binary) to get back in the queue? Has anyone cleared a 5.2.3 "third-party content" rejection where the content is genuinely original/licensed, not third-party? What evidence finally satisfied the reviewer? When you keep getting the same canned response, what's the effective next step — request a call with App Review, or appeal to the App Review Board? Any firsthand experience appreciated.

Hi, I'm the founder of a small independent mobile app company based in Istanbul, Turkey. I'm sharing this because I'm trying to understand whether anyone else has experienced something similar and whether there are any realistic paths forward after a final Apple Developer Program termination. In April 2026, our app received several App Review rejections. We addressed the issues raised by Apple and submitted updated versions of the app as requested. On April 27, 2026, we received a Pending Termination Notice alleging App Review circumvention. We submitted a formal appeal on April 28 and followed up with additional information and documentation on May 15. On June 2, Apple informed us that our appeal was insufficient and that our membership would be terminated. What caught my attention was that the same communication also stated that submitting a reinstatement request could potentially lead to reconsideration. I took that seriously. We immediately shifted our focus toward a complete compliance review of the app, brought in outside assistance, and reviewed everything we could think of: app metadata, screenshots and marketing assets, user flows, source code, business logic, and third-party integrations. The changes were not cosmetic. Entire features were removed, workflows were redesigned, and significant parts of the application's architecture were revised. Our goal was to address every concern we could identify and submit a comprehensive reinstatement request. Then, on June 6, before we were able to complete and submit that request, we received the final termination notice. To be clear, I'm not claiming Apple made the wrong decision, nor am I posting this to generate outrage. What I found difficult to understand was being told that reinstatement could be considered, investing significant time and resources into preparing that submission, and then receiving a final termination before having the opportunity to submit it. For context: We never used external payment systems. We never purchased or manipulated ratings or reviews. We never distributed binaries hidden from App Review. We never intentionally attempted to deceive Apple or bypass review procedures. I'm 24 years old and this is my first company. Looking back, I can see that some of my decisions came down to inexperience. That's exactly why I took the reinstatement process seriously. I wanted to fix what I could. A few questions: Has anyone received reconsideration after a final Apple Developer Program termination? Has anyone experienced receiving a final termination while actively preparing a reinstatement request? Are there any official communication channels available once App Store Connect access has been removed? Thank you for reading. Batuhan Özdemir Founder, Liquid Apps Team ID: 7K3Z69D85W

Hi everyone, Recently I downloaded the last XCode (Version 27.0 beta) and I'm trying to start to play with CoreAI but it's not possible so far to import the CoreAI framework. I'm using the last version of the iPhone simulator. What am I missing?

Hi everyone, I'm trying to delete an App ID from Certificates, Identifiers & Profiles on the Apple Developer portal, but I'm getting the following error: "The App ID 'XXXXXXX' appears to be in use by the App Store, so it can not be removed at this time." Here's my situation: The app was never published to the App Store — it was only created in App Store Connect (no builds were ever submitted for review, and it was never in a "Ready for Sale" state). I have already removed the app from App Store Connect via "Remove App" in App Information. The app is no longer visible in my App Store Connect dashboard. It has been over 48 hours since I removed the app from App Store Connect. Despite this, the Identifiers page still shows the error above when I attempt to delete the corresponding App ID. What I've tried: Confirmed the app no longer appears in App Store Connect (including checking "Removed Apps" filter) Waited over 48 hours for the system to propagate Cleared browser cache and retried My goal: I need to release this Bundle ID so it can be registered under a different Apple Developer account. Questions: Is there an additional waiting period beyond 48 hours before the App ID can be deleted? Is there a way to force-release this App ID, or do I need to contact Apple Developer Support directly? Has anyone experienced this same issue with an app that was never published? Any guidance would be greatly appreciated. Thank you! Environment: Apple Developer Program (Organization account) App was created in App Store Connect but never submitted for review Platform: iOS