-
Notifications
You must be signed in to change notification settings - Fork 24.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty dSYM issue #46243
Comments
|
|
As I mention in another issue, you can download the dSYMs from here. Alternatively, you can open the hermes.xcframework file and remove the lines pointing to the dSYMs from the <dict>
<key>AvailableLibraries</key>
<array>
<dict>
<key>BinaryPath</key>
<string>hermes.framework/hermes</string>
- <key>DebugSymbolsPath</key>
- <string>dSYMs</string>
<key>LibraryIdentifier</key>
<string>xros-arm64-simulator</string>
<key>LibraryPath</key>
<string>hermes.framework</string>
<key>SupportedArchitectures</key>
<array>
<string>arm64</string>
</array>
<key>SupportedPlatform</key>
<string>xros</string>
<key>SupportedPlatformVariant</key>
<string>simulator</string>
</dict>
<dict>
<key>BinaryPath</key>
<string>hermes.framework/hermes</string>
- <key>DebugSymbolsPath</key>
- <string>dSYMs</string>
<key>LibraryIdentifier</key>
<string>ios-arm64_x86_64-maccatalyst</string>
<key>LibraryPath</key>
<string>hermes.framework</string>
<key>SupportedArchitectures</key>
<array>
<string>arm64</string>
<string>x86_64</string>
</array>
<key>SupportedPlatform</key>
<string>ios</string>
<key>SupportedPlatformVariant</key>
<string>maccatalyst</string>
</dict>
<dict>
<key>BinaryPath</key>
<string>hermes.framework/hermes</string>
- <key>DebugSymbolsPath</key>
- <string>dSYMs</string>
<key>LibraryIdentifier</key>
<string>ios-arm64</string>
<key>LibraryPath</key>
<string>hermes.framework</string>
<key>SupportedArchitectures</key>
<array>
<string>arm64</string>
</array>
<key>SupportedPlatform</key>
<string>ios</string>
</dict>
<dict>
<key>BinaryPath</key>
<string>hermes.framework/hermes</string>
- <key>DebugSymbolsPath</key>
- <string>dSYMs</string>
<key>LibraryIdentifier</key>
<string>ios-arm64_x86_64-simulator</string>
<key>LibraryPath</key>
<string>hermes.framework</string>
<key>SupportedArchitectures</key>
<array>
<string>arm64</string>
<string>x86_64</string>
</array>
<key>SupportedPlatform</key>
<string>ios</string>
<key>SupportedPlatformVariant</key>
<string>simulator</string>
</dict>
<dict>
<key>BinaryPath</key>
<string>hermes.framework/hermes</string>
- <key>DebugSymbolsPath</key>
- <string>dSYMs</string>
<key>LibraryIdentifier</key>
<string>xros-arm64</string>
<key>LibraryPath</key>
<string>hermes.framework</string>
<key>SupportedArchitectures</key>
<array>
<string>arm64</string>
</array>
<key>SupportedPlatform</key>
<string>xros</string>
</dict>
</array>
<key>CFBundlePackageType</key>
<string>XFWK</string>
<key>XCFrameworkFormatVersion</key>
<string>1.0</string>
</dict>
</plist> |
Thanks for your response, by the way, I need your explanation more how to use the downloaded dSYMs file? I need you instruction how I can use this downloaded file... |
the dSYM is used to symbolicate stack traces. If you don't need to symbolicate the stack traces, it's easier to just remove the entries above, honestly |
Thanks. |
I am sorry to reopen this issue since I got some crash issues from apple after upload the app. |
@soft7store These are application errors as you can see by searching for Also, we are not a support channel for every app developer. You need to spend some time yourself to understand first if the problem is coming from React Native, a library or your app. Let's try to investigate the problem and if it persists and comes from some React Native specific component, please open a dedicate issue as the crashes are unrelated to Hermes. |
Hi were I need to move the downloaded dsym? And I am using RN 0.74.5, will be fine using this? I did tried the alternative by updating the Info.plist, but seems the issue still their |
If you want to go down to that path, you have to:
|
My solution for RN 0.76.3 is here. |
does not work... |
I recently faced this issue with RN 76.3. What I did is to upgrade to 76.5 and it is working now. Hopefully it helps someone out there 😸 |
I'm facing this issue in the RN 0.75.4 Is there any solution other than upgrading RN project? |
0.75 hasn't been released with the fix yet, sadly. So that's normal that the problem is still there. If you can, I suggest you to upgrade to 0.76.6. For the other people, it could be that you are using a cached version of the hermes-engine artifacts.
To make sure you clean up the whole system, and then rerun |
Description
React-Native : 0.73.9
Also when I run the project in debug mode, I encountered the issue log : "App empty dSYM file detected, dSYM was created with an executable with no debug info."
When I archive the app for appstoreconnect uploading, I faced this error.
The archive did not include a dSYM for the hermes.framework with the UUIDs [35FECC83-9599-34C1-813E-F020B2D0D382]. Ensure that the archive's dSYM folder includes a DWARF file for hermes.framework with the expected UUIDs.
I have no idea to fix this issue.
Can you guide me how to fix it?
Steps to reproduce
App empty dSYM file detected, dSYM was created with an executable with no debug info.
React Native Version
0.73.9
Affected Platforms
Runtime - iOS
Output of
npx react-native info
Stacktrace or Logs
Reproducer
https://github.com/soft7store
Screenshots and Videos
No response
The text was updated successfully, but these errors were encountered: