Hello, while my project, which I created with the Unity game engine, runs smoothly in the editor, when I try to run it and/or archive through Xcode, I receive the following error: Undefined symbols: Linker command failed with exit code 1 (use -v to see invocation) When I right click on the problem and click Reveal in log it doesn't take me anywhere. Can you help me with this? Thanks.

If anyone knows how to build iOS Deployment Target 11; (react-native app with 0.64.4 version) run and build on Xcode 15 with iOS 17 SDK, Mac M1 environment it will be a great help at least if you can share a guide. And I don't know is it possible or not. I would appreciate any advice you can give me. Thank You! (using Mac m1 with Sonoma.) I just ran a Hello World app from that version of react native and tried a few changes on Xcode 15, but didn't work for iOS. but Android worked well. used node 14. Is there any possibility of running this old version of RN in the latest Xcode building an archive and publish to the app store? (the main reason is we couldn't update the RN version due to some of the dependency versions.)

I am trying to archive an application, where the process replies my application is rejected. The response indicates: [The operation couldn’t be completed. Unable to login with account xxxxx.***]. The login details for account [xxxxx.***] were rejected. I just changed my Apple ID password, and unfortunately I believe this happens to be the cause of the issue. Would changing the Apple ID password take effect after a certain time period ... ? Would there possibly be an avenue I did not properly complete to allow the application to be archived … ? Best regards, jim_k

Organizer Terminations tab shows "Insufficient terminations data available" when there's no filter applied: iPhone (All). However it shows data when I explicitly select a device type. This particular app has more users than other apps for which this tab works OK. It used to work fine but stopped working a couple of months ago. The Xcode version doesn't matter (I tried Xcode 14.3.1, Xcode 15.1 and Xcode 15.2). Please check attached screenshot. Thank you.

I have several apps that contain extensions. For example an App Clip, Widget, Background Assets extension, etc. In Xcode Organizer Version 15.3 (15E204a), attempting to view crash data for these apps results in a failure. I have explicitly seen this error print out the app clip extension bundle identifier, as well as the background assets extension bundle identifier. It says the following error: An error occurred preventing Xcode from downloading crashes list. "" failed with error: Access Restricted with bundle id: com.example.app-name.extension-name Is anyone else experiencing this? I created a feedback a few weeks ago, it seemed to coincide with the release of Xcode 15.3 and or the new App Store Connect metrics APIs. App IDs and bundle identifiers detailed in the feedback if anyone at Apple wants the info. FB13677615 - Xcode: Cannot download crashes for apps that containg extensions --> "Access Restricted with bundle id:

Since yesterday (03/22/24) we are unable to upload new or existing builds to AppStoreConnect. We get the following error - “Error ITMS-90432 Unexpected file found in Frameworks. MyApp.app/Frameworks/Configurations” file is in the Frameworks directory, but the Swift runtime libraries are the only files permitted in that directory. Please remove this file and upload a new build. (ID: 57e219ea-d27e-465d-9e9b-ec41d3a0b1f7). We have tried rebuilding targerts with no changes for Builds that use to upload ok and they now get the same error too. Is this an appstoreconnect bug? If not where is the Frameworks directory and how do we remove the file?

Xcode 15 crash when distribute xcarchive and uploading testlight device build and test is ok. crash only distrubute or upload testflight. please help. log ------ Translated Report (Full Report Below) Process: Xcode [39575] Path: /Applications/Xcode 15.3.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 15.3 (22618) Build Info: IDEApplication-22618000000000000~2 (15E204a) Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-04-01 14:29:11.6246 +0900 OS Version: macOS 14.4 (23E214) Report Version: 12 Anonymous UUID: 51D32CCD-BB07-86A9-2641-AAD37E77709C Sleep/Wake UUID: F63E4DBB-7A3B-4452-A404-0127BDB0E06D Time Awake Since Boot: 160000 seconds Time Since Wake: 23531 seconds System Integrity Protection: enabled Crashed Thread: 12 Dispatch queue: com.apple.root.default-qos Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Xcode [39575] Application Specific Information: abort() called Application Specific Signatures: success Thread 0:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x18f9d21f4 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x18f9e4b24 mach_msg2_internal + 80 2 libsystem_kernel.dylib 0x18f9dae34 mach_msg_overwrite + 476 3 libsystem_kernel.dylib 0x18f9d2578 mach_msg + 24 4 CoreFoundation 0x18faf2058 __CFRunLoopServiceMachPort + 160 5 CoreFoundation 0x18faf091c __CFRunLoopRun + 1208 6 CoreFoundation 0x18faefe0c CFRunLoopRunSpecific + 608 7 HIToolbox 0x19a28b000 RunCurrentEventLoopInMode + 292 8 HIToolbox 0x19a28ae3c ReceiveNextEventCommon + 648 9 HIToolbox 0x19a28ab94 _BlockUntilNextEventMatchingListInModeWithFilter + 76 10 AppKit 0x193348970 _DPSNextEvent + 660 11 AppKit 0x193b3adec -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700 12 DVTKit 0x10573f858 -[DVTApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 300 13 AppKit 0x19333bcb8 -[NSApplication run] + 476 14 DVTKit 0x10573eb24 -[DVTApplication run] + 60 15 AppKit 0x193312f54 NSApplicationMain + 880 16 dyld 0x18f68a0e0 start + 2360 . . . Thread 12 Crashed:: Dispatch queue: com.apple.root.default-qos 0 libsystem_kernel.dylib 0x18f9daa60 __pthread_kill + 8 1 libsystem_pthread.dylib 0x18fa12c20 pthread_kill + 288 2 libsystem_c.dylib 0x18f91fa20 abort + 180 3 IDEKit 0x10a2b7b64 +[IDEAssertionHandler _handleAssertionWithLogString:assertionSignature:assertionReason:extraBacktrace:] + 972 4 IDEKit 0x10a2b7fa4 -[IDEAssertionHandler handleFailureInMethod:object:fileName:lineNumber:assertionSignature:messageFormat:arguments:] + 872 5 DVTFoundation 0x1068aa73c _DVTAssertionHandler + 424 6 DVTFoundation 0x1068aa8bc _DVTAssertionFailureHandler + 196 7 DVTFoundation 0x106770410 +[DVTFilePath _filePathForParent:pathString:] + 512 8 DVTFoundation 0x106770a9c -[DVTFilePath filePathForRelativePathString:] + 48 9 IDEFoundation 0x10bdb9edc -[IDEDistributionProcessingPipelineContext packagePathForVariant:] + 768 10 IDEFoundation 0x10bdd0514 -[IDEDistributionCreateIPAStep name] + 88 11 IDEFoundation 0x10bdb7e40 __98-[IDEDistributionProcessingPipeline observationForPhaseStateChanges:stepIndex:pipelineStepsCount:]_block_invoke + 96 12 DVTFoundation 0x1068b65e4 -[NSObject(DVTObservingConvenience) _dvt_newObserverForKeyPath:options:owner:creationBacktrace:withHandlerBlock:] + 380 13 DVTFoundation 0x1068b73ac -[NSObject(DVTObservingConvenience) dvt_newObserverForKeyPath:options:withHandlerBlock:] + 124 14 IDEFoundation 0x10bdb7d04 -[IDEDistributionProcessingPipeline observationForPhaseStateChanges:stepIndex:pipelineStepsCount:] + 152 15 IDEFoundation 0x10bdb8078 -[IDEDistributionProcessingPipeline processForThinningVariant:distributionItem:stepClass:stepIndex:pipelineStepsCount:error:] + 420 16 IDEFoundation 0x10bdb780c -[IDEDistributionProcessingPipeline process:] + 1132 17 IDEFoundation 0x10bb6c594 -[IDEDistributionPackagingStep loadDrivableFromExportOptions:error:] + 204 18 IDEFoundation 0x10bc342a8 -[IDEDistributionDriver runWithDestinationPath:wantsExportStep:] + 1992 19 IDEFoundation 0x10bef081c closure #1 in RecoverableDistributionDriver.run() + 188 20 IDEFoundation 0x10be84b84 thunk for @escaping @callee_guaranteed @Sendable () -> () + 28 21 libdispatch.dylib 0x18f860750 _dispatch_call_block_and_release + 32 22 libdispatch.dylib 0x18f8623e8 _dispatch_client_callout + 20 23 libdispatch.dylib 0x18f865580 _dispatch_queue_override_invoke + 928 24 libdispatch.dylib 0x18f873ea8 _dispatch_root_queue_drain + 392 25 libdispatch.dylib 0x18f8746b8 _dispatch_worker_thread2 + 156 26 libsystem_pthread.dylib 0x18fa0efd0 _pthread_wqthread + 228 27 libsystem_pthread.dylib 0x18fa0dd28 start_wqthread + 8

I'm trying to notarize an Objective-C app I've written in Xcode 15. However, when I archive the app, it is listed as a "Generic Xcode Archive" instead of an "app archive", so it can't be validated/distributed. I've tried following all the steps in this article: https://developer.apple.com/documentation/technotes/tn3110-resolving-generic-xcode-archive-issue My skip_install is set to NO. My app's dependencies don't show up under "Targets" so I couldn't check the skip_install setting for them. My linked libraries don't use a headers build phase. My install_path is set to $(LOCAL_APPS_DIR). Why am I not getting an "app archive"?

Domain: com.apple.dt.CoreDeviceError Code: 3002 User Info: { DVTErrorCreationDateKey = "2024-04-12 13:00:55 +0000"; IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker; NSURL = "file:///Users/Username/Library/Developer/Xcode/DerivedData/project-dwlcjztonmnjygafwwnxdjtbzkwe/Build/Products/Debug-iphoneos/target.app/"; } -- Failed to install the app on the device. Domain: com.apple.dt.CoreDeviceError Code: 3002 User Info: { IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker; NSURL = "file:///Users/Username/Library/Developer/Xcode/DerivedData/project-dwlcjztonmnjygafwwnxdjtbzkwe/Build/Products/Debug-iphoneos/target.app/"; } -- The item at target.app is not a valid bundle. Domain: com.apple.dt.CoreDeviceError Code: 3000 Failure Reason: The path to the provided bundle's main executable could not be determined. Recovery Suggestion: Ensure that your bundle's Info.plist contains a value for the key CFBundleExecutable. User Info: { NSURL = "file:///Users/Username/Library/Developer/Xcode/DerivedData/project-dwlcjztonmnjygafwwnxdjtbzkwe/Build/Products/Debug-iphoneos/target.app/"; ProvidedBundle = "file:///Users/Username/Library/Developer/Xcode/DerivedData/project-dwlcjztonmnjygafwwnxdjtbzkwe/Build/Products/Debug-iphoneos/target.app/"; } -- Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : { "device_isCoreDevice" = 1; "device_model" = "iPhone12,1"; "device_osBuild" = "17.4.1 (21E236)"; "device_platform" = "com.apple.platform.iphoneos"; "dvt_coredevice_version" = "355.24"; "dvt_mobiledevice_version" = "1643.100.58"; "launchSession_schemeCommand" = Run; "launchSession_state" = 1; "launchSession_targetArch" = arm64; "operation_duration_ms" = 2486; "operation_errorCode" = 3000; "operation_errorDomain" = "com.apple.dt.CoreDeviceError.3002.com.apple.dt.CoreDeviceError"; "operation_errorWorker" = IDEInstallCoreDeviceWorker; "operation_name" = IDERunOperationWorkerGroup; "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_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" = 0; "param_diag_gpu_shaderValidation_enable" = 0; "param_diag_gpu_validation_enable" = 0; "param_diag_memoryGraphOnResourceException" = 0; "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_stopOnIssue" = 0; "param_diag_showNonLocalizedStrings" = 0; "param_diag_viewDebugging_enabled" = 1; "param_diag_viewDebugging_insertDylibOnLaunch" = 1; "param_install_style" = 0; "param_launcher_UID" = 2; "param_launcher_allowDeviceSensorReplayData" = 0; "param_launcher_kind" = 0; "param_launcher_style" = 99; "param_launcher_substyle" = 8192; "param_runnable_appExtensionHostRunMode" = 0; "param_runnable_productType" = "com.apple.product-type.application"; "param_structuredConsoleMode" = 1; "par[tag:am_testing_launchedForTesting" = 0; "param_testing_suppressSimulatorApp" = 0; "param_testing_usingCLI" = 0; "sdk_canonicalName" = "iphoneos17.4"; "sdk_osVersion" = "17.4"; "sdk_variant" = iphoneos; } System Information macOS Version 14.4.1 (Build 23E224) Xcode 15.3 (22618) (Build 15E204a) Timestamp: 2024-04-12T18:30:55+05:30 The project is running on the simulator properly with no errors. But while running on the real device (the iPhone), the build is successful but getting the mentioned issue. Also, while creating the.ipa file, we are getting the error mentioned below. I have tried following thing to resolve the issue but nothing is worked. Clean project and try to run the app on the real device. Disconnect iPhone from Mac On iPhone: Settings > Developer > Clear Trusted Computers Uninstall the application Reconnect iPhone to Mac In Xcode Window > Devices & Simulators You should see your device in the left sidebar Re-pair the device In the project Target -> Build Settings search for: search for Excluded Architectures add arm64 there. Change the archive destination directory to a location on the local SSD (and not an external HDD). Go to settings >> Select Privacy & Security >> Turn developer mode off if on >> Turn developer mode back on an follow instrctions >> The run your app on xcode ` Please help me find the solution. Thank you in advance.

Hello everyone!! I am writing to inquire about the procedures for testing an application I am developing for iOS devices. The application has been developed using Flutter, and I would like to make it available for testing on my colleague's iPhone, who serves as our QA tester. Currently, my account on the App Store is free, and I would like to ensure proper testing before proceeding with deployment to the Apple Store. As the application is quite large, I am unable to provide it in debug mode on the QA tester's device. Therefore, I would like to enable them to use the application on their personal device for a few days to provide comprehensive feedback on performance and features. Could you please provide guidance on how to proceed with this beta testing process? I am committed to adhering to all of Apple's guidelines and policies to ensure a high-quality user experience. I would be very grateful if anyone could help me out on this, Thank you.

I work on an app that includes a network extension. The app is essentially just to activate the extension, and the extension typically has long-running background sessions. Analyzing/monitoring metrics for the network extension is very important for us. However, in the Xcode Organizer screen, only the app itself is shown in the drop down menu - the associated network extension is not an option. For Xcode Organizer screens like Termination metrics and Battery Usage metrics, does the app's background metrics include the network extension, or just the app itself? If just the app, is there any way to get these metrics for the network extension?

Hello fellow developers, I've encountered a code signing issue during the archiving process in Xcode and I'm looking for some guidance. Here's the error message I received: codesign command failed (/var/folders/44/968_7v_972vb03blw9l1_sqr0000gn/T/XcodeDistPipeline.~~~k4kX6H/Root/Payload/SweetifyCrm.app/Frameworks/hermes.framework: replacing existing signature /var/folders/44/968_7v_972vb03blw9l1_sqr0000gn/T/XcodeDistPipeline.~~~k4kX6H/Root/Payload/SweetifyCrm.app/Frameworks/hermes.framework: invalid or corrupted code requirement(s) Requirement syntax error(s): line 1:140: unexpected token: SWEETIFY ) Here's what I've tried so far: Cleaned the build folder and rebuilt the archive. Ensured that the correct signing certificate and provisioning profile are in use. Checked .entitlements file for any syntax errors or misplaced tokens. Searched for the token "SWEETIFY" in my project, which is part of the development team name, but didn't find any irregularities. This error seems to be triggered when codesign is executed during the archiving process, specifically with the Hermes framework which is part of my React Native project. I'm using Xcode version 15.0.1, and my project includes Hermes as a JavaScript engine. The issue arises when I try to archive the app for distribution. The word "SWEETIFY" appears to be causing trouble, but it's merely part of the development team's name, (LLC "SWEETIFY"). Has anyone faced a similar issue or could offer some insight into what might be going wrong here? Any help or suggestions would be greatly appreciated! Thank you in advance for your time and help.

Archive a package. [Window] -> [Organizer] -> select package just archived -> click [Distribute App] select [App Store Connect] -> click [Distribute] -> CRASH! crash log Process: Xcode [12835] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 15.3 (22618) Build Info: IDEApplication-22618000000000000~2 (15E204a) App Item ID: 497799835 App External ID: 863955376 Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-04-15 11:05:05.6599 +0800 OS Version: macOS 14.4.1 (23E224) Report Version: 12 Anonymous UUID: E74ED973-D26C-0B5C-FDB1-837215F4F6B9 Sleep/Wake UUID: 6627EBDD-D3B7-4988-B9E5-BEDB5E1ED228 Time Awake Since Boot: 92000 seconds Time Since Wake: 11424 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Xcode [12835] Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x194e6aa60 __pthread_kill + 8 1 libsystem_pthread.dylib 0x194ea2c20 pthread_kill + 288 2 libsystem_c.dylib 0x194dafa20 abort + 180 3 libswiftCore.dylib 0x1a4f049f4 swift::fatalErrorv(unsigned int, char const*, char*) + 128 4 libswiftCore.dylib 0x1a4f04a14 swift::fatalError(unsigned int, char const*, ...) + 32 5 libswiftCore.dylib 0x1a4f04be0 swift::swift_abortRetainUnowned(void const*) + 48 6 libswiftCore.dylib 0x1a4f08f10 swift_unownedRetainStrong + 140 7 SwiftUI 0x1c1cea47c 0x1c075f000 + 22590588 8 SwiftUI 0x1c1cea42c 0x1c075f000 + 22590508 9 AppKit 0x198c517d4 -[_NSQuickActionAutovalidationScheduler windowDidUpdate:] + 140 10 CoreFoundation 0x194f76b1c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148 11 CoreFoundation 0x19500adb8 ___CFXRegistrationPost_block_invoke + 88 12 CoreFoundation 0x19500ad00 _CFXRegistrationPost + 440 13 CoreFoundation 0x194f45648 _CFXNotificationPost + 768 14 Foundation 0x196061464 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88 15 CoreFoundation 0x194fadd4c -[NSArray makeObjectsPerformSelector:] + 212 16 AppKit 0x1987dccb4 -[NSApplication(NSWindowCache) _updateWindowsUsingCache] + 108 17 AppKit 0x1987dcc0c -[NSApplication updateWindows] + 64 18 AppKit 0x198c19a3c __38-[NSApplication setWindowsNeedUpdate:]_block_invoke_2 + 56 19 AppKit 0x198c1eb6c ___NSRunLoopObserverCreateWithHandler_block_invoke + 64 20 CoreFoundation 0x194f81254 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 36 21 CoreFoundation 0x194f81140 __CFRunLoopDoObservers + 536 22 CoreFoundation 0x194f8076c __CFRunLoopRun + 776 23 CoreFoundation 0x194f7fe0c CFRunLoopRunSpecific + 608 24 HIToolbox 0x19f71b000 RunCurrentEventLoopInMode + 292 25 HIToolbox 0x19f71ac90 ReceiveNextEventCommon + 220 26 HIToolbox 0x19f71ab94 _BlockUntilNextEventMatchingListInModeWithFilter + 76 27 AppKit 0x1987d8970 _DPSNextEvent + 660 28 AppKit 0x198fcadec -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700 29 DVTKit 0x10313f858 -[DVTApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 300 30 AppKit 0x1987cbcb8 -[NSApplication run] + 476 31 DVTKit 0x10313eb24 -[DVTApplication run] + 60 32 AppKit 0x1987a2f54 NSApplicationMain + 880 33 dyld 0x194b1a0e0 start + 2360

No metrics data found for the latest app versions with sufficient usage. What is sufficient usage ? Can we define sufficient usage ourself ? if Yes then how ? https://developer.apple.com/videos/play/wwdc2020/10076/ wwwdc200 does mention factor of 5, but 5 of what ? and when where is the definition ? Organizer -> Metrics is useless if there is no data. If someone knows the fix please suggest.

When I do an archive build of my app against visionOS, the archive listing in the Organizer show the archive entry as iOS. So I have one archive build for iOS with a certain build number and another archive build for visionOS with another build number (incremented by 1) They are both listed in The Organizer but they both have iOS info. I’ve submitted them both separately to TestFlight and I’m about to try to test it on visionOS. Shouldn’t the visionOS archive build that I submit to TestFlight indicate something about visionOS instead of iOS?

Hello there. I'm having trouble with notarization in Xcode. I'm developing a Swift Mac app with Xcode 14, but even when I enable Hardened Runtime and perform notarization, it displays the message "Hardened Runtime is not enabled" and I can't proceed. The steps for notarization are [Window] -> [Organizer] -> [Distribute App] -> [Developer ID] [Next] -> [Upload]. Could you please tell me what I should check, or any other information? I've attached screenshots. Thank you.

I have a multiplatform app with a single target. I’ve been focused on making release updates for just visionOS where the new version doesn’t really have any changes to the iOS/iPadOS content. When I build and archive a new version and build number for my single app target, is it an ok practice to only release the new version and build to visionOS and not iOS? The reason I ask, is that the next time I get around to releasing a version and build that has any iOS changes that I want to release on the iOS App Store, it will have skipped one or more version numbers (due to only visionOS releases) from the last time that version was seen on the iOS App Store because I was only doing visionOS releases and versions prior to that.

Our iOS app also has a Safari Extension and a Packet Tunnel Extension. When trying to gather crash logs from the packet tunnel extension, we get an error like: ***@***[dot]com failed with error: Access Restricted. Even the account holder account was unable to access these crash logs. Is there any access level that does allow access, or are they restricted in all cases for all permission levels?

Hello, We encountered the following error while attempting to upload our visionOS app. Please note that this is not an iOS app; we have specifically built the framework for the arm64 visionOS platform. Incorrect Platform. You included arm64 executable “XX.app/Frameworks/XX” in your iOS bundle. Only iOS executables can be included.

Crash reports in Xcode Organizer are only partially symbolicated. Frames for the OS are symbolicated but the app is not. I've followed the guidance here but app frames are still not symbolicated. https://forums.developer.apple.com/forums/thread/690094 We archive, export ipa and upload our iOS app using the command line instead of with Xcode UI. Archive xcodebuild -project myproject.xcodeproj -scheme myproject -archivePath build/myproject_results.xcarchive archive Export IPA xcodebuild -exportArchive -archivePath build/myproject_results.xcarchive -exportPath ./build/ipa/ -exportOptionsPlist /path/to/ExportOptions.plist In ExportOptions.plist we set uploadSymbols to true <key>uploadSymbols</key> <true/> Upload xcrun altool --upload-app -t ios -f $ipa_path -u $appstore_connect_username -p $appstore_connect_password When inspecting the .ipa file, I see .symbols files in the Symbols folder. I verified that the UUID from our dSYM matches one of the UUID .symbols files as well. How would I fix or further debug this issue?