is there a fix available?
There’s nothing really to fix here. Lemme explain…
In general:
If you’re using Xcode, both the binary and its .dSYM file end up within your Xcode archive.
Historically, Apple allowed, and in some cases required, apps to submit as bitcode. Apple then recompiled the app from that bitcode, and distributed that binary to end users.
That caused problems for symbolication because the binary being run by end users didn’t match the .dSYM file in your Xcode archive. To solve this, Apple created a mechanism for you to download a .dSYM file for the binary that Apple generated.
With Xcode 14, so about a year ago, Apple stopped doing the bitcode thing. To quote the Xcode 14 Release Notes.
Starting with Xcode 14, bitcode is no longer required for watchOS and tvOS applications, and the App Store no longer accepts bitcode submissions from Xcode 14.
So, the whole reason for downloading .dSYM files is now gone, and folks can go back to what they used to do before bitcode was a thing: Build the binary and it’s .dSYM locally and use that for symbolication.
If you have a process that relies on getting a .dSYM file from Apple, please update that process to work with your locally built file.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
-
—
bkirby_abra
-
—
Hue Essentials
-
—
scott222
Add a CommentI'm seeing the same thing. I wonder if it's related to the new submission system. It changed recently to allow multiple submissions at the same time. This was the first build using this new system that is missing dsyms.
Same issue here. Already submitted multiple builds but still no debug symbols available for download.
We've also submitted two different apps on Friday and neither of them have dSYMs as of today (monday)