Hello,
I'm trying to figure out the behavior of AssetPackManager.shared.remove(assetPackWithID: ).
I'm working with MapKit tiles and currently working on trying projecting them correctly which involves serving the AssetPack locally, downloading, checking alignment, and then deleting and changing.
My question is that remove(assetPackWithID: ) completes successfully and the asset pack is removed. This is confirmed by trying to remove the AssetPack again which throws an error.
However, the asset is still appearing on MapKit after the removal. This is a bit odd as this persists not only with force killing, but also restarting the device.
Please advise on how to properly remove an AssetPack.
Thank you
iPhone 15 Pro Max (iOS 26.0.1)
iPhone 17 Pro Max (iOS 26.0.1)
Dive into the vast array of tools, services, and support available to developers.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hello Team,
I try to delete photo from Photos for that i used this method,
[[PHPhotoLibrary sharedPhotoLibrary] performChanges:^{
[PHAssetChangeRequest deleteAssets:@[assetToDelete]];
completionHandler:^(BOOL success, NSError *error) {
}];
This method pops up a dialog with Don't Allow or Delete. But some time in some iPhones not respond PHAssetChangeRequest deleteAssets method that's why that completionHandler not called because of that i can't perform any operation of PHPhotoLibrary then after.
If I restart my iPhone then it works. Many users of my app complained about this issue. I have an iPhone 11 with iOS 15.3. But some iOS 12,14,16 users also face the same issue.
So what exact issue is there? Is it related to iOS or a method?
Thanks,
Ankur
How to download the runtime simulators for the most recent Xcode 26 beta? The current download command I’m using doesn’t seem to work, and I’m encountering the following issues:
The runtime simulator download command (xcodebuild) requires the version number to be specified explicitly. I’ve tried multiple variations of version names/numbers but haven’t been able to identify the correct naming convention used by Apple for the Xcode 26 beta simulator runtimes.
$ xcodebuild -downloadPlatform IOS -exportPath ~/Downloads -buildVersion 26
Finding content...iOS 26 is not available for download.
$ xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion 26.0
Finding content...iOS 26.0 is not available for download.
$ xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion 26.0 beta
Finding content...iOS 26.0 is not available for download.
$ xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion "26.0 beta"
Finding content...iOS 26.0 beta is not available for download.
$ xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion "26.0_beta"
Finding content...iOS 26.0_beta is not available for download.
$ xcodebuild -downloadPlatform iOS -exportPath ~/Downloads -buildVersion 26.0_beta
Finding content...iOS 26.0_beta is not available for download.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Last week we received this e-mail from Apple, without any information about reasons. Our infrastructure builds on Apple infrastructure and contains more than 1000 iOS devices. We have paid enterprise account until April 2025. Why Apple cancelled our membership?
We are reaching out to inform you that your Apple Developer Enterprise Program ("ADEP") membership will be terminated, effective February 12, 2025.
Please be assured that this decision is not a result of any action or inaction on your part, and it is not subject to appeal.
As of February 12, 2025, you will no longer have access to your membership and account-related services for developing and distributing in-house, internal use software. Certificates, identifiers, and provisioning profiles will be revoked, and the apps associated with your account will no longer function.
In accordance with Section 11.3 of the ADEP Agreement, please immediately destroy all Apple Confidential Information that is in your possession or control and note your continuing obligations upon termination. Nothing in this letter should be construed as a waiver of any rights or remedies Apple may have, all of which are hereby reserved.
Topic:
Developer Tools & Services
SubTopic:
Apple Developer Program
Tags:
Enterprise
Business and Enterprise
We are seeing repeated occurrences of the following log line in test runs triggered via .xctestrun files on iOS 26:
IDERunDestination: Supported platforms for the buildables in the current scheme is empty.
This line is printed n number of times after a test fails, significantly increasing test execution duration (2–3 minutes extra in some cases).
The issue does not occur when tests are built and run together from Xcode directly — it’s specific to .xctestrun-based executions using xcodebuild test-without-building.
Steps to Reproduce:
Use Xcode 26 to build a sample XCTest target (we used a simple UI test project).
Locate the generated .xctestrun file under DerivedData/.../Build/Products/....
Run tests using:
xcodebuild -xctestrun /path/to/sample.xctestrun \
-destination "id=<device_id>" \
test-without-building
Observe the logs during test failure.
Observed Behavior:
The log line
IDERunDestination: Supported platforms for the buildables in the current scheme is empty
appears multiple times.
The test cleanup and teardown phase takes significantly longer (2–3 minutes).
Expected Behavior:
The log should appear once or not at all.
Test cleanup time should remain consistent.
Additional Information:
Affects only iOS 26 devices and .xctestrun-based runs.
Not reproducible on iOS < 26.
Xcode 26 and 26.x beta versions tried.
Reproducible both locally and on CI systems using real devices.
Same .xctestrun file, when used on older OS versions, does not cause delay.
Hey guys, I updated to macOS Tahoe and after that I tried installing Xcode 26, but I always get an error message saying it can’t complete the installation, both through the App Store and via direct download from Apple’s website. Is anyone else having this same issue?
Hi,
I have just updated my MacBook to Tahoe Beta 2, but now I cannot boot the iOS simulator.
Where can I download the next Xcode beta? The Application download page is still showing the Xcode beta 1 build.
Cheers,
Jeff
Hi so i have a given project where I am trying to use components within the PhotosUI Framework with Xcode26 and Xcode26.0.1
Just for reference here is an attached screenshot
This sample code compiled successfully with xcode16.4 and was in production.
There is no change in the pbxproj file , all the build settings have remained the same. Attaching it for reference.
project.pbxproj.txt
While showing declarations of PHPickerViewControllerDelegate i get two options
which is the same as in Xcode16.4
while browsing online found this reddit thread which is very similar
https://www.reddit.com/r/Xcode/comments/1nkku20/my_project_wont_compile_after_xcode_26_update_due/
Pls help :)
Just downloaded the latest Swift Playground for Mac (4.6). The Welcome window does not let you scroll horizontally via mouse, trackpad, or other means, so you can only see the first two Learn to Code resources - similar for the App Gallery and Extend Your App sections.
Hi.
I'm currently working on Xcode CI build uploading ipa to TestFlight.
Building archive is successful but exportArchive is failed with error "exportArchive Failed to Use Accounts".
How can I fix this error?
After upgrading to macOS 26.0 Tahoe and Xcode 26.0.1, I’ve noticed an issue with audio playback whenever the iOS Simulator is running.
Device: MacBook Pro 13" (2020, Intel, 16GB RAM, 500GB SSD)
Issue: Any sound played on the Mac (system sounds, music, videos) begins to break/distort once the Simulator is active.
App Sounds: If the app running inside the Simulator plays audio, that audio also breaks/distorts.
Previous Version: This issue did not occur on macOS Sequoia 15 or with Xcode 16. Everything was working fine before the upgrade.
Attempting to launch a widget in Debug mode on Sonoma from Xcode 15 is failing with the following message:
attach failed (Not allowed to attach to process. Look in the console messages (Console.app), near the debugserver entries, when the attach failed. The subsystem that denied the attach permission will likely have logged an informative message about why it was denied.)
Looking in console I see this message:
macOSTaskPolicy: (com.apple.debugserver) may not get the task control port of (MacGalleryWidget) (pid: 1851): (MacGalleryWidget) is hardened, (MacGalleryWidget) doesn't have get-task-allow, (com.apple.debugserver) is a declared debugger(com.apple.debugserver) is not a declared read-only debugger
What Xcode settings should I be looking at to rectify this? I suspect I may have something that's out of whack.
Failed to fetch certificates:
This request is forbidden for security reasons - Unable to find a team with the given Content Provider ID '72df6041-c291-4d95-b690-2a3b75ff72f6' to which you belong. Please contact Apple Developer Program Support. https://developer.apple.com/support
I have already confirmed that: All API keys were generated correctly. All required roles and permissions have been assigned in App Store Connect.
To confirm my doubt, I requested api key from a fellow developer, and that worked in CodeMagic without throwing an error.
Could you please help me figure out why the given Content Provider ID is not being recognized?
Thank you.
Is there a way to use CFBundleVersion instead of CI_BUILD_NUMBER from XCode Cloud's workflow on Web ?
We would like to have control over the major and minor version numbers of the build from the workflow.
I am getting following error from one of the pod frameworks while running the app (Build is a success).
dyld: Symbol not found: __ZN5swift34swift50override_conformsToProtocolEPKNS_14TargetMetadataINS_9InProcessEEEPKNS_24TargetProtocolDescriptorIS1_EEPFPKNS_18TargetWitnessTableIS1_EES4_S8_E.
Referenced from: X framework
Expected in: frameworks/DeviceKit.framework/DeviceKit
mac OS 10.15
Xcode 12.4
React native 0.63
cocoapods: 1.10.1
Not a question, but a surprise.
Did I miss something, but apparently there has been no new beta release (16.3) since Release of 16.2 on Dec 11. 2 months without betas is really unusual (in fact, it never happened and usually, next beta n+1 is even released before the final release of version n).
So does that mean 16.3 will be a major update ? Wait and see.
I can't find Rosetta Simulators in Xcode 26 Beta, even when I select "Show all destinations."
Topic:
Developer Tools & Services
SubTopic:
Xcode
I am not able to use the Debug Memory Graph tool as well as Leaks instrument inside Xcode to debug my project.
I'm running my project on physical iOS device on running 18.3 version and I tested the project on two different MacBooks running Xcode 16.3 and 16.1. On both the same problem persists. I have also reinstalled the project on the device and tried restarting all devices and cleared DerivedData. Nothing helped.
Clicking "Show details" shows such output:
Domain: DTLeaksService
Code: -1
User Info: {
DVTErrorCreationDateKey = "2025-05-07 06:30:53 +0000";
DVTRadarComponentKey = 637311;
}
--
Event Metadata: com.apple.dt.memory_graph_capture : {
"debugSession_coalescedState" = 2;
"debugSession_isSynthetic" = 0;
"debugSession_state" = 2;
"device_identifier" = "00008110-0009448221A3801E";
"device_isCoreDevice" = 1;
"device_model" = "iPhone14,4";
"device_osBuild" = "18.4 (22E240)";
"device_platform" = "com.apple.platform.iphoneos";
"device_thinningType" = "iPhone14,4";
"dvt_coredevice_version" = "397.24";
"dvt_coresimulator_version" = "987.2";
"dvt_mobiledevice_version" = "1784.102.1";
"launchSession_schemeCommand" = Run;
"launchSession_state" = 2;
"launchSession_targetArch" = arm64;
"memgraphDebugger_duration_ms" = 3050;
"memgraphDebugger_precedingCount" = 1;
"memgraphDebugger_status" = "-1";
"param_debugger_attachToExtensions" = 0;
"param_debugger_attachToXPC" = 1;
"param_debugger_type" = 3;
"param_destination_isProxy" = 0;
"param_destination_platform" = "com.apple.platform.iphoneos";
"param_diag_113575882_enable" = 0;
"param_diag_MainThreadChecker_stopOnIssue" = 0;
"param_diag_MallocStackLogging_enableDuringAttach" = 0;
"param_diag_MallocStackLogging_enableForXPC" = 1;
"param_diag_allowLocationSimulation" = 1;
"param_diag_checker_tpc_enable" = 1;
"param_diag_gpu_frameCapture_enable" = 3;
"param_diag_gpu_shaderValidation_enable" = 0;
"param_diag_gpu_validation_enable" = 0;
"param_diag_guardMalloc_enable" = 0;
"param_diag_memoryGraphOnResourceException" = 0;
"param_diag_mtc_enable" = 1;
"param_diag_queueDebugging_enable" = 1;
"param_diag_runtimeProfile_generate" = 0;
"param_diag_sanitizer_asan_enable" = 0;
"param_diag_sanitizer_tsan_enable" = 0;
"param_diag_sanitizer_tsan_stopOnIssue" = 0;
"param_diag_sanitizer_ubsan_enable" = 0;
"param_diag_sanitizer_ubsan_stopOnIssue" = 0;
"param_diag_showNonLocalizedStrings" = 0;
"param_diag_viewDebugging_enabled" = 1;
"param_diag_viewDebugging_insertDylibOnLaunch" = 1;
"param_install_style" = 2;
"param_launcher_UID" = 2;
"param_launcher_allowDeviceSensorReplayData" = 0;
"param_launcher_kind" = 0;
"param_launcher_style" = 99;
"param_launcher_substyle" = 0;
"param_runnable_appExtensionHostRunMode" = 0;
"param_runnable_productType" = "com.apple.product-type.application";
"param_structuredConsoleMode" = 1;
"param_testing_launchedForTesting" = 0;
"param_testing_suppressSimulatorApp" = 0;
"param_testing_usingCLI" = 0;
"sdk_canonicalName" = "iphoneos18.1";
"sdk_osVersion" = "18.1";
"sdk_variant" = iphoneos;
}
--
System Information
macOS Version 14.5 (Build 23F79)
Xcode 16.1 (23503) (Build 16B40)
Timestamp: 2025-05-07T08:30:53+02:00
Here are my active scheme settings:
Topic:
Developer Tools & Services
SubTopic:
Xcode
Below is an English version of your post, ready to copy-and-paste into the Apple Developer Forums:
I’m seeing a crash in Xcode 26 beta 3 whenever the StoreKit symbol SKStoreProductParameterAdNetworkSourceIdentifier is present while running on an iOS 15 simulator.
Steps to reproduce
Install Xcode 26 beta 3.
Create any iOS app and run it on an iOS 15 simulator (device model doesn’t matter).
Add the following code anywhere and run:
override func viewDidLoad() {
super.viewDidLoad()
if #available(iOS 16.1, *) {
print("SKStoreProductParameterAdNetworkSourceIdentifier: \(SKStoreProductParameterAdNetworkSourceIdentifier)")
}
}
The project builds successfully, but before the #available(iOS 16.1, *) check is reached, the app crashes with:
Symbol not found: _SKStoreProductParameterAdNetworkSourceIdentifier
When I build the same project with Xcode 16.4 and launch it on an iOS 15 simulator, it runs without crashing.
Investigation so far
Because SKStoreProductParameterAdNetworkSourceIdentifier is just an NSString, I could substitute the string literal "SKStoreProductParameterAdNetworkSourceIdentifier" as a temporary workaround, but that doesn’t feel like a proper fix.
The symbol is still declared in both SDKs:
/Applications/Xcode-16.4.0.app/.../StoreKit.framework/Headers/SKAdNetwork.h:48:
SK_EXTERN NSString * const SKStoreProductParameterAdNetworkSourceIdentifier API_AVAILABLE(ios(16.1)) API_UNAVAILABLE(macos, watchos, visionos);
/Applications/Xcode-26.0.0-Beta.3.app/.../StoreKit.framework/Headers/SKAdNetwork.h:48:
SK_EXTERN NSString * const SKStoreProductParameterAdNetworkSourceIdentifier API_AVAILABLE(ios(16.1)) API_UNAVAILABLE(macos, watchos, visionos);
So the symbol hasn’t been removed in the beta SDK. Given that the code is wrapped in #available(iOS 16.1, *), I don’t believe the sample itself is at fault.
Questions
Could this be a bug in Xcode 26’s availability checking or linker?
Has anyone else encountered the same issue or found a more robust workaround?
Any insights would be greatly appreciated.
"Auth Key can only be downloaded once. This auth key has already been downloaded."