-
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
main.jsbundle does not exist. This must be a bug with "react-native": "0.63.4" #31025
Comments
May you try with this? |
@teamzz111, yes I tried it, the same error |
@teamzz111, same for me too tried #29351 (comment) too still no change :( |
@teamzz111 no I am using JS |
We have the same issue. A regular build works, an archive build fails. |
same here. regular build works, archive fails ! |
I ran into this in a mono-repo setting. The solution I found is here react-native-community/cli#656 (comment) |
See #31094 (comment) |
any update goes same thinks |
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as a "Discussion" or add it to the "Backlog" and I will leave it open. Thank you for your contributions. |
This issue was closed because it has been stalled for 7 days with no activity. |
I figured out
main.jsbundle does not exist. This must be a bug with
issue after upgrading react native from 0.63.3 to 0.63.4 and it was solved,but now when I tried to Archive a build the same error appears.
when I tried to see the main.jsbundle file from the path generated using archive build using cmd to see if it's exist, the path is true, but the file doesn't exist.
I thought that I did a wrong thing in my project, by adding a wrong code or something else in Xcode, then I created a new react-native project and tried to Archive a build, but the same error appears.
here is the system info:
thanks 🙏
The text was updated successfully, but these errors were encountered: