create-react-native-app: Error running adb: Error running app. Error: Activity not started, unable to resolve Intent { act=android.intent.action.VIEW dat=exp://192.168.0.100:19000 flg=0x10000000 }

this worked for me source: https://www.bountysource.com/issues/43329081-error-staring-android-emulator source in github: https://github.com/react-community/create-react-native-app/issues/112

make sure you are using minimal API 19 on your emulator, its work on me somehow.

In my case it was solved by running any device with API 30. It is worth mentioning that it was with the M1 chip.

I’m having the same issue, do you have any pointers? Just yesterday the emulator was running fine 😕

In case if anyone needs it։

Specifically in my case I’ve found that after running “expo start --dev-client” I had installed expo-dev-client. So I just uninstalled that package, also for just in case removed node_modules and reinstalled npm packages again

npm uninstall expo-dev-client
rm -r node_modules
npm install

And after that it worked well as before. My android physical device worked with v12, Expo v49, emulator was Pixel_7_API_34

I’m new to RN so don’t have much knowledge, but clearing .apk caches didn’t help me. Actually I’ve had my app running well until working with EAS builds (for the Mapbox integration).

I bumped into this exact issue when trying to run my Expo (42) app on android emulator (I was trying to use API 31 at first). Clearing ~/.expo/android-apk-cache did not work.

My issue was resolved when I decided to switch to an emulator with API 30.

O meu erro é recente tem como me ajudar??

Couldn’t start project on Android: Error running adb: Error running app. Error: Activity not started, unable to resolve Intent { act=android.intent.action.VIEW dat=exp://192.168.44.236:19000 flg=0x10000000 }

This is happening to me with the newest Pixel 6 on API 33 and I’ve also tried on Pixel 4 API 30, Expo v44.

My two cents for people that want to understand what’s going on:

When you run npm run android, Expo gets installed on the emulator automatically, and since Expo requires Android 4.4+ (API 19), @rednull solution may do the trick (my case 🙌).

On the other hand, if you’re using Genymotion and it throws this error when you try to use an emulator that has Android 4.4+:

you may still be able to use it by reducing the number of cores in the device settings.

@rednull solution helped. Don’t toss that out.

Can you try some of the steps that the Expo docs recommend at https://docs.expo.io/versions/latest/guides/genymotion.html ?