Overview

I’m trying to integrate Apple’s Translation framework in a Swift 6 project with Approachable Concurrency enabled. I’m following the code here: https://developer.apple.com/documentation/translation/translating-text-within-your-app#Offer-a-custom-translation And, specifically, inside the following code .translationTask(configuration) { session in do { // Use the session the task provides to translate the text. let response = try await session.translate(sourceText) // Update the view with the translated result. targetText = response.targetText } catch { // Handle any errors. } } On the try await session.translate(…) line, the compiler complains that “Sending ‘session’ risks causing data races”. Extended error message: Sending main actor-isolated 'session' to @concurrent instance method 'translate' risks causing data races between @concurrent and main actor-isolated uses I’ve downloaded Apple’s sample code (at the top of linked webpage), it compiles fine as-is on Xcode 26.4, but fails with the same error as soon as I switch the Swift Language Mode to Swift 6 in the project. How can I fix this?

We are facing an issue where our App Clip card appears when scanning the QR code, but displays “App Clip Unavailable” even though the main app is already live on the App Store. App Details • App Name: ExpRE – Experiencing Reality • Main App Bundle ID: com.livingmedia.adplayer • App Clip Bundle ID: com.livingmedia.adplayer.Clip • Apple ID: 6758887250 • Team ID: 9NU8HZB68A Current Status: • Main app status: Ready for Distribution (visible on App Store) • App Clip Advanced Experience status: Received • App Clip Experience URL: https://aaj-tak-test-app.web.app Issue Description When scanning the QR code linked to the App Clip Experience: • The App Clip card with image appears • But the card shows the message: “App Clip Unavailable” Additional Observations • The default App Clip link opens correctly: https://appclip.apple.com/id?p=com.livingmedia.adplayer.Clip • Advanced App Clip Experience status still shows “Received”. • Also if there is testflight build then clip card work. But fresh install with QR with link show App clip Unavailable in card. Question Is there an additional propagation or approval step required after the status becomes Received for Advanced App Clip Experiences? How long does it typically take for the App Clip to become publicly available after the main app is released? In iphone developer I checked with Diagnostics in App clip testing.

We've been stuck without an approval of our app since Feb 3. and we are desperate for any help. We need our build approved. The history: Submitted build on 2/3 Sat in 'Waiting for Review' for 6 day Cancelled and resubmitted on 2/9 Sat in 'Waiting for Review' for 15 day (called multiple times and was told that there wasn't anything they could do) Cancelled and resubmitted on 2/25 App rejected about 6 hours later with a note that said basically "You have this small issue on iPad. You can fix it in your next build just let us know.' We responded immediately that we would fx it in our build and to please approve the build. No response since we responded more than 3 days ago We are absolutely desperate to get this build approved. It has been nearly a month and this is destroying our company. It is impossible to understate how hard this been for us. Does anyone know any way of trying to resolve?

Hello, I am writing to ask for assistance regarding two of my apps that have been stuck in “Waiting for Review” for an extended period. At the moment: App ID 6497716649 — Waiting for Review since Feb, 19 at 11:45 AM App ID 6743224713 — Waiting for Review since Feb, 15 at 10:26 PM There are no warnings, Resolution Center messages, or visible issues in App Store Connect. All Agreements, Tax, and Banking information are active and up to date. The builds were uploaded successfully, and no further action appears to be required on my side. Could you please help confirm: Whether there is any hidden blocker or account-related issue? Or if this delay is currently due to review queue processing times? If additional details are needed (bundle IDs, app category, sign-in requirements, encryption/export compliance, etc.), I will be happy to provide them immediately. Thank you very much for your time and support. Best regards,

On february 9, I tried to enroll to the developer program, I got charged and received and order number, the next day when I tried to see the status of the enrollment, the order number provided on the email confirming the order was not working, I've tried to get support through email, nothing happens; I've called about 20 times to Apple Support, nothing happens, they said they doesn't have direct communication to the Apple Developer department, I have two weeks plus trying to have an answer on email, and nothing happens, but you know what happened? They completed the charge on my CC.

Hello everyone, I’m facing an unusually long app review delay and would appreciate any insight from the community. My app has been stuck in the "Waiting for Review" status since February 10, 2026, with no updates or feedback. App details: App ID: 6756574744 Case Number: 102824473424 During this time, I have: Submitted several support requests Filed multiple expedited review requests Tried contacting through email and the support section Attempted to follow up on the case status Despite all of these efforts, I have not received any response, acknowledgment, or update regarding its review progress. I understand that review times can vary, and delays sometimes happen. What concerns me more is the complete lack of communication. At this point, it feels like the app might be stuck in the queue. Has anyone else experienced long "Waiting for Review" times recently? Is there anything else I can do to get clarification or make sure the submission is not blocked for some reason? Thanks in advance for any insight!

Hi, Is there a resource or sample code about how to draw an outline around a mesh in RealityKit? Typically, this is useful for visualizing a selection, like in Reality Composer Pro. How to achieve such effect? A shader material? A post-process effect in ARView or RealityRenderer? Methods such as duplicating the entity mesh, scaling it, and using material.faceCulling = .front did not look good in my experiments. Thank you.

I keep getting a fails to open page message when I try to sign in using my Claude ai Pro account. The request was for an http url instead of an https url.

Hi, I’m implementing ePassport reading in an iOS app using a third-party KYC identity verification SDK (the SDK handles the NFC logic internally). Before adding any specific AID, the NFC session would start normally and iOS showed the system popup asking the user to hold the passport near the device. However, the passport was never read , the session just stayed there with no progress or data returned. I then tried enabling the ICAO ePassport AID: A0000002471001 After adding this, the build failed with the following signing error: Provisioning profile "iOS Team Provisioning Profile: com.sandrotbilisi.DigitalCurrency" doesn't include the com.apple.developer.nfc.readersession.iso7816.select-identifiers entitlement. Has anyone encountered this behavior when working with ePassports? Do I need special entitlement approval from Apple for this AID? Thank you.

I’m building an iOS app where real money moves based on goal completion results, including transfers between users. I need a real money flow that supports top ups, internal balance updates, and withdrawals. I’m launching in the EU first and want to avoid building the wrong architecture from the start. I’d appreciate practical guidance from anyone who has shipped similar apps: When can external payment processors be used for real money flows? If users can withdraw real money, what compliance requirements are usually needed first? Is it as complicated as I think? This is my first project of this kind, so I want to approach it correctly. Thank you in advance.

I’m looking for advice from anyone who has gone through the process of converting an Apple Developer account to an Organization / Company account. I’ve been trying to convert my account for organization and the process has been taking much longer than expected. Apple initially requested documentation to verify both the business and my authority to act on behalf of the company. So far, I have already provided or prepared everything they ask for. At this point, I’ve been waiting for 9 days without much clarity on whether my documents are sufficient

I'm facing an issue with Xcode Cloud. Every branch I push to my GitLab repository is not appearing as selectable when I try to create a build with my workflow. Additionally, if I try to update the workflow from Xcode, it crashes every time I save the changes. Any help would be appreciated. Translated Report (Full Report Below) ------------------------------------- Process: Xcode [32110] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 26.2 (24553) Build Info: IDEApplication-24553000000000000~2 (17C52) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.apple.dt.Xcode [58945] User ID: 501 Date/Time: 2026-02-19 13:11:54.9987 -0600 Launch Time: 2026-02-19 13:03:37.7725 -0600 Hardware Model: Mac16,5 OS Version: macOS 26.2 (25C56) Release Type: User Crash Reporter Key: 61D7E2DA-E724-EFE2-6A01-25079BFCA2D1 Incident Identifier: B3D4A277-7CB5-4696-A00F-057929659F41 Sleep/Wake UUID: 2D4F6C41-716C-4B47-8D40-27FD2D74A8AE Time Awake Since Boot: 440000 seconds Time Since Wake: 15967 seconds System Integrity Protection: enabled Triggered by Thread: 9, Dispatch Queue: com.apple.root.user-initiated-qos.cooperative Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6, Abort trap: 6 Terminating Process: Xcode [32110] Application Specific Information: abort() called Thread 0:: Dispatch queue: com.apple.main-thread 0 AppKit 0x19ffb8250 __51-[NSWindow(NSDisplayCycle) _postWindowNeedsDisplay]_block_invoke + 0 1 CoreFoundation 0x19afe4604 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 28 2 CoreFoundation 0x19afe4544 __CFRunLoopDoBlocks + 396 3 CoreFoundation 0x19afe3988 __CFRunLoopRun + 2356 4 CoreFoundation 0x19b09de34 _CFRunLoopRunSpecificWithOptions + 532 5 HIToolbox 0x1a7ad3790 RunCurrentEventLoopInMode + 316 6 HIToolbox 0x1a7ad6ab8 ReceiveNextEventCommon + 488 7 HIToolbox 0x1a7c60b64 _BlockUntilNextEventMatchingListInMode + 48 8 AppKit 0x19f8fcb5c _DPSBlockUntilNextEventMatchingListInMode + 236 9 AppKit 0x19f3f6e48 _DPSNextEvent + 588 10 AppKit 0x19fec1d0c -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688 11 AppKit 0x19fec1a18 -[NSApplication(NSEventRouting) nextEventMatchingMask:untilDate:inMode:dequeue:] + 72 12 AppKit 0x19f3ef780 -[NSApplication run] + 368 13 IDEKit 0x10cf3f630 -[IDEApplication run] + 192 14 AppKit 0x19f3db6dc NSApplicationMain + 880 15 dyld 0x19ab7dd54 start + 7184 Thread 1:: com.apple.NSEventThread 0 libsystem_kernel.dylib 0x19af02c34 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x19af15028 mach_msg2_internal + 76 2 libsystem_kernel.dylib 0x19af0b98c mach_msg_overwrite + 484 3 libsystem_kernel.dylib 0x19af02fb4 mach_msg + 24 4 CoreFoundation 0x19afe4ba0 __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x19afe34f8 __CFRunLoopRun + 1188 6 CoreFoundation 0x19b09de34 _CFRunLoopRunSpecificWithOptions + 532 7 AppKit 0x19f486a34 _NSEventThread + 184 8 libsystem_pthread.dylib 0x19af45c08 _pthread_start + 136 9 libsystem_pthread.dylib 0x19af40ba8 thread_start + 8 Thread 2: 0 libsystem_kernel.dylib 0x19af02c34 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x19af15028 mach_msg2_internal + 76 2 libsystem_kernel.dylib 0x19af0b98c mach_msg_overwrite + 484 3 libsystem_kernel.dylib 0x19af02fb4 mach_msg + 24 4 CoreFoundation 0x19afe4ba0 __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x19afe34f8 __CFRunLoopRun + 1188 6 CoreFoundation 0x19b09de34 _CFRunLoopRunSpecificWithOptions + 532 7 Foundation 0x19d232964 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 212 8 DTDeviceKitBase 0x118331930 +[DTDKRemoteDeviceConnection startServiceBrowsers] + 148 9 Foundation 0x19c7fd7a0 __NSThread__start__ + 732 10 libsystem_pthread.dylib 0x19af45c08 _pthread_start + 136 11 libsystem_pthread.dylib 0x19af40ba8 thread_start + 8

[Note: this issue was happening on a main testing device, and after testing the same code on other devices, this issue is only happening on 1 out of 4 devices] We are successfully getting a MusicCatalogResourceResponse for every song ID where we make the MusicCatalogResourceRequest. We are able to display the song title, artist name, and album artwork for each Song in the response. However - when we go to play the song, there are some songs that play, and several songs that do not play. For the songs that don't play, the console shows “Failed to prepareToPlay error=<MPMusicPlayerControllerErrorDomain.6 "Failed to prepare to play" {}>” let musicPlayer = ApplicationMusicPlayer.shared func playSong(_ song: Song) { musicPlayer.queue = [song] Task { try await musicPlayer.prepareToPlay() try await musicPlayer.play() } Is there anything else we can investigate about what may be causing specific song IDs not to play on this specific device? Even if we remove line 6 musicPlayer.prepareToPlay() we still see the same console error when running playSong with the Songs that don't work. It is always the same song IDs that we can play and always the same song IDs that we cannot get to play, even trying them across different projects with different bundle identifiers. We can tap to play a song that works, and it starts playing immediately. Then tap a song that doesn't work, and nothing happens. Then back to a song that works. It's consistent which songs succeed and fail on this device. Perhaps there is an issue specific to this very iPad when it comes to certain specific songs, but we'd like to be confident that an app relying on MusicKit will be able to play songs that have been successfully loaded with a MusicCatalogResourceResponse. Thanks for any help or suggestions about what we may be able to investigate further on the device or what we should consider when launching an app that expects anyone with Apple Music to be able to listen to any of the songs loaded by the app. Specific iPad details: iPad Pro (12.9-inch) (6th generation) running iPadOS 26.4 Beta Two of the song IDs that won't play on this iPad (even though we can access and display their album artwork and all other information): 943204000 and 1441164805

Hello, I am trying to enroll in the Apple Developer Program, but I cannot complete the payment. During the purchase process, I receive the following error: We are unable to complete your order. There was an issue when we processed your order. An invalid value '1549' was provided for State, Province, or Region. My details: Country: Kosovo State/Province/Region: Kosovo Region (selected from the available option) I have verified my information multiple times, but the error appears every time. I have contacted Apple Developer Support multiple times over the past month.I have not received any response (positive or negative). I need to complete enrollment to publish my apps, and this delay is blocking my work.

Since purchasing my 17 Pro, CarPlay has been an abysmal failure. I’m happy to say since installing 26.4 developer beta, it seems to be working much better.

Hi all, The SSDC states: Challenge submissions are due by Saturday, February 28, 2026, at 11:59 p.m. PST I am curious does this apply to local timezone? I am GMT+0, so would this mean the deadline for GMT+0 is on the 1st of March at 7:59AM? Kind regards, Adam

We're handling our universal links (deep links) via our custom router written in express.js. We recently update our .well-known format as per: https://developer.apple.com/documentation/xcode/supporting-associated-domains Our own domain link shows them correctly if we apply cache bust to it: Normal link: https://links.sastaticket.pk/.well-known/apple-app-site-association Cache bust: https://links.sastaticket.pk/.well-known/apple-app-site-association?1 Now, since app-site cache is not updating at: https://app-site-association.cdn-apple.com/a/v1/links.sastaticket.pk Our main domain link is not getting updated response either. Its been more than 72 hours now. Any help, how to push the app-site cache to update? I can provide more context if needed, Thanks

Description On macOS, system-level autocomplete suggestions appear in <textarea> elements even when all relevant HTML attributes intended to disable autocomplete and text assistance are explicitly set. Is this behavior intentional, or is there any supported way for developers to control or disable this functionality? Steps to Reproduce Send yourself an email using the native macOS Mail app containing a verification code (for example). Focus an HTML <textarea> element in any web application. Focus the textarea. Expected Result The autocomplete popup should be controllable from the code, and it should be possible to fully disable it using standard HTML attributes or browser APIs. Actual Result The system autocomplete popup appears in all cases and cannot be controlled or disabled by the code, even when all known attributes (autocomplete="off", autocorrect="off", autocapitalize="off", spellcheck="false") are set.

Hey, I've noticed that in some scenarios photo data can be corrupted from the cameras on iPhone 17 Pro. The requirements are: The zoom level is greater than 2 times the base zoom, so 2x for the wide lens, and 8x for the telephoto. QualityPrioritization is set to .Quality. If set to .Balanced the images look as expected. The scene is well lit. I haven't managed to work out if there's an ISO cut off, but in darker scenes the images look as expected. The scene does not contain any objects or texture, e.g. a blank white screen, a blue sky, up close against a bright wall. Here is an example: This is really weird behavior. I have opened a ticket here: https://feedbackassistant.apple.com/feedback/22092908 There's also a repo here if anyone would like to try it: https://github.com/alexfoxy/CameraQualityTest. Thanks, Alex

For apps, I can select a base price and region (currency) so that prices for other regions adapt automatically, but for app packages I can only set a base price in USD. I just noticed that my app package wasn't visible on the App Store anymore because of an automatic price change which caused its price in USD to become invalid (too low), as it was below the highest app price within the package. Is it intended that I have to monitor price changes and manually correct prices for app packages? I created FB22093289.