when i install the ios app , app screen is not responding. After refreshing and clear the background process the app is working fine.
How to fix the issue?
Yeah, you'll need to include some code or more details as to what is happening. It sounds like you have some code that is failing on initialization but is not depended upon for the rest of the app. If you run react-native log-ios from the command line in your repo, do you get any interesting messages that might contribute to the unresponsiveness?
Related
I have been building an app in React Native with Expo for the last few months.
I just got accepted as a Apple Developer so now I am trying to publish my app to TestFlight.
Everything seemed to go perfect, the building process passed and I uploaded my app through the Transporter app. Now I have my app installed on my phone but every time I open the app it shows a very short Splash image and then goes to a white screen forever. I've searched every possible solution but can't seem to find anything and I am running out of options.
I checken my app.config.js and my eas.json file and it all seems valid to me. So please, if someone experienced this and knows how to solve this, it would be very helpful!
I was expecting to see my app just like I saw it before, while testing it in the Xcode simulator. I have tried changing my config files but it all seems correct to me.
I am developing a ReactNative app for iOS using Expo.
The app worked correctly on a real iPhone with just basic components (View, Text, Button & Styling).
However, I added Stack Navigation last night. The app had no issues on the simulator so I built through 'eas build' (also no problems). I submitted it to TestFlight for internal testing. But, when I click to open the app, it crashes immediately. As it is an actual app, it gives no info about the cause.
I am very stumped, so any help would be great. Thanks!
Solved this months ago but forgot to post the solution.
In case anyone is having a similair issue, the problem was really small.
I was using navigation components such as'createStackNavigator' instead of their native counterparts e.g. 'createNativeStackNavigator'. Made the swap and the app is now working properly.
currently I'm migrating my react native app to expo bare workflow. Everything it's been fine so far, except for the following.
This may seem like a noob mistake, but I'm unable to use the Metro Bundler from Expo when I run my app from Xcode. Before, I could run from Xcode and the simulator would appear in the Metro Bundler with all it's logs, that was very useful.
I've been searching this for a couple days and the closest thing I've found to what I want, is using expo build:ios. The problem, it pops up a warning saying that if I'm not sure what I'm doing it's best to leave it as it is. It's a big application so I'm worried it might lead to errors, therefore I didn't do it.
If anyone knows for sure if this command is what I'm looking for, or has a better suggestion, it would be much appreciated. Thank you.
[EDIT]
To be more specific, I don't mean using the Expo Go app. I mean a standalone app (I'm not sure if this is the correct term for it). Thank you!!
expo build:ios is used for building an app bundle for your application. This is used when you want to publish your application on the store and that is why it asks for credentials of developer account on the iOS.
If you just want to run your app and check then you should use expo start. This will start the Metro Bundler for you and then you can run your application on your device scanning the QR code that would appear there.
Few days ago I noticed watchman stopped working.
Using a real android device with shake gesture I cannot Reload the app (a reload doesn't take the changes to the code). Live reload and hot reloading don't work either.
The only way I have to get the app take the changes is to kill the packager and relaunch it (often neither this method makes the app takes changes!).
There is a way I can solve? This issue It's pretty frustrating.
I'll answer to myself. After further research, this issue looks to be caused by this option in app.json
"packagerOpts": {
"nonPersistent": "--nonPersistent"
}
which I've added to be able to produce a release build using Expo (otherwise I get error "socket hang up").
It would be nice if some Expo developer would post some infos about this issue and what that option in app.json really does (the docs says nothing).
I am developing react native application via expo. Earlier everything worked well, but after I decided to translate my app into redux with one monster commit it began crash on iOS , but on Android well. What can be reason of such behavior? In debugger I put a lot of breakpoints, but I couldn't find where is that crashes. If I install osx on virtualbox with xcode and read logs will it help?
In my case there was problem with AsyncStorage. I tried to save null into AS. On android it won't cause any error, but not on ios