Skip to content
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

React Packager "Unexpected raw mappings" in 0.43.0-rc.2 #12895

Closed
pocesar opened this issue Mar 13, 2017 · 25 comments
Closed

React Packager "Unexpected raw mappings" in 0.43.0-rc.2 #12895

pocesar opened this issue Mar 13, 2017 · 25 comments
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.

Comments

@pocesar
Copy link

pocesar commented Mar 13, 2017

Description

After starting Perf Monitor with Dev settings off, React Packager eventually choked without me doing anything with:

 ERROR  Unexpected raw mappings for G:\mobile\cadastro\lib\root.js
{"name":"Invariant Violation","framesToPop":1}
Invariant Violation: Unexpected raw mappings for G:\mobile\cadastro\lib\root.js
    at invariant (G:\mobile\cadastro\node_modules\react-native\node_modules\fbjs\lib\invariant.js:44:15)
    at getModules.forEach.module (G:/mobile/cadastro/node_modules/react-native/packager/src/Bundler/Bundle.js:222:7)
    at Array.forEach (native)
    at Bundle._getCombinedSourceMaps (G:/mobile/cadastro/node_modules/react-native/packager/src/Bundler/Bundle.js:217:23)
    at Bundle.getSourceMap (G:/mobile/cadastro/node_modules/react-native/packager/src/Bundler/Bundle.js:245:14)
    at Bundle.getSourceMapString (G:/mobile/cadastro/node_modules/react-native/packager/src/Bundler/Bundle.js:251:34)
    at building.then.p (G:/mobile/cadastro/node_modules/react-native/packager/src/Server/index.js:777:31)
    at process._tickCallback (internal/process/next_tick.js:109:7)

Reproduction

  • Enable perf monitor
  • Reload a couple of times

Additional Information

  • React Native version: 0.43.0-rc.2
  • Platform: Android
  • Operating System: Windows 10 x64
@Jakevin
Copy link

Jakevin commented Mar 14, 2017

+1
When I do reload and disable JS Dev Mode at using Remote JS Debug.

Unexpected raw mappings for /Volumes/mx200/ReactNativeProject/accupassnative/js/Globals.js
{"name":"Invariant Violation","framesToPop":1}
Invariant Violation: Unexpected raw mappings for /Volumes/mx200/ReactNativeProject/accupassnative/js/Globals.js
    at invariant (/Volumes/mx200/ReactNativeProject/accupassnative/node_modules/fbjs/lib/invariant.js:44:15)
    at /Volumes/mx200/ReactNativeProject/accupassnative/node_modules/react-native/packager/src/Bundler/Bundle.js:222:7
    at Array.forEach (native)
    at Bundle._getCombinedSourceMaps (/Volumes/mx200/ReactNativeProject/accupassnative/node_modules/react-native/packager/src/Bundler/Bundle.js:217:23)
    at Bundle.getSourceMap (/Volumes/mx200/ReactNativeProject/accupassnative/node_modules/react-native/packager/src/Bundler/Bundle.js:245:14)
    at Bundle.getSourceMapString (/Volumes/mx200/ReactNativeProject/accupassnative/node_modules/react-native/packager/src/Bundler/Bundle.js:251:34)
    at /Volumes/mx200/ReactNativeProject/accupassnative/node_modules/react-native/packager/src/Server/index.js:754:31
    at process._tickCallback (internal/process/next_tick.js:103:7)

@nishiltamboli
Copy link

+1
Same issue. When I enable Remote Debugger and reload - Particularly when there is a reload after some change is made in a file.

@GeoffreyPlitt
Copy link

Getting this constantly now.

@zachrnolan
Copy link

zachrnolan commented Mar 22, 2017

+1
Having the same exact issue every reload. Using 0.42.0

@groke
Copy link

groke commented Mar 24, 2017

edit: I removed each of these plugins one at a time from my installation and the error continues so they don't seem to be the issue

Me too. Maybe a plugin causing it? Do we have anything in common?
"react-native-admob": "^1.2.1",
"react-native-fcm": "^6.1.0",
"react-native-linear-gradient": "^2.0.0",
"react-native-menu": "^0.20.2",
"react-native-splash-screen": "^2.0.0",
"react-native-swipe-gestures": "^1.0.2",
"react-native-timer": "^1.3.1",
"redux-persist": "^4.4.2",

@GeoffreyPlitt
Copy link

We use react-native-linear-gradient and react-native-swipe-gestures

@groke
Copy link

groke commented Mar 25, 2017

I think I found a way around this issue, at least for my setup.
From the development menu on my android I selected Dev Settings and re-enabled JS Dev Mode that resolved this issue for me.

@ophite
Copy link

ophite commented Mar 27, 2017

+1

@itbeihe
Copy link

itbeihe commented Apr 13, 2017

+1.
When I do reload and change JS Dev Mode at using Remote JS Debug.

Additional Information

react-native-cli: 2.0.1
react-native: 0.43.3
Platform: Android avd
Operating System: debian 8

@Wu4D
Copy link

Wu4D commented Apr 14, 2017

+1
Disable dev mode + Start remote js debuging + Reload = crash
Enabling dev mode does solve it

@JosephDev
Copy link

+1
I have the same issue on iOS. any solution for iOS?

"react-native": "0.43.3",
"react": "16.0.0-alpha.6",

@mehulmpt
Copy link

mehulmpt commented Apr 25, 2017

+1
I face the same issue randomly when developing on real device. (Using adb reverse tcp 8081)

Update: disabling remote JS debugging kinda fixes it.

@nimish-gupta
Copy link
Contributor

nimish-gupta commented May 1, 2017

+1
Same issue. with enabling the remote debugging app crashing on every reload with the same above error

@BeckZero
Copy link

BeckZero commented Jun 1, 2017

+1!!
"react": "16.0.0-alpha.6",
"react-native": "0.44.2",

@JosephDev
Copy link

Here is my solution but I don't know why it works.

  1. remove native codes. ios and android folders. !! backup first !!
    rm -rf os && rm -rf android
  2. create a new dummy project.
    react-native init AwesomeProject
  3. copy native codes to current project folders
cp -R AwesomeProject/ios currentProject/
cp -R AwesomeProject/android currentProject/ 
  1. build
  2. modify native codes as you've done on current project for example:
  • icons, version information, and/or push notification etc...

@annelorraineuy
Copy link

I am getting this as well.
So on DEV mode ON, chrome debugging works the first time. Upon reload, the app is just a white screen. So I have to turn off Remote JS Debugging in order to get the app back again. Rinse and repeat cycle. :/

"react-native": "0.44.0"
I am using "react-native-navigation": "^1.1.81" though. Not sure if this has something to do with it.

@Zehio
Copy link

Zehio commented Jun 15, 2017

+1!!!! Extremely annoying.

@ItsNoHax
Copy link

ItsNoHax commented Jun 29, 2017

This still happens, has any facebook dev replied to this?

Literally last couple react-native versions have been so crap :(

@fredbt
Copy link

fredbt commented Jun 30, 2017

This is also happening to me. Really annoying.

@wuyunqiang
Copy link

me too.
android simulator is right. and hardware is bug show me.
reloadimg

@RomanISWG
Copy link

Same issue by me with
react-native-cli: 2.0.1 react-native: 0.47.2

@alzalabany
Copy link

any workaround yet ?

@WolfieZero
Copy link

WolfieZero commented Nov 9, 2017

I've been having this issue, but I can pin-point it to a line.

findContent(block: Block): string {
    const contentBlock = block.descendants[0];

    if (typeof contentBlock.content === 'string') {
        return contentBlock.content; // << Here
    }

    return '';
}

When I change it to return ''; it reloads fine.

JS Dev Mode: off
JS Minify: off
Remote JS Debugging: on
react: 16.0.0-alpha.12
react-native: 0.46.3

@lasuax
Copy link

lasuax commented Nov 21, 2017

Impossible to debug because of this disruptive error.

@stale
Copy link

stale bot commented Jan 20, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. If you think this issue should definitely remain open, please let us know why. Thank you for your contributions.

@stale stale bot added the Stale There has been a lack of activity on this issue and it may be closed soon. label Jan 20, 2018
@stale stale bot closed this as completed Jan 27, 2018
@facebook facebook locked and limited conversation to collaborators May 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Stale There has been a lack of activity on this issue and it may be closed soon.
Projects
None yet
Development

No branches or pull requests