[iOS]The archive did not include a dSYM for the AdjustSigsSdk.framework with the UUID

[AdamZay]

The archive did not include a dSYM for the Adjust SigSdk.framework with the UUIDs
[D43EE3FF-476C-3898-8D78-7519F7C91E57]. Ensure that thearchive's dSYM folder includes a
DWARF file for AdjustSigSdk.framework with the expected UIDs

[rscloura]

Hi @AdamZay. This warning appears due to the lack of debugging information for the Signature library, and shows only from Xcode 16 onwards. The lack of debugging information is intentional, and so the warning is expected. Debugging information has no impact on the execution of the underlying code, and the warning is safe to ignore.

[LazyDebuggerr]

But even we ignore the issue, the build doesn't appear on App Store connect

[rscloura]

Hi @LazyDebuggerr. I'm afraid failing to upload the build to App Store Connect is unrelated to debugging symbols or lack thereof. The lack of a DWARF file for frameworks is well documented, and even expected in cases such as this. Here's an example of an Apple engineer facing this exact situation. I quote:

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.

We also have no other reports, and no internal reproducibility. Are you sure the upload failure is due to Signature? If so, does it fail with an error, and which error? What Signature version have you integrated?

[LazyDebuggerr]

The upload didn't failed. The build uploaded successfully but on the test flight the bundle doesn't appear

…

On Wed, 17 Dec 2025 at 16:12, Ricardo Loura ***@***.***> wrote: *rscloura* left a comment (adjust/flutter_sdk#182) <#182 (comment)> Hi @LazyDebuggerr <https://github.com/LazyDebuggerr>. I'm afraid failing to upload the build to App Store Connect is unrelated to debugging symbols or lack thereof. The lack of a DWARF file for frameworks is well documented, and even expected in cases such as this. Here <https://developer.apple.com/forums/thread/761589?answerId=806733022#806733022>'s an example of an Apple engineer facing this exact situation. I quote: 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. We also have no other reports, and no internal reproducibility. Are you sure the upload failure is due to Signature? If so, does it fail with an error, and which error? What Signature version have you integrated? — Reply to this email directly, view it on GitHub <#182 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BL56KZI3TL4DF62C2AWVJS34CE3BZAVCNFSM6AAAAACNOB3IZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNRUHA3DKOBXGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[rscloura]

@LazyDebuggerr The issue you're experiencing seems to be unrelated to debugging symbols. Could you please open a new issue, describing the steps you took? In particular, please include the following details:

• App token.
• SDK version.
• Signature version (if manually integrated).
• Whether the app successfully shows in App Store Connect without Signature.
• Any upload logs that might be available.