Version 0.44.0 应用一启动闪退 Open the application crash #13857

Activity

1. dobrienlzd commented on May 9, 2017

   

   dobrienlzd

   on May 9, 2017

   Last edited by dobrienlzd

   More actions

   Two possibilities:

   1. you need to restart the packager. If you are in development
      shutting down the emulator.
      close out terminals
      npm start // or react-native run-ios or react-native run-android depending on platform.
      also check no excess stuff running on debugger port.
      Cmd M open debugger menu on app and switch off and back on the debug js as needed.
      even reboot machine if needed.
      It might be your packager is not running correctly and you need to restart. Not sure.

   2. wrong version of react or react-native. This is easier to check for. Use commands shown at the bottom to check what's really installed vs. what's in your package.json

   Look inside package.json for versions of react and react-native.
   For example in mine this is what I see:

   "react": "^16.0.0-alpha.6",
   "react-native": "^0.43.4",

   most people believe that when you do:

   npm install

   You are guaranteed that these versions are the ones installed. But that is not always the case. Sometimes npm just grabs whatever it can find from internet.

   You may need to do:

   npm install --save react@16.0.0-alpha.6 // check in package.json for correct values.
   npm install --save react-native@0.43.4 // or 0.44.0 in perhaps in your case.

   Dont assume that 'npm install' puts exactly what you need into node_modules. You might have to occasionally clean out node_modules

   rm -rf node_modules
   npm install --save react@16.0.0-alpha.6
   npm install --save react-native@0.43.4 // in your case 0.44.0 but check what's in package.json
   npm install

   Let us know if that fixes it. You might try downgrading to 0.43.4 if that's an option or you as well. (Also note in SOME cases you need to do 'react-native link' after the installs but you should see some messages about this after npm install if that's the case.

   To see what's really installed:
   npm list
   npm list | grep react // if you can access grep.
   npm list | grep react-native

   LET US KNOW IF THIS WORKS! If not tell us more! Like if you just created the app? Or are you development when this happens etc.
2. hramos commented on Jul 20, 2017

   

   hramos

   on Jul 20, 2017

   Last edited by hramos

   Contributor

   More actions

   Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

   If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

   • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
   • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
   • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

   If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.
3. hramos

   added

   Icebox

   on Jul 20, 2017
4. hramos

   closed this as completedon Jul 20, 2017
5. react

   locked as resolved and limited conversation to collaborators on Jul 20, 2018
6. react-native-bot

   added

   Resolution: LockedThis issue was locked by the bot.This issue was locked by the bot.

   on Jul 20, 2018