Search results for

“Xcode”

93,877 results found

Post

Replies

Boosts

Views

Activity

AVAudioFile.read extremely slow after seeking in FLAC and MP3 files
I'm developing an audio player app that uses AVAudioFile to read PCM data from various formats. I'm experiencing severe performance issues when seeking in FLAC, while other compressed formats (M4A/AAC) work correctly. I don't intend to use them in my app, but I also tested mp3 files just by curiosity and they also have this issue. Environment: macOS 26 (Tahoe) Xcode 26.3 Apple Silicon (M1) The issue: After setting AVAudioFile.framePosition to a position mid-file, the subsequent call to AVAudioFile.read(into:frameCount:) blocks for an unreasonable amount of time for FLAC and MP3 files. The delay scales linearly with the seek target, seeking near the beginning is fast, seeking toward the end is proportionally slower, which suggests the decoder is decoding linearly from the beginning of the file rather than using any seek index. (My app deals with “images” of Audio CDs ripped as a single long audio file.) The issue is particularly severe when reading files from an SMB network share (server on Ethernet,
0
0
124
1w
DeviceActivityMonitor extension rejected by App Store Connect validator — NSExtensionPointIdentifier "com.apple.deviceactivity.monitor" invalid (IrisAPI -19241)
Hi everyone, I'm building an iOS app that uses a DeviceActivityMonitor app extension as part of the Screen Time / Family Controls API. Every time I try to upload my IPA to App Store Connect, the validation fails with this error: Invalid Info.plist value. The value of the NSExtensionPointIdentifier key, com.apple.deviceactivity.monitor, in the Info.plist of 'Alexandria.app/PlugIns/AlexandriaActivityMonitor.appex' is invalid. Error Domain=IrisAPI Code=-19241, iris-code=STATE_ERROR.VALIDATION_ERROR What I have verified (everything looks correct): NSExtensionPointIdentifier = com.apple.deviceactivity.monitor NSExtensionPrincipalClass = AlexandriaActivityMonitor.AlexandriaActivityMonitorExtension (correctly resolved in the compiled binary, verified with plutil -p) The Swift class correctly subclasses DeviceActivityMonitor CFBundleShortVersionString matches the main app Both the main app and extension provisioning profiles explicitly contain com.apple.developer.family-controls = true (verified by inspecting embedde
3
0
140
1w
Reply to Simulator was shutdown during an update
Hi, Sorry to hear you are having problems getting previews working. This kind of issue can often indicate a crash in a problem with the simulator infrastructure itself. If you look into the folder ~/Library/Logs/DiagnosticReports, do you see any crash reports for anything that corresponds with the timeframe where you reproduced the problem? If nothing stands out to you, the best next step will be to file a feedback with diagnostics so we can take a look. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an error banner will appe
1w
RealityView content disappears when selecting Lock In Place on visionOS
Hi, I'm experiencing an issue where all RealityView content disappears when the user selects Lock In Place from the window management menu (long press on close button). Follow Me works correctly and this happens in Testflight builds only not reproducible when I run locally I have reproduced this with a minimal project containing nothing but a simple red cube — no custom anchors, no app state, no dependencies. Steps to Reproduce: Open an ImmersiveSpace. A red cube is placed 1m in front of the user via RealityView. Long press the X button on any floating window Select Lock In Place. The cube disappears immediately. Expected: Cube remains visible after window is locked Actual: Cube disappears. Minimal reproducible code: var body: some View { RealityView { content in let cube = ModelEntity( mesh: .generateBox(size: 0.3), materials: [SimpleMaterial(color: .red, isMetallic: false)] ) cube.setPosition(SIMD3(0, 1.5, -1), relativeTo: nil) content.add(cube) } } } Device: Apple Vision Pro visionOS vers
3
0
487
1w
RealityView content disappears when selecting Lock In Place on visionOS
I'm experiencing an issue where all RealityView content disappears when the user selects Lock In Place from the window management menu (long press on close button). Follow Me works correctly and this happens in Testflight builds only not reproducible when I run locally I have reproduced this with a minimal project containing nothing but a simple red cube — no custom anchors, no app state, no dependencies. Steps to Reproduce: Open an ImmersiveSpace A red cube is placed 1m in front of the user via RealityView Long press the X button on any floating window Select Lock In Place The cube disappears immediately Expected: Cube remains visible after window is locked Actual: Cube disappears. Note: Follow Me does NOT reproduce this issue. Minimal reproducible code: struct ImmersiveView: View { var body: some View { RealityView { content in let cube = ModelEntity( mesh: .generateBox(size: 0.3), materials: [SimpleMaterial(color: .red, isMetallic: false)] ) cube.setPosition(SIMD3(0, 1.5, -1), relativeTo:
0
0
288
1w
Reply to Icon composer icon contains alpha channel upload error
Following the documentation here also did not work for me. https://developer.apple.com/documentation/xcode/creating-your-app-icon-using-icon-composer#Add-your-Icon-Composer-file-to-an-Xcode-project What worked for me was the following: In Icon Composer, select File -> Export... For Appearance, select All, then click Export... Select a location and click Export to save Navigate to the location you saved, there should be 6 .png files. Select the three you will use for AppIcon from assets for Any Appearance, Dark, and Tinted options. Open those in Preview In Preview for each image, select File -> Export... Be sure to uncheck the Alpha setting and save the file. Use the newly exported images for your three AppIcon settings in Assets.
1w
AccessoryNotification Demo
I am planning to run the AccessoryNotifications framework on xcode26.4 and ios26.4, please refer to the documentation https://developer.apple.com/documentation/accessorynotifications I couldn't find a complete demo, but I found a demo based on AccessorySetup Kit, ASK Sample https://docs-assets.developer.apple.com/published/89f5eef578ef/SettingUpAndAuthorizingABluetoothAccessory.zip. So I plan to practice the entire process of AccessoryNotifications based on this demo. Find accessories based on ASK Sample and connect them, OK Call requestForwarding (for:), OK Add AccessoryData Provider extension to receive system notifications But this step failed. I added an extension according to the documentation, but the following method will not be executed func activate(for session: NotificationsForwarding.Session) func add(notification: AccessoryNotification alertingContext: AlertingContext, alertCoordinator: AlertCoordinating) {} I found the following error log in console.app Error 16:38:17.582340+0800 usernotification
0
0
55
1w
Simulator was shutdown during an update
I am trying to preview my SwiftUI views but Xcode Preview Canvas failing. I tried everything that I found at internet but nothing works. Finally I created a new iOS project that contains only a view import SwiftUI struct ContentView: View { var body: some View { VStack { Image(systemName: globe) .imageScale(.large) .foregroundStyle(.tint) Text(Hello, world!) } .padding() } } #Preview { ContentView() } Even this view cannot be previewed The error is Simulator was shutdown during an update Simulator [3E0DB935-C4C2-4566-BA48-8E21564C207C] failed to boot and may have crashed. I tried to restart xCode, restart Mac, download ios 26.0 sdk and created a simulator with that sdk but nothing helped. Do you have an idea?
1
0
74
1w
Reply to 26.4 beta and RC versions are unable to be created on anything but 26.4 beta host OS
AFAIK there’s no magic here. And I tried reproducing this on my main work Mac and didn’t have a problem. Specifically: On macOS 26.3.1, I downloaded the current 26.4rc seed (UniversalMac_26.4_25E243_Restore.ipsw). Using an off-the-shelf Virtualization framework app [1], I created a VM from that. It installed and booted, and I was able to run all the way through MacBuddy and get to the Finder. I’m not sure why this is failing in your environment. This Mac is production hardware that’s only ever run released system software (plus various Xcode beta seeds). When I wrote the above I hadn’t yet installed Xcode 26.4rc. So I installed that and repeated the test. It didn’t change anything. Things continued to work. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] VirtualBuddy 2.1.
Topic: App & System Services SubTopic: Core OS Tags:
1w
Reply to Does signed macho binary with teamID is signed by Apple root certificate
[quote='880707022, chapo213, /thread/818938?answerId=880707022#880707022, /profile/chapo213'] I need to support both use case (exec and dylib). [/quote] OK. [quote='880707022, chapo213, /thread/818938?answerId=880707022#880707022, /profile/chapo213'] [Library validation] does not apply in my scenario since the library is provided by a third party [/quote] I’d like to better understand that. It’s quite common for Mac apps to use libraries created by other developers, and they retain library validation by re-signing those libraries. Is there something preventing you from doing that in this case? The most obvious case where folks need to disable library validation is that their app supports in-process plug-ins, where those plug-ins are built and shipped by other third-party developers in a way that’s completely independent of the main app’s vendor. Is that what’s happening here? Because if you’re managing these plug-in releases then it’d be better to have you re-sign the plug-in and leave library validation enab
1w
Reply to Xcode 26.3 not rendering Unicode/Emoji in Simulator or Canvas
Thanks so much for this post and thanks for your patience on my replay. When Unicode characters and emojis render perfectly on a physical device but appear as blank spaces or empty boxes in the Simulator and SwiftUI Canvas, in my opinion it means the Color Emoji font is missing and this is corrupted, or failing to load inside the Simulator Runtime. Because the SwiftUI Canvas uses the exact same underlying simulator infrastructure as the standalone Simulator app, both break at the same time. We identified this a bug and I would encourage you to use the physical device or to download the latest beta simulators iOS 24.4 RC https://developer.apple.com/download/os/ and let me know it the issue has been fixed. Here are the most effective ways to resolve this issue: Open Xcode and go to Xcode > Settings (or Preferences) > Platforms. Find the iOS Simulator runtime you are currently using (e.g., iOS 26.3). Right-click (or Control-click) it and select Delete. Once deleted, click the + button at
1w
Reply to All Xcode projects showing up in source control navigator.
Git repos can be big source of this problem. But there's one more to check. Xcode projects actually consist of two parts - the project and the workspace. The source code integrations are based on the workspace. Xcode uses a shared workspace by default. But you can create a dedicated workspace file for your project and then just open that file instead of the project file.
Replies
Boosts
Views
Activity
1w
Reply to All Xcode projects showing up in source control navigator.
Hi! Could you check whether you've created a git repo in a parent folder relative to your projects? For example, in your home folder. When a project is opened in Xcode, it searches all parent folders for a git repo, so that it is able to correlate workspaces that span multiple projects, and this could be triggering that logic.
Replies
Boosts
Views
Activity
1w
AVAudioFile.read extremely slow after seeking in FLAC and MP3 files
I'm developing an audio player app that uses AVAudioFile to read PCM data from various formats. I'm experiencing severe performance issues when seeking in FLAC, while other compressed formats (M4A/AAC) work correctly. I don't intend to use them in my app, but I also tested mp3 files just by curiosity and they also have this issue. Environment: macOS 26 (Tahoe) Xcode 26.3 Apple Silicon (M1) The issue: After setting AVAudioFile.framePosition to a position mid-file, the subsequent call to AVAudioFile.read(into:frameCount:) blocks for an unreasonable amount of time for FLAC and MP3 files. The delay scales linearly with the seek target, seeking near the beginning is fast, seeking toward the end is proportionally slower, which suggests the decoder is decoding linearly from the beginning of the file rather than using any seek index. (My app deals with “images” of Audio CDs ripped as a single long audio file.) The issue is particularly severe when reading files from an SMB network share (server on Ethernet,
Replies
0
Boosts
0
Views
124
Activity
1w
DeviceActivityMonitor extension rejected by App Store Connect validator — NSExtensionPointIdentifier "com.apple.deviceactivity.monitor" invalid (IrisAPI -19241)
Hi everyone, I'm building an iOS app that uses a DeviceActivityMonitor app extension as part of the Screen Time / Family Controls API. Every time I try to upload my IPA to App Store Connect, the validation fails with this error: Invalid Info.plist value. The value of the NSExtensionPointIdentifier key, com.apple.deviceactivity.monitor, in the Info.plist of 'Alexandria.app/PlugIns/AlexandriaActivityMonitor.appex' is invalid. Error Domain=IrisAPI Code=-19241, iris-code=STATE_ERROR.VALIDATION_ERROR What I have verified (everything looks correct): NSExtensionPointIdentifier = com.apple.deviceactivity.monitor NSExtensionPrincipalClass = AlexandriaActivityMonitor.AlexandriaActivityMonitorExtension (correctly resolved in the compiled binary, verified with plutil -p) The Swift class correctly subclasses DeviceActivityMonitor CFBundleShortVersionString matches the main app Both the main app and extension provisioning profiles explicitly contain com.apple.developer.family-controls = true (verified by inspecting embedde
Replies
3
Boosts
0
Views
140
Activity
1w
Reply to Simulator was shutdown during an update
Hi, Sorry to hear you are having problems getting previews working. This kind of issue can often indicate a crash in a problem with the simulator infrastructure itself. If you look into the folder ~/Library/Logs/DiagnosticReports, do you see any crash reports for anything that corresponds with the timeframe where you reproduced the problem? If nothing stands out to you, the best next step will be to file a feedback with diagnostics so we can take a look. Install the logging profile using instructions available here: https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift On your mac running Xcode, and on your physical preview device (if you are using one). Install the logging profile using the following instructions on your mac running Xcode; and if you are using one, your physical preview device (iOS or visionOS): https://developer.apple.com/bug-reporting/profiles-and-logs/?name=swift Then when you reproduce the problem in Xcode: Either (a) an error banner will appe
Replies
Boosts
Views
Activity
1w
RealityView content disappears when selecting Lock In Place on visionOS
Hi, I'm experiencing an issue where all RealityView content disappears when the user selects Lock In Place from the window management menu (long press on close button). Follow Me works correctly and this happens in Testflight builds only not reproducible when I run locally I have reproduced this with a minimal project containing nothing but a simple red cube — no custom anchors, no app state, no dependencies. Steps to Reproduce: Open an ImmersiveSpace. A red cube is placed 1m in front of the user via RealityView. Long press the X button on any floating window Select Lock In Place. The cube disappears immediately. Expected: Cube remains visible after window is locked Actual: Cube disappears. Minimal reproducible code: var body: some View { RealityView { content in let cube = ModelEntity( mesh: .generateBox(size: 0.3), materials: [SimpleMaterial(color: .red, isMetallic: false)] ) cube.setPosition(SIMD3(0, 1.5, -1), relativeTo: nil) content.add(cube) } } } Device: Apple Vision Pro visionOS vers
Replies
3
Boosts
0
Views
487
Activity
1w
RealityView content disappears when selecting Lock In Place on visionOS
I'm experiencing an issue where all RealityView content disappears when the user selects Lock In Place from the window management menu (long press on close button). Follow Me works correctly and this happens in Testflight builds only not reproducible when I run locally I have reproduced this with a minimal project containing nothing but a simple red cube — no custom anchors, no app state, no dependencies. Steps to Reproduce: Open an ImmersiveSpace A red cube is placed 1m in front of the user via RealityView Long press the X button on any floating window Select Lock In Place The cube disappears immediately Expected: Cube remains visible after window is locked Actual: Cube disappears. Note: Follow Me does NOT reproduce this issue. Minimal reproducible code: struct ImmersiveView: View { var body: some View { RealityView { content in let cube = ModelEntity( mesh: .generateBox(size: 0.3), materials: [SimpleMaterial(color: .red, isMetallic: false)] ) cube.setPosition(SIMD3(0, 1.5, -1), relativeTo:
Replies
0
Boosts
0
Views
288
Activity
1w
Reply to Icon composer icon contains alpha channel upload error
Following the documentation here also did not work for me. https://developer.apple.com/documentation/xcode/creating-your-app-icon-using-icon-composer#Add-your-Icon-Composer-file-to-an-Xcode-project What worked for me was the following: In Icon Composer, select File -> Export... For Appearance, select All, then click Export... Select a location and click Export to save Navigate to the location you saved, there should be 6 .png files. Select the three you will use for AppIcon from assets for Any Appearance, Dark, and Tinted options. Open those in Preview In Preview for each image, select File -> Export... Be sure to uncheck the Alpha setting and save the file. Use the newly exported images for your three AppIcon settings in Assets.
Replies
Boosts
Views
Activity
1w
AccessoryNotification Demo
I am planning to run the AccessoryNotifications framework on xcode26.4 and ios26.4, please refer to the documentation https://developer.apple.com/documentation/accessorynotifications I couldn't find a complete demo, but I found a demo based on AccessorySetup Kit, ASK Sample https://docs-assets.developer.apple.com/published/89f5eef578ef/SettingUpAndAuthorizingABluetoothAccessory.zip. So I plan to practice the entire process of AccessoryNotifications based on this demo. Find accessories based on ASK Sample and connect them, OK Call requestForwarding (for:), OK Add AccessoryData Provider extension to receive system notifications But this step failed. I added an extension according to the documentation, but the following method will not be executed func activate(for session: NotificationsForwarding.Session) func add(notification: AccessoryNotification alertingContext: AlertingContext, alertCoordinator: AlertCoordinating) {} I found the following error log in console.app Error 16:38:17.582340+0800 usernotification
Replies
0
Boosts
0
Views
55
Activity
1w
Simulator was shutdown during an update
I am trying to preview my SwiftUI views but Xcode Preview Canvas failing. I tried everything that I found at internet but nothing works. Finally I created a new iOS project that contains only a view import SwiftUI struct ContentView: View { var body: some View { VStack { Image(systemName: globe) .imageScale(.large) .foregroundStyle(.tint) Text(Hello, world!) } .padding() } } #Preview { ContentView() } Even this view cannot be previewed The error is Simulator was shutdown during an update Simulator [3E0DB935-C4C2-4566-BA48-8E21564C207C] failed to boot and may have crashed. I tried to restart xCode, restart Mac, download ios 26.0 sdk and created a simulator with that sdk but nothing helped. Do you have an idea?
Replies
1
Boosts
0
Views
74
Activity
1w
Reply to 26.4 beta and RC versions are unable to be created on anything but 26.4 beta host OS
AFAIK there’s no magic here. And I tried reproducing this on my main work Mac and didn’t have a problem. Specifically: On macOS 26.3.1, I downloaded the current 26.4rc seed (UniversalMac_26.4_25E243_Restore.ipsw). Using an off-the-shelf Virtualization framework app [1], I created a VM from that. It installed and booted, and I was able to run all the way through MacBuddy and get to the Finder. I’m not sure why this is failing in your environment. This Mac is production hardware that’s only ever run released system software (plus various Xcode beta seeds). When I wrote the above I hadn’t yet installed Xcode 26.4rc. So I installed that and repeated the test. It didn’t change anything. Things continued to work. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] VirtualBuddy 2.1.
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
1w
Reply to Does signed macho binary with teamID is signed by Apple root certificate
[quote='880707022, chapo213, /thread/818938?answerId=880707022#880707022, /profile/chapo213'] I need to support both use case (exec and dylib). [/quote] OK. [quote='880707022, chapo213, /thread/818938?answerId=880707022#880707022, /profile/chapo213'] [Library validation] does not apply in my scenario since the library is provided by a third party [/quote] I’d like to better understand that. It’s quite common for Mac apps to use libraries created by other developers, and they retain library validation by re-signing those libraries. Is there something preventing you from doing that in this case? The most obvious case where folks need to disable library validation is that their app supports in-process plug-ins, where those plug-ins are built and shipped by other third-party developers in a way that’s completely independent of the main app’s vendor. Is that what’s happening here? Because if you’re managing these plug-in releases then it’d be better to have you re-sign the plug-in and leave library validation enab
Replies
Boosts
Views
Activity
1w
Reply to Grant Access - Register GitLab Application - 504 Client Timeout
Dear Xcode cloud support The same error occur on my hosted gitlab repo. I allow my firewall with the IP adress ranges you mention, but i still have the same error 504 Client Timeout. If you are using a firewall, it must be configured to accept incoming connections. Thanks yours sincerely,
Replies
Boosts
Views
Activity
1w
All Xcode projects showing up in source control navigator.
This just started happening today out of nowhere. Instead of only the project I’m working on appearing in Source Control, every project inside my Xcode projects folder is now showing up in the Source Control navigator. This is happening in both the Changes and Repositories tabs.
Replies
2
Boosts
0
Views
165
Activity
1w
Reply to Xcode 26.3 not rendering Unicode/Emoji in Simulator or Canvas
Thanks so much for this post and thanks for your patience on my replay. When Unicode characters and emojis render perfectly on a physical device but appear as blank spaces or empty boxes in the Simulator and SwiftUI Canvas, in my opinion it means the Color Emoji font is missing and this is corrupted, or failing to load inside the Simulator Runtime. Because the SwiftUI Canvas uses the exact same underlying simulator infrastructure as the standalone Simulator app, both break at the same time. We identified this a bug and I would encourage you to use the physical device or to download the latest beta simulators iOS 24.4 RC https://developer.apple.com/download/os/ and let me know it the issue has been fixed. Here are the most effective ways to resolve this issue: Open Xcode and go to Xcode > Settings (or Preferences) > Platforms. Find the iOS Simulator runtime you are currently using (e.g., iOS 26.3). Right-click (or Control-click) it and select Delete. Once deleted, click the + button at
Replies
Boosts
Views
Activity
1w