You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of Xcode 16, archiving an iOS app for submission to the App Store leads to a large number of warnings during the validation process.
Steps to reproduce
Generate a HelloWorld iOS app with Briefcase
Add a developer identity to the project
Select Archive from the Product menu
Select the recently generated archive from the list in the archive window
Click "Validate App", then Validate
Wait for the validation report
Expected behavior
No validation issues should be found.
Screenshots
No response
Environment
Operating System: macOS 15.3.2, Xcode 16.3
Python version: 3.13
Software versions:
Briefcase: 0.3.23
Logs
The validation log will list a single issue with Python.framework, and with each of the binary modules included in the app:
Upload Symbols Failed
The archive did not include a dSYM for the Python.framework with the UUIDs [87F39C90-34C0-3669-89EA-B18F5F01DBCC]. Ensure that the archive's dSYM folder includes a DWARF file for Python.framework with the expected UUIDs.
Upload Symbols Failed
The archive did not include a dSYM for the _asyncio.framework with the UUIDs [89363EE2-D685-3DF8-A31B-99A9E597B564]. Ensure that the archive's dSYM folder includes a DWARF file for _asyncio.framework with the expected UUIDs.
Upload Symbols Failed
The archive did not include a dSYM for the _blake2.framework with the UUIDs [9509B0A6-CB26-3D32-AAAB-E6A781581B15]. Ensure that the archive's dSYM folder includes a DWARF file for _blake2.framework with the expected UUIDs.
...
Additional context
These are warnings - they do not prevent submission of the app to the App Store. However, it would be desirable to have no warnings during the build process.
A dSYM folder can be generated after compilation using dsymutil <binary> -o <binary>.dSYM; however, it needs to be generated at the same time as compilation to ensure that source file references can be generated.
The text was updated successfully, but these errors were encountered:
Firstly - I've got a fix for this problem almost ready to land.
Secondly - there's no expectation that you work on everything, everywhere. Pick one project at a time, and contribute where you can. If you can't contribute... don't. There's no need to call out a bug asking for someone else to help unless it's something that you're (a) actively working on, or (b) it's actually impacting you personally.
Secondly - there's no expectation that you work on everything, everywhere. Pick one project at a time, and contribute where you can. If you can't contribute... don't. There's no need to call out a bug asking for someone else to help unless it's something that you're (a) actively working on, or (b) it's actually impacting you personally.
Sorry, I was trying to work too hard, apparently.
Firstly - I've got a fix for this problem almost ready to land.
Describe the bug
As of Xcode 16, archiving an iOS app for submission to the App Store leads to a large number of warnings during the validation process.
Steps to reproduce
Expected behavior
No validation issues should be found.
Screenshots
No response
Environment
Logs
The validation log will list a single issue with Python.framework, and with each of the binary modules included in the app:
Additional context
These are warnings - they do not prevent submission of the app to the App Store. However, it would be desirable to have no warnings during the build process.
A dSYM folder can be generated after compilation using
dsymutil <binary> -o <binary>.dSYM
; however, it needs to be generated at the same time as compilation to ensure that source file references can be generated.The text was updated successfully, but these errors were encountered: