-
Notifications
You must be signed in to change notification settings - Fork 24.5k
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
[iOS] Upload Symbols Failed on Xcode 16 #46853
Comments
|
|
@zzz08900 Thanks for the issue. we fixed that already with this commit f529fe4, but we forgot to cherry pick it. Let me create pick requests for that. To unblock yourself, you can
<key>DebugSymbolsPath</key>
<string>dSYMs</string>
|
Fixed in the release candidate v0.76 |
I have tried this on 0.74.6 and previously on 0.73.8. but the warning still does not disappear when i remove the lines. |
Thanks for the fix in 0.76, in the mean time: Does anyone know how to patch this fix so that it stays in place after a re-install? If I run the following:
Then the fix is reverted and the error persists. |
I have tried this on version 0.74.2, but the warning still appears when validating the archive. |
We should backport the fix to previous versions then. |
Still same warning after uploading to appstoreconnect with "react-native": "0.76.3".
|
That's surprising.. If the Info.plist does not have any |
Should this be re-opened? As it seems that the issue is still present in 0.76.3 |
What I did for now to fix the issue on RN 0.76.3.
#!/bin/bash
echo "[Custom Script] Copy dSYMs to hermes-engine 1"
# Define source and destination paths
SOURCE_PATH=${PROJECT_DIR}/dSYMs
DEST_PATH=${PROJECT_DIR}/Pods/hermes-engine/destroot/Library/Frameworks/universal/hermes.xcframework/ios-arm64/
echo "[Custom Script] Copy dSYMs to hermes-engine 2 $SOURCE_PATH"
echo "[Custom Script] Copy dSYMs to hermes-engine 2 $DEST_PATH"
# Check if source directory exists
if [ ! -d "$SOURCE_PATH" ]; then
echo "[Custom Script] Copy dSYMs to hermes-engine 3 $DEST_PATH"
echo "Error: Source directory $SOURCE_PATH does not exist"
exit 1
fi
# Copy the directory
cp -R "$SOURCE_PATH" "$DEST_PATH"
echo "[Custom Script] Copy dSYMs to hermes-engine 4 $DEST_PATH"
echo "Successfully copied dSYMs to Hermes destination"
|
Having the same issue on react-native 0.76.3 |
Having the same issue on react-native 0.76.2 BTW does this error have any bad effect? |
my react native ios give this error i am using a xcode version 16 and my react native version is 74 i can try this but still i get this error i can use this chat all related answer but not working please help |
I have the same issue, tried this solution but it didn't work for me. |
The need to download the dSYM files with every package update is overly burdensome. |
Strange, my own solution even doesn’t work anymore in RN 76.5. 1 - Copying Now, the archive had been uploaded to AppStore Connect but it's still showing the error in XCode. |
I am tempted to turn off hermes which in any case makes start-up very slow in iOS |
There are some issues related to Xcode 16 that might make this worse: https://forums.developer.apple.com/forums/thread/763731?page=4 It might not be a React Native problem, as many other libraries are affected Out of curiosity, is there someone that is encountering this issue and that is developing using Expo and uploading with EAS? |
@cipolleschi Hello, in my case, I moved an application that I built with eas and successfully sent to testflight to cli due to sdks that do not support expo. |
Any updates on this? I still get the error in react native version: 0.76.6 |
Which version of Xcode are you using? Are you uploading a Debug or a Release App? The error makes no sense to me, because there are no references to the dSYMS in the Hermes.xcframework... |
I'm getting the same symptom with RN 0.72 when I upgradef from older XCode to XCode 16 in order to ,make debug builds for an iOS 18 device. I"m trying to upload a release build. Since I was doing this same build pre XCode 16, I'm asssuming this wartning is just letting me know aomehting about my bujilds thay is not new as I didn't otherwize change anything about my RN bujild other than moving to XCode 16.... |
did anyone find the solution I'm still looking for solution nothing works here |
|
yeah i just got this too... the app seems to upload to testflight still but it's weird and interesting nonetheless |
@cipolleschi Ran that just now on Xcode 16.2 and RN 0.76.6, and still get the error... |
As well here: |
I think i checked all the options in the comments and none of them work, I am still getting error :( |
Also having the same issue for quite some time. XCode 16.2, |
I verified with Expo and they are not doing anything different than uploading the same artifacts we ship as you would do without Expo. This must be a local configuration otherwise the upload would be broken for everyone or for nobody. Out of curiosity: are you uploading a Debug build or a Release build? |
Same issue with RN 0.77.0 and Xcode 16.2. WorkaroundTo resolve this issue, I added the following script to the Pre-actions of the Archive step in Xcode’s scheme settings. generate-hermes-dsym.shif [[ -z "$1" ]]; then
echo "❌ Usage: $0 <TargetName>"
exit 1
fi
TARGET_NAME=$1
export ARCHIVE_PATH=$(ls -dt ~/Library/Developer/Xcode/Archives/*/"$TARGET_NAME"*.xcarchive | head -1)
echo "📦 Using Archive Path: $ARCHIVE_PATH"
if [[ ! -d "$ARCHIVE_PATH" ]]; then
echo "❌ Archive not found for target: $TARGET_NAME! Please archive the project first in Xcode."
exit 1
fi
echo "🔍 Existing dSYM files:"
find "$ARCHIVE_PATH/dSYMs" -name "*.dSYM"
export HERMES_BINARY=$(find "$ARCHIVE_PATH/Products/Applications" -name "hermes.framework" -type d)
echo "📍 Hermes Binary Path: $HERMES_BINARY"
if [[ ! -d "$HERMES_BINARY" ]]; then
echo "❌ Hermes framework not found!"
exit 1
fi
dsymutil "$HERMES_BINARY/hermes" -o "$ARCHIVE_PATH/dSYMs/hermes.framework.dSYM"
echo "✅ Hermes dSYM generated at: $ARCHIVE_PATH/dSYMs/hermes.framework.dSYM"
echo "📂 Final dSYM files:"
find "$ARCHIVE_PATH/dSYMs" -name "*.dSYM"
echo "🎉 Done! Hermes dSYM successfully generated!" Xcode Pre-actions SetupIn Edit Scheme → Archive → Pre-actions, add the following script
|
Facing the same issue on Xcode 16.2 |
Still getting same issue.
@cipolleschi - I followed the above steps in my project. My project has react-native:0.73.7. |
I believe something is wrong with Xcode 16.2. Those steps use to work with previous versions of Xcode when this was happening. Sadly, there is very little I can do as we don't control Xcode. For anyone reading: what you are seeing is just a warning. It does not prevent you from upload and submit your app and Apple will not reject your app because of missing debug symbols in the release binary. |
This issue still exists even today, can we not request to reopen this issue for tracking? |
The issue is duplicated by other issues.
I'll lock this and the other two that are closed already, please forward all the comments to the one open: #49059 |
Description
So everything looks to be working fine, but when building .ipa/uploading to AppStore Connect I got this warning:
The archive did not include a dSYM for the hermes.framework with the UUIDs *****
Although everything seems to be in working order (the ipa is successfully uploaded to AppStore Connect), I'm wondering if there's a way to get rid of this warning.
Steps to reproduce
npx @react-native-community/cli@latest init rnTest1 --version 0.74.5
React Native Version
0.74.5
Affected Platforms
Other (please specify)
Output of
npx react-native info
Stacktrace or Logs
Reproducer
https://github.com/zzz08900/react-native-hermes-dSYM
Screenshots and Videos
The text was updated successfully, but these errors were encountered: