"main.jsbundle does not exist" error when building iOS version locally with Expo SDK 47 using eas-cli #1516
Comments
lindan4
changed the title
|
having the same issue but on non local. I don't know how to get fastlane to generate a main.jsbundle |
|
Reported in the main repo as well. Apparently, it's being looked at. expo/expo#20001 |
|
I was able to fix my issue by following this: https://stackoverflow.com/a/57889288/5395605 I think using the postinstall script allowed main.jsbundle to be generated during fastlane process. |
dsokal
added
eas build
bug
|
This has already been addressed here |
|
This should be resolved with |
|
``Hi, How can I upgrade safely to 47.0.7 ? |
|
I upgraded but I see the exact same error. |
Did you find a solution? |
|
You are probably running an old version of expo-cli. I would update that, and try again: |
|
@izakfilmalter, thanks! I did it, my version is 6.1.0. The output is this:
And the error persists. |
|
I have this error when I build with eas remote build too. |
|
This is my error output: |
|
SOLVED! For anyone: the problem wasn't .gitignore or .easignore, it was that that image that was "missing" had an accent, "Alì---Aliper.jpg". I renamed it to remove the accent and now it is working. Very weird error. Please, print a better error during build time! |
|
@FrancescoBonizzi I am facing the same error, so do I need to look for a missing Image? |
Make the build online, uploaded to eas servers. The download Xcode logs and search for some errors there! |
|
Was still happening for me locally with expo 47.0.13 this weekend. To fix, open you project in Xcode, Go to build phases, Then also in Build Phase Script, start packager, line 17, The Xcode project well then build. I haven't got the "EAS local build" to work yet, as Xcode was saving the new scripts to the /Users/MyUser/Library/Developer/Xcode/DerivedData and not to "Expo/Eas IOS directory" for my project: Anyone know how to make Xcode save the scripts to there? |
|
Dealing with this same issue.. +1 on this still being a problem. |
|
I'm having the same issue, failing the build with eas. I am using expo managed workflow so don't have option to make changes in xCode for the eas build. Is there any workaround? How can we get this issue open again? |
|
Updated expo to v48, getting the same error "main.jsbundle" does not exist, under 48 as 47. |
|
For me, this was that there was a compiler error buried in the FASTLANE logs. I had used a fairly modern Javascript "usage" (i.e. x ||= y) and that wasn't interpreted well by FASTLANE. When I changed my Javascript to a more normal/old javascript construct, I was able to compile. |
|
If you're still having this issue, this might work: expo/expo#21542 (comment) |
|
@cspeer Yes it worked for me. Thank you |
|
@FrancescoBonizzi is correct. Download your Xcode log on your expo build details page. You will find imports with special characters (maybe in spanish?) and xcode is unable to find them. Just replace them. |
Done! That was the problem. Thanks! |
have you figured it out??? |
SOLVED! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Build/Submit details page URL
App is built with --local flag
Summary
I am trying to build the iOS version of an application locally whose Expo version I had upgraded to version 47. I have no issues building the Android version but run into issues when building the iOS. I can build the iOS version when I generate the Xcode project myself but cannot via eas.
Managed or bare?
Managed
Environment
expo-env-info 1.0.5 environment info:
Expo doctor output:
Error output
Reproducible demo or steps to reproduce from a blank project
npx eas build --platform ios --non-interactive --local --profile previewThe text was updated successfully, but these errors were encountered: