Overview

I am working on Screen Record function in Apple Vision Pro, when I use broadcast upload extension, after I click record button, the XCode console show the exception: <<<< FigAudioSession(AV) >>>> audioSessionAVAudioSession_CopyMXSessionProperty signalled err=-19224 (kFigAudioSessionError_UnsupportedOperation) (getMXSessionProperty unsupported) at FigAudioSession_AVAudioSession.m:606 we create and config the project as flow: Create a Apple Vision Project. Create a Broadcast Upload Extension Target. Add App Group for Project Target and Extension Target, both use the same identifier. Add "Main Camera Access", "Passthrough in Screen Capture" Capabilities for all targets. Add "NSScreenCaptureUsageDescription", "NSMicrophoneUsageDescription" in Plist. Add record button in view Run debug in Apple Vision Pro device, after click record button, throw the exception.

Our Application [7 Dawns: Echoes] was recently rejected by the App Store for Guideline 4.3 Apple ID:6753892922 Bundle ID:com.ark.jylhgl.ios Change of Operating Entity Our company, has obtained exclusive global operating rights (excluding Mainland China, Hong Kong, Macau, Taiwan, and certain regions of South Korea) from the copyright owner. The previous distributor’s version, Eternal Sword M (App ID 1369681345, Bundle ID com.emagroups.ea2), has been fully removed from the App Store. Our cooperation with them officially ended on December 29, 2023. New Version Updates This submission is not a duplicate, but a newly operated and updated version. We introduced new gameplay systems (7-day seasonal competitive mode, team-based PvP, dispatch and multi-pet strategy systems), optimized monetization and in-game economy, and improved performance and UI (including redesigned app icon and key interfaces). Evidence Submitted We have provided the Operating Authorization Letter and Software Copyright Certificate via App Store Connect and email to the review team. and we have submitted Review Support but no reply!

We're trying to switch from using main camera access on Arkit to screen-capture with passthrough however we're facing some issues and it seems a bit complicated to debug. We have set up a broadcast Extension, set up some logs on the sample Handler but we get nothing in the console nor that the recording starts, we set up the picker as well and we can see our extension in the control center as one of the choices but clicking start, results in it stopping in less than one second after. The only message that is rather contradictory we see in the console.app is the following [INFO] -[RPRecordingManager getSystemBroadcastExtensionInfo:]_block_invoke:1333 Extension has passthrough license and just right after [INFO] -[RPRecordingManager getSystemBroadcastExtensionInfo:]_block_invoke:1336 Extension does not have passthrough license

When I distribute my app, is it possible for it to be approved by apple when not complete, maybe with reduced levels. Once I add more levels, I release another update? Would apple approve my app with reduced levels, or would they say ot enough content.

Good afternoon, everyone! I received a notification that my app was rejected for the following reason: "We noticed that the user is taken to the default web browser to sign in or register for an account, which provides a poor user experience." The app is a directory of partners that offer a benefit to our members. So the intent of the app is for users that are already registered with our nonprofit to access their benefits using existing account credentials. (Note: The sign-in itself is handled within the app after the account is created.) Is there any way to make this compliant with guidelines without having to offer a duplicate registration form within the app and sync them?

I understand that private APIs are not permitted under Apple’s App Review Guidelines. However, our application requires I²C communication, and we are currently considering the following APIs: IOAVServiceReadI2C IOAVServiceWriteI2C IOI2CSendRequest Could you please confirm: Is there any provision to use these APIs in a Mac App Store–approved application? Are there public alternatives available for achieving I²C communication on macOS? Thank you for your guidance.

Hello everybody. I need your help with configuring navigationItem properly. I want to use its appearance properties to configure how the navigation bar looks on per-screen basis without interacting with UINavigationBar directly (the API has been implemented for this specific use case, right?) What I'm confused about is that setting any appearance property resets back button image to the default chevron. What I do now: Inside my app delegate let navigationBarAppearance = UINavigationBar.appearance() navigationBarAppearance.backIndicatorImage = UIImage() navigationBarAppearance.backIndicatorTransitionMaskImage = UIImage() I do this to hide the default chevron to customize back button appearance on per-view-controller basis Then in my presenting view controller: override func viewDidLoad() { super.viewDidLoad() navigationItem.title = "Root" navigationItem.backBarButtonItem = UIBarButtonItem( title: nil, image: nil, primaryAction: UIAction( title: "", image: UIImage(systemName: "square.and.arrow.up"), identifier: nil, discoverabilityTitle: nil, attributes: [], state: .on, handler: { [weak self] _ in self?.navigationController?.popViewController(animated: true) } ), menu: nil ) let appearance = UINavigationBarAppearance() appearance.configureWithTransparentBackground() appearance.backgroundColor = UIColor.red appearance.titleTextAttributes = [ .foregroundColor: UIColor.purple ] appearance.largeTitleTextAttributes = [ .foregroundColor: UIColor.purple ] navigationItem.standardAppearance = appearance navigationItem.compactAppearance = appearance navigationItem.scrollEdgeAppearance = appearance navigationItem.compactScrollEdgeAppearance = appearance } The colors are set up as expected, however the default chevron image appears on the next view controller next to square.and.arrow.up. If I don't touch navigation item appearance properties - only square.and.arrow.up is displayed, as I want, but obviously I loose all the customization. Can anyone please explain how to set things up properly? Thanks!

I’m writing to report a serious usability regression in the iOS 26 Photos app. Folders can still be created and albums can still be assigned to them, but folders can no longer be opened to view the albums they contain. A container that cannot be opened is not a container, and this breaks a fundamental information architecture model that has existed in Photos for well over a decade. This change disproportionately harms users who maintain large, intentional photo libraries—travel archives, projects, professional work, or long-term personal documentation—where hierarchy and ordering are essential. Search and automated surfacing are not substitutes for deliberate structure. Removing the ability to browse folder → album hierarchy on iOS strips users of control while still exposing the UI for folder creation, which is internally inconsistent. If this behavior is intentional, it should be clearly documented and the folder UI removed to avoid misleading users. If it is not intentional, it needs urgent correction. At minimum, iOS should retain parity with macOS Photos for basic navigation of folders and albums. This is not a niche request; it is a regression in core functionality.

Got new iPhone Boxing Day all works bar image playground uninstalled/reinstalled turns ai on/off still stuck

It seems I was able to previously download a Disk Image (.dmg) file to install macOS High Sierra. However, I'm now having trouble finding where to download the resource. Any guidance would be greatly appreciated.

Hi, My name is incorrectly displayed in the Individual / Tax Forms section as MarkF Frelly, while my legal name is Mark Frelly (example name). It looks like an extra “F” was mistakenly added, possibly treated as a middle initial. My account name shows correctly as Mark Frelly, but the team name and tax name are uneditable, and I’m concerned this could cause issues with tax forms. I’m unable to find any option to correct this myself. Has anyone faced this before, or is contacting Apple Developer Support the only way to fix it?

Is there any way for an iOS app to get a log of all Airdrop transfers originating in all apps on the iOS device e.g. from the last week?

Description The Shortcut Automation Trigger Transaction frequently times out, ultimately causing the shortcut automation to fail. Please see the attached trace for details. Additionally, the Trigger is activated even when the Transaction is declined. Details In the trace I see the error: [WFWalletTransactionProvider observeForUpdatesWithInitialTransactionIfNeeded:transactionIdentifier:completion:]_block_invoke Hit timeout waiting for transaction with identifier: <private>, finishing. Open bug report: FB14035016

If an app is rated 4+, does it have any additional obligation due to the SB2420 beyond this rating on the AppStore ?

Using SwiftUI on macOS, how can I add a toolbar item on the right-most (trailing) edge of the window's toolbar when an Inspector is used? At the moment, the toolbar items are all left-of (leading) the split view tracking separator. I want the inspector toolbar item to be placed similar to where Xcode's Inspector toolbar item is placed: always as far right (trailing) as possible. NavigationSplitView { // ... snip } detail: { // ... snip } .inspector(isPresented: $isInspectorPresented) { InspectorContentView() } .toolbar { // What is the correct placement value here? ToolbarItem(placement: .primaryAction) { Button { isInspectorPresented.toggle() } label: { Label("Toggle Inspector", systemImage: "sidebar.trailing") } } } See the attached screenshot. When the InspectorView is toggled open, the toolbar item tracks leading the split view tracking separator, which is not consistent with how Xcode works.

Since watchOS 26, watch face sharing has stopped working completely. I tested the following: Sharing via CLKWatchFaceLibrary Other public APIs Sharing via iMessage In all cases, the watch face cannot be reinstalled after being shared. This issue is not limited to my app. Large third-party apps such as Facer and other major watch face platforms are also affected, which suggests this is a system-level change or bug. Everything worked correctly before watchOS 26. Has Apple officially acknowledged this issue? Is there a recommended place to report or track this bug?

Hi everyone, I enrolled in the Apple Developer Program on the evening of December 22, 2025, and the membership fee has already been successfully charged to my bank account. It's 8 days without program... However, my account is still showing a “Pending” status with the message “Subscribe your membership.”

@Apple Developer Support Hello, It has now been more than 72 hours since my Apple Developer Program purchase. The payment was completed and the invoice was issued. Order Number: W1302770460 I have not received any response to my previous support requests, and my membership is still not active. Please escalate this case and complete the manual activation of my membership as soon as possible. Thank you.

When trying to login using apple account it shows me this error "Your request could not be completed because of an error. Please try again later." although in the inspector everything looks fine (200)

Hi, I have created an AppIntent in which there is a parameter called price, I have set the default value as 0. @Parameter(title: "Price", default: 0) var price: Int Problem When the shortcut is run this parameter is skipped Aim I still want to price to be asked however it needs to be pre-filled with 0 Question What should I do that the shortcut can still ask the price but be pre-filled with 0?