question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

main.jsbundle not found for ios

See original GitHub issue

Environment

System: OS: macOS 10.15.5 CPU: (4) x64 Intel® Core™ i5-5257U CPU @ 2.70GHz Memory: 239.48 MB / 8.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 12.18.2 - ~/.nvm/versions/node/v12.18.2/bin/node Yarn: 1.10.1 - /usr/local/bin/yarn npm: 6.14.5 - ~/.nvm/versions/node/v12.18.2/bin/npm Watchman: 4.9.0 - /usr/local/bin/watchman Managers: CocoaPods: 1.9.3 - /Users/ivo/.rbenv/shims/pod SDKs: iOS SDK: Platforms: iOS 13.5, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2 Android SDK: API Levels: 24, 27, 28, 29 Build Tools: 28.0.3, 29.0.2 Android NDK: 20.0.5594570 IDEs: Android Studio: 3.4 AI-183.6156.11.34.5692245 Xcode: 11.5/11E608c - /usr/bin/xcodebuild Languages: Java: 1.8.0_131 - /usr/bin/javac Python: 2.7.16 - /usr/bin/python npmPackages: @react-native-community/cli: Not Found react: 16.13.1 => 16.13.1 react-native: 0.63.0 => 0.63.0 npmGlobalPackages: react-native: Not Found

Upgrading version

0.63

Problem

Running xcode build result in main.jsbundle not found

Solution

I had imports like this:

import Component from '..'

replacing these imports with relative paths seems to have resolved the issue. Here is my SO answer to a question regarding main.jsbundle for 0.63

Issue Analytics

  • State:open
  • Created 3 years ago
  • Reactions:1
  • Comments:12

github_iconTop GitHub Comments

4reactions
umang-simformcommented, Jul 13, 2020

I am also facing same issue.

1reaction
EmpireJonescommented, Jul 12, 2020

This seems to be related to usage of babel-plugin-module-resolver in my case. Were you using that too?

I haven’t figured out a workaround yet. Removing usage of that plugin isn’t really a great solution.

Read more comments on GitHub >

github_iconTop Results From Across the Web

main.jsbundle does not exist. This must be a bug with #29356
I even checked the dir and indeed, there is NO main.jsbundle file in there. ... Build fails for iOS: main.jsbundle does not exist...
Read more >
main.jsbundle does not exist. this must be a bug with + echo ...
ios /main.jsbundle' --dev=false --platform='ios' because of heap memory error But I am not able to find where is main.jsbundle.
Read more >
main.jsbundle does not exist [fixed] | by Onexlab - Medium
Open the package.json file and add the following line · Run following command. It will generate main. · Select -> Target → Build...
Read more >
main.jsbundle: No such file or directory issue fixed - YouTube
react native iso main. jsbundle issue fixedmain.jsbundle: No such file or directorymain.jsbundle does not exist. this must be a bug with + ...
Read more >
Impossible to build archive | Apple Developer Forums
... Build / Intermediates.noindex / ArchiveIntermediates / JDC / BuildProductsPath / Release-iphoneos / jdc.app / main.jsbundle does not exist.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found