Missing dSYM for PrivySDK.framework when Uploading Archive to TestFlight

[sjdthree]

Title
Missing dSYM for PrivySDK.framework when Uploading Archive to TestFlight

Description
When uploading a build to TestFlight, we receive this error (also see screenshot below):

The archive did not include a dSYM for the PrivySDK.framework with the UUIDs [83CEFC36-548E-3269-BD26-1A353ED15096].
Ensure that the archive's dSYM folder includes a DWARF file for PrivySDK.framework with the expected UUIDs.

Steps to Reproduce
1. Include PrivySDK.framework in the project.
2. Build and archive the app.
3. Attempt to upload the archive to TestFlight.
4. Observe the dSYM missing error.

Expected Behavior
• The archive should contain a matching dSYM for PrivySDK.framework, and the upload to TestFlight should succeed without error.

Observed Behavior
• Xcode reports that the dSYM for PrivySDK.framework is missing or does not match the expected UUID.

Possible Causes
• “Debug Information Format” for Release might not be set to DWARF with dSYM File.
• Bitcode settings could be misconfigured or inconsistent with the SDK.
• PrivySDK might not ship the matching dSYM for the distributed framework.

Proposed Solutions include:
• Verify DWARF with dSYM File is enabled for the Release build configuration.
• Ensure bitcode settings align with PrivySDK’s capabilities (either both enabled or both disabled).
• Confirm you have the correct framework + dSYM files for PrivySDK.

Environment
• Xcode version: Version 16.2 (16C5032a)
• iOS Deployment Target: iOS 17.6
• PrivySDK version: 1.8.0

Additional Context

[sjdthree]

Note: I see it's only a warning. So you can actually proceed and push your app out to testers within testflight.

[jagtejsodhi]

Hey @sjdthree, sorry for the delay here. Can you please upgrade to our 2.0.0 release and let me know if the problem persists? Please refer to our migration guide if updating from 1.Y.Z.