stasel
commented
1 month ago According to the dev forums, It seems to be a temporary bug in the new Xcode. Was this requirement officially mentioned anywhere?
Open mpretty-cyro opened 1 month ago
stasel
commented
1 month ago According to the dev forums, It seems to be a temporary bug in the new Xcode. Was this requirement officially mentioned anywhere?
mpretty-cyro
commented
1 month ago Nah I couldn't find anything in the release notes, annoyingly no one from Apple has replied to that particular thread but based on their responses in https://forums.developer.apple.com/forums/thread/761589 it seems like you're right and it's probably a bug with Xcode 😞
Hopefully they fix it in 16.1
mpretty-cyro
commented
1 month ago Just a small update on this, a DTS engineer responded to one of the threads: https://forums.developer.apple.com/forums/thread/761589?answerId=806733022#806733022
This is a new warning in Xcode 16 where if you're missing a dSYM, Xcode lets you know in case you aren't expecting that — this is to reduce scenarios where you won't are able to fully symbolicating frames coming from your app's code in crash reports. In some cases, you may not have a dSYM, such as a closed source library from a vendor, and in those cases, the warning is safe to discard.
So it sounds like it's a feature rather than a bug, but is just a warning that can be ignored - I'll update the title of this issue accordingly:
It seems that as of Xcode 16 the App Store validation now requires app include dSYM information for each framework embedded - building with Xcode 16 and submitting now gives the following error:
Building and submitting with Xcode 15.3 is working without issue though (for anyone else running into this issue)
Seems like quite a few people have started running into the same issue: https://forums.developer.apple.com/forums/thread/763731