Overview

Hello, We are currently integrating the new Declared Age Range framework to comply with the age assurance requirements (such as the Texas regulatory rollout). We are specifically trying to test the AgeRangeService.RegulatoryFeature.significantAppChangeRequiresParentalConsent flow for minors. The Problem When testing in the Sandbox environment, the consent flow returns a mocked response immediately. While this validates our basic code logic, it does not allow us to test or see the actual end-to-end user experience/UI of the parental consent flow. When we attempt to test this outside of the Sandbox environment on a production build/device to see the true system UI, the AskCenter.ask(PermissionQuestion, in: ...) request fails immediately with the following error: Error: “The user is in a region that does not support this type of ask." UserInfo: {NSLocalizedDescription=The user is in a region that does not support this type of ask., NSLocalizedRecoverySuggestion=Please ensure the user is in an eligible region., NSLocalizedFailureReason=The user must be in a supported region to use this feature.} What We Have Tried Verified that our App Store Connect Sandbox account and test devices are configured correctly according to the "Testing Age Assurance in Sandbox" documentation. Attempted to change the region/location settings on our physical test devices to Texas/US to trigger the real flow, but the production environment still blocks it with the region error. Reviewed existing forum threads (such as 809889 and 809483) where other developers are facing the exact same roadblock without a clear solution. Our Questions Is there any supported way to trigger the full, unmocked system consent UI end-to-end during development/local testing? If changing the device's region settings isn't enough to bypass the production region check for AskCenter, how does Apple determine region eligibility for this specific API during local evaluation? Any insights, workarounds, or configuration steps to properly preview this UI before app submission would be greatly appreciated. Thank you!

My devices are showing a message has not been viewed but I can't find it. I looked through all the messages on my devices and all show viewed. Am using the latest betas on iPhone, iMac, iPad. Any advice?

I created a minimal sample project that reproduces a microphone issue with nearby SharePlay / Window Sharing on Apple Vision Pro. Sample project: https://github.com/JerryNee/mic-demo Screen recording: https://youtu.be/aMj_A_leJWU Issue I first implemented SharePlay through FaceTime and found that local microphone capture was unavailable. That seemed understandable because FaceTime itself uses the microphone. I then moved the app to a nearby SharePlay / Window Sharing session specifically to avoid a FaceTime call, but local microphone capture still fails. Local microphone capture works before starting nearby SharePlay. After starting a nearby SharePlay / Window Sharing session with GroupActivities, the same app fails at: try audioEngine.start() This does not require a FaceTime call. It happens with an in-room nearby SharePlay / Window Sharing session. The screen recording also goes silent when the Share Window UI appears. I checked the MP4 audio track with ffmpeg silencedetect; audio becomes silent at about 00:00:22.60, matching the moment nearby sharing starts: silence_start: 22.600612 silence_end: 55.051927 | silence_duration: 32.451315 Environment Two nearby Apple Vision Pro devices Xcode device list: visionOS 27.0 and visionOS 26.5 Xcode 27.0, build 27A5194q Frameworks: GroupActivities, AVFoundation, Speech Entitlement: com.apple.developer.group-session Microphone and speech recognition permissions granted Steps Run the sample on Apple Vision Pro. Tap Start Listening and speak. Transcription works. Tap Stop Listening. Tap Start Nearby Session. Share with another nearby Apple Vision Pro. Tap Start Listening again while the nearby session is active. audioEngine.start() fails. Ending the nearby session makes microphone capture work again. Minimal microphone code let recognizer = SFSpeechRecognizer() let audioEngine = AVAudioEngine() let request = SFSpeechAudioBufferRecognitionRequest() request.shouldReportPartialResults = true let session = AVAudioSession.sharedInstance() try session.setCategory(.record, mode: .measurement, options: [.duckOthers]) try session.setActive(true) let input = audioEngine.inputNode let format = input.outputFormat(forBus: 0) input.installTap(onBus: 0, bufferSize: 1024, format: format) { buffer, _ in request.append(buffer) } audioEngine.prepare() try audioEngine.start() Minimal nearby SharePlay code struct MicDemoActivity: Codable, GroupActivity, Transferable { static let activityIdentifier = "com.example.mic-demo.nearby-mic-repro" static var transferRepresentation: some TransferRepresentation { CodableRepresentation(contentType: .micDemoActivity) } var metadata: GroupActivityMetadata { var metadata = GroupActivityMetadata() metadata.type = .generic metadata.title = "Mic Demo Nearby Session" return metadata } } for await session in MicDemoActivity.sessions() { session.join() } _ = try await MicDemoActivity().activate() Questions Is local microphone capture expected to be unavailable during a nearby SharePlay / Window Sharing session? Is screen recording audio expected to become silent during nearby sharing? What is the recommended way to support nearby shared UI/state while still allowing local voice input?

Hi everyone, I’m wondering whether anyone else is currently experiencing unusually long App Review delays. My app, LiveTunes, version 4.1.1, was initially rejected under Guideline 1.1 because of wording in the App Store description. The issue was metadata-only. I updated the description across all supported localizations and resubmitted the same build, which Apple allows for metadata corrections. The app then remained in “Waiting for Review” for an unusually long time. I eventually canceled and resubmitted it. Interestingly, the related new in-app purchase, which had also been waiting for review, was approved approximately 10 to 20 minutes after I canceled and resubmitted the app. However, the app itself is still stuck in “Waiting for Review” with no movement. I also submitted a Developer Support request but have not received a response. A few details: • Existing app with a long App Store history • Version 4.1.1 • Same binary that was previously reviewed • Original rejection was for metadata, not the app binary • All requested metadata changes were completed • Associated in-app purchase is now approved • No unresolved messages or required actions appear in App Store Connect • Active subscribers are waiting for the new content in this update Has anyone seen a submission become stuck after a rejection or resubmission like this? Did uploading a fresh build number help, or did it simply restart the waiting period? I’m trying to determine whether this is a current App Review queue issue, a routing issue related to the previous rejection, or something specific to resubmitting the same build. Thanks for any insight.

It would be good if SensorKit was more available for non research related apps. For example I want to create an app that tracks light sensor values to create a mapping of bikelanes with poor lighting. This doesn’t fall under a research app, but seems like a reasonable use of this data. creating a way to opt the user into this (via clear warnings that the data Is being collected, and maybe a 24 or 1 hour time limit) might be a way to make this sensor data available. also clear warnings on the app store privacy page, or maybe even rules about running in the background or at app startup and an icon in the toolbar (similar to the mic) could make this more safe for users.

Hello Apple community I would like to know why new Siri is currently inactive on my phone. I have a iPhone 17 base model and downloaded iOS 27 beta. I suspect that it is not functioning due to me being 13 and having parental controls on. That is my guess why New Siri is not downloading. The phone states that I have joined the waitlist though my stance on the situation is that there is more to this!

I've been unable to enroll in the Apple Developer Program for several weeks. When I navigate to the enrollment page, I'm redirected to a contact form instead of the enrollment flow — this happens for both Individual and Organization enrollment, on multiple browsers and devices. I have an existing support ticket on file and have provided the requested screenshot. The ticket has gone unanswered. Is there anything on the account side that is blocking enrollment from proceeding? If an Apple staff member can look into this, I'm happy to provide my Apple ID and ticket number via direct message.

We been waiting + weeks now onm getting our account verified ? Anyone know whats going on

90338: Non-public API usage. The app references non-public symbols in TrustAPP: __ZN3re210chartoruneEPiPKc, __ZN3re210runetocharEPcPKi, __ZN3re211perl_groupsE, __ZN3re212posix_groupsE, __ZN3re214unicode_groupsE, __ZN3re215num_perl_groupsE, __ZN3re216CharClassBuilder11RemoveAboveEi, _ZN3re216CharClassBuilder12AddCharClassEPS0, __ZN3re216CharClassBuilder12GetCharClassEv, __ZN3re216CharClassBuilder6NegateEv, __ZN3re216CharClassBuilder8AddRangeEii, __ZN3re216CharClassBuilder8ContainsEi, __ZN3re216CharClassBuilderC1Ev, __ZN3re216num_posix_groupsE, __ZN3re216unicode_casefoldE, __ZN3re218num_unicode_groupsE, __ZN3re220num_unicode_casefoldE, __ZN3re26Regexp11NumCapturesEv, __ZN3re26Regexp13CompileToProgEx, __ZN3re26Regexp13ComputeSimpleEv, __ZN3re26Regexp15AddRuneToStringEi, __ZN3re26Regexp17ConcatOrAlternateENS_8RegexpOpEPPS0_iNS0_10ParseFlagsEb, __ZN3re26Regexp20CompileToReverseProgEx, __ZN3re26Regexp6DecrefEv, __ZN3re26Regexp6IncrefEv, __ZN3re26RegexpC1ENS_8RegexpOpENS0_10ParseFlagsE, __ZN3re28fullruneEPKci. If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed. I installed the Didit SDK in the project and now the build doesn't go to TestFlight, as it did above. What could be the problem?

I have an existing app that uses NavigationSplitView with a detail view that is never changed and just updates to show changes in data. All navigation changes the sidebar only using NavigationLinks with .isDetailLink(false). Now I'm wanting to use NavigationPath with a simple router and enums. import SwiftUI @main struct NavRouterApp: App { @State private var router = Router() var body: some Scene { WindowGroup { NavigationStack(path: $router.navPath) { ContentView() .navigationDestination(for: AppRoute.self) { route in switch route { case .citizens: ContentView() .environment(router) case .citizen: EmptyView() .environment(router) case .tasform2: TASForm2View() .environment(router) case .start: StartView() .environment(router) case .editcharacteristics: EmptyView() .environment(router) case .basicdata(let citizen): BasicDataView(citizen: citizen) .environment(router) .navigationBarBackButtonHidden(true) case .characteristics: EmptyView() .environment(router) } } } .environment(router) } } } The problem is that pushing a subview now replaces the entire content instead of just the sidebar. Pushing a subview with NavigationSplitView would update the sidebar as desired but I would have to replace the detail view, which is not a good idea. I haven't been able to find any way to accomplish what I want. Suggestions?

I am a paid apple developer that has been on the AI waitlist since day one of the keynote. How many other paid developers are still waiting like me?

While running my application on macOS 27 today, it crashed in a strange way. The backtrace for the thread that crashed looks like it was some kind of Spotlight search indexing thread. The strange part is that my app makes no use of Spotlight and is not mentioned anywhere in the Spotlight section of System Prefs. Here is the backtrace, maybe something in here is enough of a clue as to what happened and why my App was running a Spotlight-related thread. This was on 27 beta 1 (26A5353q), and the app is a video streaming app that uses both Qt 6.11.1 and SDL 3 and was rendering some frames with Metal at the time. The most unusual thing in the backtrace is the existence of ObjC params spelled both updatingDonationProgress as well as updatingDonationProgres. Thread 8 Crashed:: Dispatch queue: com.apple.root.user-initiated-qos 0 libobjcMsgSend.dylib 0x19e7f0808 objc_msgSend + 8 1 CoreFoundation 0x1970fe300 __NSSetM_new + 368 2 CoreFoundation 0x19711cd64 -[NSSet initWithArray:range:copyItems:] + 304 3 LaunchServices 0x1976bc144 -[_LSLocalizedStringRecord _missingBundleLocsWithContext:tableID:unitID:unitBytes:] + 104 4 LaunchServices 0x197700628 objc_object* __strong __LSRECORD_GETTER__<objc_object* __strong>(LSRecord*, objc_selector*, objc_selector*) + 288 5 LaunchServices 0x1976bc854 -[_LSLocalizedStringRecord _detachFromContext:tableID:unitID:unitBytes:] + 68 6 LaunchServices 0x197701cac -[LSRecord detach] + 240 7 LaunchServices 0x197773720 -[UTTypeRecord _detachFromContext:tableID:unitID:unitBytes:] + 68 8 LaunchServices 0x1977756fc -[_UTDeclaredTypeRecord _detachFromContext:tableID:unitID:unitBytes:] + 52 9 LaunchServices 0x197701cac -[LSRecord detach] + 240 10 LaunchServices 0x197702c74 +[LSRecord(LSDetachable) resolveAllPropertiesOfRecords:count:andDetachOnQueue:] + 392 11 UniformTypeIdentifiers 0x19cd1bc80 +[UTType _typeWithTypeRecord:detachTypeRecord:findConstant:installInConstant:] + 232 12 UniformTypeIdentifiers 0x19cd19d38 _UTTypeGetForIdentifier(NSString*, bool) + 148 13 SpotlightKnowledge 0x2a7596adc -[SKGProcessor(EmbeddingsUtils) needsEmbeddingsForRecord:bundleID:] + 604 14 SpotlightKnowledge 0x2a7590bd4 -[SKGAttributeProcessor processorAttributesForRecord:bundleID:protectionClass:isUpdate:] + 500 15 CoreSpotlight 0x1a79bfa84 -[CSSearchableItemAttributeSet(CSPrivateAttributes) _standardizeProcessorAttributesForBundle:protectionClass:isUpdate:] + 292 16 CoreSpotlight 0x1a79b11a4 -[CSSearchableItem(Internal) standardizeAttributesForBundle:protectionClass:] + 780 17 CoreSpotlight 0x1a799f218 __39-[CSSearchableIndex _standardizeItems:]_block_invoke + 248 18 CoreFoundation 0x19712e56c __NSARRAY_IS_CALLING_OUT_TO_A_BLOCK__ + 24 19 CoreFoundation 0x197277604 ____NSCollectionHandleConcurrentEnumerationIfSpecified_block_invoke + 116 20 libdispatch.dylib 0x196ed45d4 _dispatch_client_callout2 + 16 21 libdispatch.dylib 0x196ecf2d4 _dispatch_apply_invoke3 + 336 22 libdispatch.dylib 0x196ed45bc _dispatch_client_callout + 16 23 libdispatch.dylib 0x196ebd624 _dispatch_once_callout + 32 24 libdispatch.dylib 0x196ecf974 _dispatch_apply_invoke_and_wait + 364 25 libdispatch.dylib 0x196ecea70 _dispatch_apply_with_attr_f + 1312 26 libdispatch.dylib 0x196ecebf4 dispatch_apply + 96 27 CoreFoundation 0x197277548 __NSCollectionHandleConcurrentEnumerationIfSpecified + 184 28 CoreFoundation 0x19712e350 -[__NSArrayM enumerateObjectsWithOptions:usingBlock:] + 188 29 CoreSpotlight 0x1a78d99b4 -[CSSearchableIndex _standardizeItems:] + 144 30 CoreSpotlight 0x1a799d4b0 -[CSSearchableIndex indexSearchableItems:deleteSearchableItemsWithIdentifiers:clientState:expectedClientState:clientStateName:updatingDonationProgress:protectionClass:forBundleID:options:reason:completionHandler:] + 824 31 CoreSpotlight 0x1a799d024 -[CSSearchableIndex indexSearchableItems:deleteSearchableItemsWithIdentifiers:clientState:expectedClientState:updatingDonationProgress:protectionClass:forBundleID:options:reason:completionHandler:] + 52 32 CoreSpotlight 0x1a799ca64 __131-[CSSearchableIndex endIndexBatchWithExpectedClientState:newClientState:critical:reason:updatingDonationProgres:completionHandler:]_block_invoke + 188 33 libsystem_trace.dylib 0x196d957e8 _os_activity_initiate_impl + 64 34 CoreSpotlight 0x1a799c91c -[CSSearchableIndex endIndexBatchWithExpectedClientState:newClientState:critical:reason:updatingDonationProgres:completionHandler:] + 448 35 AppKit 0x19c7a3568 0x19b5b6000 + 18797928 36 AppKit 0x19c4d8584 0x19b5b6000 + 15869316 37 libdispatch.dylib 0x196ebaa30 _dispatch_call_block_and_release + 32 38 libdispatch.dylib 0x196ed45bc _dispatch_client_callout + 16 39 libdispatch.dylib 0x196ec3018 _dispatch_lane_serial_drain + 744 40 libdispatch.dylib 0x196ec3b4c _dispatch_lane_invoke + 448 41 libdispatch.dylib 0x196ecdf70 _dispatch_root_queue_drain_deferred_wlh + 284 42 libdispatch.dylib 0x196ecd874 _dispatch_workloop_worker_thread + 720 43 libsystem_pthread.dylib 0x197076f78 _pthread_wqthread + 292 44 libsystem_pthread.dylib 0x197075cc4 start_wqthread + 8

I am unable to enroll for an unknown reason. When I go to enroll, I get the message Your enrollment could not be completed.". I've contacted support via email, I went through the standard troubleshooting, I then submitted my documentation/identity verification as requested, but I have not heard anything since. That was four weeks ago. Can someone from apple support please look into my case?

Hi, My subscription is getting rejected as need developer attention with no reason. May I please know where to look for rejected reasons. I am not able to find anything on screen and no email from apple as well. Apprectiate the help. Thanks Vinny

Hello, I have a question about App Intents and the Action button on iPhone. I have an App Intent that opens the app and navigates to a specific entity, conforming to OpenIntent with a single AppEntity parameter. The entity conforms to EnumerableEntityQuery, and the intent is registered as an App Shortcut via the AppShortcutsProvider. When assigning this shortcut to the Action button in Settings, the system doesn’t prompt the user to select a default entity upfront. Instead, it prompts on every activation, creating friction. In contrast, shortcuts like “Open Note…” and other third-party ones prompt the user for a note to open when setting up the Action button, and its title also includes three dots, indicating a pre-configurable parameter. My shortcut’s title shows no dots. What’s required to make an App Shortcut prompt for a default parameter during Action button setup? Sincerely, Holger

Anyone else seeing a lot more "Class X is implemented in both ..." warnings on Xcode 27 than on Xcode 26? Same source, same flags, the count goes from a handful to a couple thousand, and some now correlate with real crashes (cast failures, missing protocol conformances) instead of the usual harmless first-wins behavior. Is this a known change in Swift 6.4 / Xcode 27? Is there a new flag I should be passing? Any suggestions welcome.

Its been 2 days now? What am I missing?

iOS 27.0 beta 24A5355q has a completely unacceptable Settings crash that blocks Wi-Fi Calling activation and E911 emergency address setup. This is not some tiny visual bug. This breaks actual phone service. I cannot activate Wi-Fi Calling, I cannot register my 911 emergency address, and my SIM line is effectively unusable because Apple shipped a broken beta Settings app. Process: Preferences / com.apple.Preferences Device: iPhone16,1 Crash type: NSInvalidArgumentException Reason: -[UIThreadSafeNode _smartReplyUpdateInProgress]: unrecognized selector sent to instance The stack points to Apple’s own code: UIPredictionViewController UIKeyboardImpl TextInputUI UIKeyboardLayoutJapanese50OnFlick I tried Bluetooth keyboard, disabling prediction, removing keyboards, rebooting, and avoiding text input. Nothing works. The Wi-Fi Calling / Emergency Address page crashes on load. This is a stupid, critical Apple bug. Settings should never crash when opening a carrier service page, and it is insane that a broken prediction UI can block emergency-address registration and phone service activation. Please fix this immediately, or provide a way to configure Wi-Fi Calling E911 address without loading the broken TextInputUI / prediction UI path.

On iOS 26, a Simulator screen recording shows the bottom corners of content go from rounded to square during normal push and sheet transitions. This happens on the simulator, but I don't see this on a real iPhone. Steps to reproduce: Create a new SwiftUI app and use the attached content view. Run on an iOS 26 Simulator. Start a Simulator screen recording. Tap a row to push, and tap "Filter" to present the sheet. Stop the recording and play it back frame by frame. Run the same app on a real iPhone and watch the transitions live. Question: Is this a new feature or a simulator bug? Configuration: Xcode 26.4.1 iOS 26 Simulator — iPhone 17 Pro Real device: iPhone 16 Pro Max Attachments: ContentView

Hi there, not sure anyone encountered the same situation, we rolled out our feature and we found that flag is all false for all the users in Brazil.. super weird.. anyone has any idea?