microsoft/clarity

Issue: dSYM File Missing for Clarity.framework

Closed this issue · 10 comments

somangoi commented

Summary:

When archiving my project in Xcode, I am encountering an error related to the missing dSYM file for Clarity.framework. The UUID for the missing dSYM file is [0370CC1D-7770-379A-A5A1-D8EB736BD176]. This issue prevents me from successfully uploading the archive to App Store Connect. And when I just install the test flight app, it crashes right away on the actual device.

Error Message:

image

Upload Symbols Failed The archive did not include a dSYM for the Clarity.framework with the UUIDs [0370CC1D-7770-379A-A5A1-D8EB736BD176]. Ensure that the archive's dSYM folder includes a DWARF file for Clarity.framework with the expected UUIDs.

Steps to Reproduce:

  1. Create an archive of the project in Xcode.
  2. Observe that the upload to App Store Connect fails due to a missing dSYM for Clarity.framework.

Expected Outcome:

The archive should include the required dSYM file for Clarity.framework, and the upload process should complete successfully without any errors.

Actual Outcome:

The archive does not include a dSYM file for Clarity.framework, causing the upload to App Store Connect to fail.

System Info:

  • Xcode version: 16.0
  • Clarity and react version:
    "react": "18.2.0",
    "react-native": "0.74.5",
    "react-native-clarity": "^3.0.4",

Additional Information:

I have confirmed that DWARF with dSYM File is selected in my Xcode project settings under Debug Information Format. This issue persists despite cleaning the build and ensuring that other dSYM files are generated properly.

Could you please advise on how to resolve this issue or provide a workaround?

amralaa-MSFT commented

@somangoi Thank you for reporting this issue! We will investigate this issue. Meanwhile, could you please let us know if you've ever succeeded to archive and upload your app using Clarity before upgrading to Xcode 16?

somangoi commented

@somangoi Thank you for reporting this issue! We will investigate this issue. Meanwhile, could you please let us know if you've ever succeeded to archive and upload your app using Clarity before upgrading to Xcode 16?

Thanks for replying. There was no problem with 15.4.

amralaa-MSFT commented

@somangoi Thank you for conforming! Could you please answer these questions:

  1. Do you get the same error if you only build the project in Xcode (both in Debug and Release configurations)?
  2. Does your app crash when run on an iOS 18 device?
  3. Do you have more detailed error messages, e.g. in the Report navigator view? If so, could you please share them?
somangoi commented

@amralaa-MSFT

Do you get the same error if you only build the project in Xcode (both in Debug and Release configurations)?

When I build, there was no issue until I uploaded to testflight.

Does your app crash when run on an iOS 18 device?

On iPhone 16 that uses iOS 18, it crashes.

Do you have more detailed error messages, e.g. in the Report navigator view? If so, could you please share them?

The error only shows during the process of uploading to testflight, so I'm afraid that there is no further information. But I will try to find one and update you on this thread. Thanks..!

abrarulhaq7 commented
Screenshot 2024-09-30 at 5 39 30 PM I am also getting these similar warnings while archiving Xcode project. (Image attached) This is my first time I am archiving my project.
  • 👍1
amralaa-MSFT commented

Screenshot 2024-09-30 at 5 39 30 PM I am also getting these similar warnings while archiving Xcode project. (Image attached) This is my first time I am archiving my project.

@abrarulhaq7 These errors seem unrelated to Clarity. Do you also get the same errors if you try removing Clarity from your project?

amralaa-MSFT commented

@somangoi Unfortunately, I'm not able to reproduce the issue because I have no access to a quick way to publish an app. This issue seems to be unrelated to Clarity as other developers reported the same errors with other libraries after updating to Xcode 16.

However, there might be a workaround but I'm not sure if it fixes your issue. So, I would appreciate if you can try the following and let me know how it went:

  1. Create a file named fix-clarity.sh in next to package.json file with the following content:
#!/bin/bash

THIS_DIR="$(realpath "$(dirname "$BASH_SOURCE")")"

strip=`xcrun -sdk iphoneos --find bitcode_strip`

strip_it () {
    local file=$1

    echo ">>> bitcode_strip $file"
    cp $file "${file}.bak"

    echo ">>> before: $(ls -la $file)"
    $strip -r $file -o $file
    echo ">>> after: $(ls -la $file)"

    echo ''
}

strip_it $THIS_DIR/ios/Pods/Clarity/Clarity.xcframework/ios-arm64/Clarity.framework/Clarity
strip_it $THIS_DIR/ios/Pods/Clarity/Clarity.xcframework/ios-arm64_x86_64-simulator/Clarity.framework/Clarity
  1. Execute the script using bash fix-clarity.sh.
  2. Try building and publishing from Xcode.
  • 👀1
aliffarisqi commented

Screenshot 2024-09-30 at 5 39 30 PM I am also getting these similar warnings while archiving Xcode project. (Image attached) This is my first time I am archiving my project.

hi @abrarulhaq7 i have smae issue like that, do you have the way to solve ?

liangjiazhang commented

遇到了和楼主同样的问题，请问该怎么解决？

amralaa-MSFT commented

Developers have been facing the same issue with lots of other libraries after upgrading from Xcode 15 to Xcode 16.
Some have found workarounds to bypass the warning and publish their apps successfully.

Keep an eye on this thread (https://forums.developer.apple.com/forums/thread/763731) for updates and potential solutions.

Please let us know if there's anything specific we can fix as library owners.

  • 👍1