-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
Unable to map error #41
Comments
sane error : Unable to map 898765/3810818 bytes (23.58%) |
In what way does it fail? Output looks good to me.. |
I had this same problem, and at least in my case, the solution was knowing where to look for the output... My experience:I run My setup:I host all of my projects on a different machine than the one I sit at. It is a server on my local network. I access everything over SSH on that host machine. What went wrong:The reason "nothing happened" is because *a browser window was automatically opened which displays the visualizer's output - but that browser happens to be on my host machine, not the one I am sitting in front of!* I then found this ticket, wherein the OP and others appear to be reporting an error/failure, and at the same time the moderator sees nothing wrong... A little later, when I happened to turn on my server's monitor, there were all of my visualization tabs opened in a browser... How to "fix" it:@deathemperor @novonimo I recommend you suspect your browser setup. Where is your browser? Is it on your local machine, is it somewhere else, can it be opened automatically? @IjzerenHein I think it would be useful if two things were added:
Not everyone does local dev on the same machine where their project files are located (code-server users, some enterprise setups, anyone who runs a local server like I do). VS Code and others provide built-in support for sshing into a different machine. I turn off browsersync on projects, because they would always open on that different host machine... So to take this a step further, people with a setup similar to mine are also going to want the ability to disable the automatic browser opening, and instead manually go to the URL which needs to be outputted to CLI. |
Was also having this issue, for myself it was not actually an error but the output was not showing, this was due to me running it in WSL on Windows and it was not opening the webpage. Doing it in Powershell made it work file. If you really want to run it in WSL you may be able to open the webpage manually which is located in Windows at: |
I was also running in WSL, and I had to go into /tmp/react-native-bundle-visualizer to find the explorer.html after running this tool in WSL |
Generating bundle... info Writing bundle output to:, C:\Users\aksha\AppData\Local\Temp\react-native-bundle-visualizer\Hinduzz\android.bundle |
@akshay-khapare have you found any solution on this issue ? |
I was able to run a couple weeks ago but failed continuously today without any error.
The text was updated successfully, but these errors were encountered: