Use Expo Metro Bundler instead of react-native start - react-native

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.

Related

React Native Expo app shows white screen on TestFlight

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.

Expo React Native building apk

I have been trying to build my apk today but I always face this problem. After completing the build, i download it to my phone and i cannot open it. However, this was not the case 2-3 days ago. I had no difficulties or errors in Run expo doctor. I was able to download the apk to my device and test my app.
I am not really sure what to do and any help would be appreciated.
This is what I got after running npx expo doctor:
I managed to solve my problem. I used Android Studio's logcat feature and when I ran the app on the emulator I found the issue - it was related to admob. At this point, I dont need admob, so I deleted its folder from my project and everything was fine after this.
Running expo doctor usually ends up in flagging what dependency needs to be upgraded if the jump to automatically update it goes into the majors like in your case from 4 to 5.
Maybe try upgrading #expo/config-plugins by using expo upgrade or commands from your preferred package manager.
If that’s impossible due to other packages depending on the specific version, maybe consider adding overrides in your package.json. Here is a helpful article about that.
In my experience this may not be the only reason for the crash of the app. Try running the app consecutively about 3 or 4 times even if it crashes and I believe Android will prompt you to submit a bug report and maybe show you the call stack it failed at.
Let us know how it goes.

How to troubleshoot an app after its installed

I just built and installed an android app using expo but upon launching it, the app crashes after the splash screen when it was working just fine when I using expo. I now wonder how am I to fix it when I can't even see where the problem lies.
Is there a way to find out what the problem is ? like some kind of debug=true option or anything else to figure out and fix the issue ?
You can use a 3rd party plugin that does just that like firebase or instabug, these are the 2 that I've used but I'm sure you can find a lot more.

Mobile app using react-native-cli or expo-cli?

I'm going to make my first app in React Native. I have windows, but I want to make this app cross-platform. I want to use camera for making short videos (like tiktok) on this app.
Can I make this app using windows? and what I need to use? expo or react-native-cli?
Thank you!
I think that is a question about an opinion. To use the camera you'll need native modules, idk if expo allows that, some time ago didnt allow but idk what is status of expo now. Beyond that, IMHO you could begin with rn cli directly because this is the most used in "the real life" and no has a big difference with expo.

Application is freeze when "this.props.navigation.navigate"

I am using expo 34 and I am tried with 32,33 and 31.
It works when I run it with Expo client on Ios Simulator but
In the "this.props.navigation.navigate" commands, the program freezes and the cpu rises.
I'm not getting a mistake either.
I have the same problem with Android tests.
Expo client version 2.12.1
I tried it separately on Windows and Apple operating systems to solve this problem, but the problem still persisted.
Not: In the meantime, the application I am talking about is now online.
I mean, he was definitely working before, but I can't even test him now.
You need to install that in your project.
npm install react-navigation --save
Also you need to pass in the view name. For example:
this.props.navigation.navigate('ViewName');