Overview

The link to download “MaterialX definitions” is broken on the main page of ShaderGraph documentation in the Interoperability section. See here: https://developer.apple.com/documentation/ShaderGraph#Interoperability Link in the page is https://developer.apple.com/augmented-reality/realitykit/files/MaterialX-definitions.zip but leads nowhere now. Since Reality Composer Pro 3 has been released, it would be good to have these definitions available to download again and to know if it’s still MaterialX 1.38 being used in the updated RCP & RealityKit. Opened a ticket about this: FB23258836

In WWDC26 video "Camera and Photo Technologies Group Lab", @14:17, Brad Ford mentions that we can use isCinematicVideoCaptureEnabled on videoDeviceInput to display depth blur on camera preview, even on a photo camera app. However, when I turn it on for depth mode, the API tells me that it is not supported with the current camera, which is Dual or Dual Wide cameras I use for depth. Since there are no other resources on this, I would love to get some guidance on how to do this. I just want to display depth blur on camera preview, that is it.

I could not find iCloud invading capabilities, it Shows nothing found, is there a problem in account or what

Hello App Review Team, My app, SUB PREMIUM TV (Apple ID: 6769972609, Version 1.0), has been in “Waiting for Review” status for several days. I would like to confirm whether there is any issue with my submission or if any additional information is needed from me. Thank you for your time and assistance. Best regards, Babucarr Ngum

Hello App Review Team, My app, SUB PREMIUM TV (Apple ID: 6769972609, Version 1.0), has been in “Waiting for Review” status for several days. I would like to confirm whether there is any issue with my submission or if any additional information is needed from me. Thank you for your time and assistance. Best regards, Babucarr Ngum

My app has been stuck in "waiting for review" for almost a week now. The previous time it was stuck for a few weeks until I posted here for someone to review it. Can somebody please take a look at my app and review it.

Hi, I am posting here because my organization enrollment has been stuck since May 26, 2026, across three full cycles with the same outcome each time, and first level support has not been able to resolve it. I am hoping someone with backend access can inspect my account and clear whatever is blocking it. Enrollment ID: 8X76A9G2JF Support Case ID: 102917486425 Entity: Organization enrollment, company based in Brazil. Current status: My documents were reviewed and accepted. I accepted the Program License Agreement. The only remaining step is payment, and that is where it fails. What happens at payment: In the Apple Developer app I cannot proceed. It shows: "Enrollment through the Apple Developer app is not available for this Apple Account." On the web, I fill in the payment details and the process simply returns to pending and never completes. My bank confirmed that the transaction request never reaches them. There is no declined charge, no attempt, nothing arrives. The exact same card works normally for purchases on the Apple Store. This tells me the payment is being blocked on Apple's side before it ever leaves, so it is not a card or bank issue. It looks like a backend block tied to my account or enrollment record. Why I am posting publicly: This is the third time I go through the entire process, waiting around three weeks each cycle, and each time it ends at the same payment block. Resetting and retrying clearly does not fix it, since the result is identical every time. An earlier issue where Apple's identity verification read my name incorrectly ("Makcu" instead of "Marco") was already corrected, so that is not the blocker anymore. What I am asking: Could someone with the right access please inspect my account and enrollment record to find why payment is blocked at the backend, and clear it so I can complete a fresh payment? I am happy to pay as many times as needed once the block is removed, and I can provide any additional information through the existing support case. Thank you.

Can someone explain why my account shows pending while ive paid for the developer program?

My app was submitted to the appstore connect via transport. The logs show no errors, the status has been “The App is Processing“ for over a week. I opened a ticket, nobody responded. I called, spoke to support. They could not identify the issue, and escalated. It’s now beed several days and I have had no response. In appstore connect Testflight It shows no build processing.

With visionOS 27, if you use a non US Apple ID, if the language is set to English on the country to USA, you don’t get Siri AI even if Siri AI is supposed to be available on visionOS 27 in all countries if the system is in English. iOS and iPadOS are the only systems where Siri AI is not available in Europe. As macOS, visionOS is supposed to have Siri AI enabled worldwide if the system is configured in English. The problem is confirmed with many French Vision Pro users with a French Apple ID. Feedback: FB23207278

I’ve been experiencing several issues on my iPhone that have become quite frustrating: The device frequently freezes and becomes unresponsive. In many apps, the touch screen suddenly stops responding, and even during typing or chatting, there are noticeable lags and stutters. The camera switching behavior is poor. The camera often jumps between lenses unnecessarily, resulting in an inconsistent and unpleasant experience. A major bug affects screenshots. When I take a screenshot and immediately crop it before saving, the edit appears to be applied successfully. However, when I later open the image in Photos, the screenshot is still the original full-screen version and the crop was not saved. The sticker creation feature in Photos, where users can press and hold an object to create a sticker, performs very poorly. Object detection is often inaccurate, unreliable, and appears to be buggy. These issues significantly affect the overall user experience and should be investigated.

Hi everyone, I am currently completely blocked from submitting my new app for TestFlight Beta Review (External Testing). The App Store Connect web interface fails to submit, and when I try to bypass the UI using the App Store Connect REST API to create a betaAppReviewSubmissions request, Apple's servers return the following 422 error: { "errors" : [ { "status" : "422", "code" : "ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING", "title" : "Beta contract is missing for the app.", "detail" : "Beta Contract is missing." } ] } Here is what I have already checked and verified on my end: Agreements, Tax, and Banking: My "Paid Apps Agreement", "Free Apps Agreement", "U.S. Tax Forms", and "Bank Accounts" all clearly show as "Active" status. There are absolutely no pending banners or unaccepted agreements on developer.apple.com or appstoreconnect.apple.com. Apple Developer App: I logged into the official iOS Apple Developer app with the Account Holder ID, and there are no hidden agreements to accept there either. App Privacy: All data collection questions are answered, and the App Privacy section is fully Published. Test Information: All required Beta App Review details (Name, Email, Phone) are correctly filled. Export Compliance: My Info.plist includes <key>ITSAppUsesNonExemptEncryption</key><false/>, and the build attributes confirm it. It appears that my TestFlight beta contract has somehow become detached, bugged, or failed to provision on Apple's backend. Has anyone experienced this specific API error recently? Is there a way to force the system to re-provision the contract, or does this strictly require manual intervention from an Apple Engineer? Any guidance would be highly appreciated. Thanks!

We’re planning a migration from App Store Server Notifications V1 to V2 and are reviewing our rollback strategy before enabling V2 in production. While researching, we found TN3180: TN3180: Reverting to App Store Server Notifications V1 | Apple Developer Documentation The technote appears to describe reverting App Store Server Notifications from V2 back to V1 using the Modify an App endpoint. Before proceeding, we’d like to clarify a few points: Is V2 → V1 rollback via the Modify App endpoint fully supported for production applications? If an application is reverted from V2 back to V1, can it later be migrated back to V2 again? During a rollback, should developers expect any overlap period where both V1 and V2 notifications may be delivered due to retries or notifications already in flight? Our goal is to understand whether the V2 → V1 capability should be treated as a fully supported operational rollback mechanism or as an emergency recovery path intended only for exceptional situations. Thank you for any clarification.

I generated an Apple Maps API key and Server API test token via Maps services, and checked it has a valid header and payload with jwt. Ive also generated a valid token with my AuthKey_.p8 file via PyJWT, however, I continue to get 401 error returned from my local server when trying to test hitting https://maps-api.apple.com/v1/api/searchAutocomplete?....

Hello, I am writing this out of profound frustration and desperation. My team has worked incredibly hard to build an app that now supports a community of 500,000 users, trusting Apple as a reliable partner. Instead, we are being completely starved of our own capital due to a severe and ongoing failure in Apple’s payout routing, and support is entirely ignoring us. The Timeline of Errors: February 8: Monetization began, and we met the minimum payout threshold within two days. April 9: The app was legally transferred to my developer account from my ex-co-founder. I updated all banking and tax details on my account that exact same day. Payout Failure 1 (April 9): Upon transfer, Apple incorrectly issued our earned revenue to my ex-co-founder’s bank account instead of mine. Thankfully, my former co-founder is cooperative and manually transferred the funds to me. However, this could have created a major financial and legal issue if the previous account holder had not cooperated. Payout Failure 2 (June 4): Despite my banking details being verified and active for two months, Apple againbypassed my account and routed another payout to my ex-co-founder. Worse, the amount sent was only a fraction of the total revenue actually owed. It is now June 10. The 45-day payment cycle logic is completely broken, and funds are actively being sent to an account that no longer owns the application. The Impact: Behind this app are real people. I have employee salaries to pay and personal bills to cover, and my business operations are being suffocated because Apple is withholding our earned revenue. When I call support, representatives tell me they cannot access finance issues and tell me to open another ticket. When I open tickets, I am met with absolute silence. Ignored Support Tickets: Case ID: 20382739 Case ID: 20447730 Could a community manager or moderator please escalate these case IDs to a senior supervisor in Finance? This is extremely frustrating because Apple takes a 30% commission, but I still cannot get clear information or timely access to earned revenue. Thank you.

On iOS/macOS 26, CNAssetSpatialAudioInfo(asset:) and CNAssetSpatialAudioInfo.assetContainsSpatialAudio(asset:) accept a spatial capture only when its spatial track is APAC-encoded which AVCaptureMovieFileOutput produces when the video codec is HEVC. An otherwise-identical ProRes capture, whose spatial track is LPCM (4-channel First-Order Ambisonics, kAudioChannelLayoutTag_HOA_ACN_SN3D | 4), is rejected with CNCinematicErrorDomain code 3 (CNCinematicErrorCodeIncomplete) "no eligible audio tracks in asset". This reproduces with Apple's own SpatialAudioCLI sample run on Apple's own stock iPhone captures, so it appears to be a property of the format/API rather than my code. I'd like to confirm whether this is intended, and find a supported way to obtain Audio-Mix-eligible spatial audio while still recording ProRes video (we use Apple Log/ProRes for color grading). Respectively, is wiring a manual AVAssetWriter setup the only way to manage spatial audio and ProRes video? Eligibility appears to require an APAC-encoded, exactly-4-channel FOA track. Because AVCaptureMovieFileOutput only writes APAC audio for HEVC (ProRes forces LPCM), ProRes spatial captures are never eligible — including Apple's own ProRes stock captures, which SpatialAudioCLI also rejects. Key finding: eligibility seems baked into the native APAC bitstream Starting from an eligible HEVC/APAC file, I used AVAssetReader/AVAssetWriter to re-encode only the FOA track (APAC → LPCM → APAC), leaving the AAC stereo track, the HEVC video, and the timed-metadata track untouched. The structurally-identical output is then rejected (code 3). Preserving the cinematic-audio metadata track is not sufficient. Re-encoding the APAC itself loses eligibility. This suggests the mix metadata that gates eligibility is carried inside the APAC bitstream and is produced only at capture time. Questions Is it intended that ProRes (LPCM FOA) spatial captures are not Audio-Mix-eligible via CNAssetSpatialAudioInfo, while HEVC (APAC FOA) captures are? Is this documented? Where exactly is the eligibility metadata stored — in the APAC bitstream, or in the cinematic-audio timed-metadata track (Re-encoding the APAC while preserving that metadata track still loses eligibility)? Is there any supported way to make an existing LPCM/ProRes FOA capture eligible after the fact (a transcode/encode path that produces the required APAC), or is native capture the only source? Any guidance, or a pointer to documentation, would be greatly appreciated. Thank you. Environment iPhone 16 Pro Max, iOS 26.x; macOS 26.2; Xcode 26.2.

How can I get in touch with Apple Engineering since this doesn’t seem to work despite being told it’s the only way? I made this post in the appropriate forum several days ago. No responses. https://developer.apple.com/forums/thread/834948

I tried to enroll, went thru the whole process, but now I'm stuck on "Enrollement not completed - Your enrollment in the Apple Developper pogram could not be completed at this time." I have raised the issue and contacted Developer Support team but there is no email or response. Can you help me resolve this?

Hey, I've been banging my head against this for a few days now and genuinely can't figure out if it's something on my end or an Apple backend issue. My app has WeatherKit integrated and it works fine in the simulator, but on my physical device I consistently get this in the console: Failed to generate jwt token for: com.apple.weatherkit.authservice Error Domain=WeatherDaemon.WDSJWTAuthenticatorServiceListener.Errors Code=2 "(null)" Things I've already tried and ruled out: WeatherKit capability is enabled in the App ID on developer.apple.com ✓ com.apple.developer.weatherkit = true is in the entitlements file ✓ Removed and re-added the capability in Xcode Signing & Capabilities ✓ Clean Build Folder, fresh install on device ✓ The location coordinates are valid (hardcoded lat/lon in Bavaria) ✓ The weird part is that it's not a location issue — Error Code 2 from WDSJWTAuthenticatorServiceListener suggests the JWT generation itself is failing before any location lookup even happens. I've had this App ID since early this year, WeatherKit was working at some point, and I'm not sure what changed. My fallback to Open-Meteo works fine so the app isn't broken, but I'd like to actually use the API I'm paying for. I also opened a support ticket but got redirected to the forums, so here I am. Anyone else seen this recently or know if there's something on the provisioning side I'm missing?

I’ve been using the Age Assurance support page and related Developer News posts as the source of truth for understanding Apple’s expectations around Age Assurance on Apple platforms: https://developer.apple.com/support/age-assurance/ https://developer.apple.com/news/?id=sg176nne Can anyone from Apple clarify whether anything has recently changed with App Review expectations related to Age Assurance? Specifically, are there any new requirements or updated guidance around implementing technologies like DeclaredAgeRange or PermissionKit? I didn’t see any sessions or announcements that indicated these frameworks are now required but with all of the new child safety announcements I thought I'd ask and document for the developer community. I did see the new sample code for implementing Age Assurance and permissions, but nothing suggesting their use is mandatory for App Store approval. https://developer.apple.com/documentation/declaredagerange/implementing-age-assurance-and-permissions Just trying to confirm whether current guidance remains the same, or if App Review expectations are evolving.