I've been working on a react-native app managed mode built on expo, I was working from a mac at first which worked perfectly fine using the IOS simulator it didn't work on android emulator on mac, here i switched to a windows computer and the issue still exists on the android emulator, executing the command "expo start" the app crashes after the splash screen before the logo appears, I tested the app on a real device on the debug mode and it worked! also after deploying the apk file the app works with no issues, the only problem is it's not working on android simulator using expo client, things i tried to solve the issue including trying to reinstall android studio and install the latest version, tried updating expo sdk to latest version also tried playing around with the app.js from where the app launches the first time but still crashes at the same point, it's not showing any errors or warning it just crashes, any suggestion or something i could try would be very helpful thanks.
I am also having a similar issue : after upgrading to the latest release (SDK 41) the android simulator hangs often and the app crash without any errors. But works some time .
Related
I recently got a new Macbook Pro M1 Max and am trying to set up my expo react native environment (VScode). The app bundles and everything is working as it should, but when I try to open the Expo Go app in the simulator, the app crashes (shown below).
Everything works fine when I open the Expo app from my iPhone, so I think it is just a simulator issue. Does anyone know what is causing the issue?
I had been working with react native for few days and I used to run my app in my own android phone through LAN. But recently the expo client app is not supporting. When I open it it shows all the recent project as well as working project. when I click on working once it shows all the normal stuffs like Dowloading javascript bundles and in metro bundler also it shows Building JavaScript bundle: finished in 5380ms. No problem there. But when it finishes a pop up came and show Expo stopped
like this :
I cleared the cashe and atlast reinstalled expo client app in android device and expo-cli in my system. Still the problem persisting. How to resolve it... :(
I want to run my React Native app in the iOS emulator. Here is what I done so far:
I installed XCode, along with its command line tools, and can bring up the emulator without issue.
I created an empty React Native app using the Expo CLI, per the instructions here. https://facebook.github.io/react-native/docs/getting-started. I am running on Node v10.0.0 on a Mac.
Afterwards I install all the necessary dependencies.
I then run "sudo npm run ios". This fires up the Metro Bundler as well as the iOS simulator. The Simulator loads up after about 5 minutes of waiting, but my app does not start up.
What am I missing here?
I should note that I prefer to stick with Expo, so I'd prefer not to have to eject.
Yesterday I release my app but I have problem on Android. When the app starts it shows the splash screen and crashes immediately (before actually showing any part of the app) with the message “Unfortunately App has stopped”. I build the release with the following
./gradlew assembleRelease
and everything was successful. I tested the app with
react-native run-android —variant=release
on my device and there wasn’t any problem. But in production it’s not working… What can be the problem?
Actually It turns out that the problem was with managing my production releases in the Google Play Store. My first release was build from the Android Studio and not from the console with ./gradlew assembleRelease (I thought that this is just another way and did it in the standard way of building release for android app). Because of that all the JavaScript needed to run my app wasn't bundled in the APK and it was showing only the splash screen. After fixing that and releasing the new APK with the bundled JavaScript and fixing the right release on the Google Play Console everything is fine now.
The documentation is very good and clear: Releasing on Android documentation
I have a problem when running react-native run-ios on my project.
The IOS emulator launch well.
Then the application start (react-native white splash screen) and immediately after that, it return me to the Iphone home screen.
If I Cmd-Shift-H (with pressing H two times) I saw the app in the background (still with the react-native white splash screen).
When I click on it, it return me to the home screen again.
If I launch the Xcode project and run the app, it work fine and I can navigate in my application.
I've had some troubles with my app before, the IOS version was 'abandoned' and I've installed a lot of modules and changed the name of the project in the mean time, before trying to make it work on IOS.
Then I've decided to create a new project with react-native init myNewProject (because I couldn't figured out how to fix the IOS, something with a workspace not configured) and copy paste my old src and index.ios/android.js inside.
So now Android is still working and IOS is only working if I launch the app from Xcode.
I've tried to reset the emulator but it don't change anything.
I don't have any logs about app crash or something.
The Android app version is working fine.
Any idea ?
Logs
I've put the device logs after running react-native run-ios on a gist
https://gist.github.com/ansmonjol/f6fa1e71a20b944bf67429c57d081165
Additional Information
React Native version: 0.35
Platform: IOS
Operating System: macOS El capitan
Xcode: Version 8.0
I ran into this problem, and solve it:
In my case i install third-party native component in my project and link it using command react-native link <component-name>. Than i have a problem about you wrote:
Running project by Xcode - works fine. Bundling start, after loading dependency graph.
But runnig project by react-native run-ios app hide immediately and bundling not started after loading dependency graph. And not any errors happened.
I tried reinstall all, clean npm cache, react-native upgrade, delete build folder, delete derived data... nothing helped.
I found one way that helped me:
I remove that problem library not manyally from Xcode, but from terminal using command react-native unlink <component-name>. Its way to resolve this problem for me, maybe for you too.
Sorry for my english.