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 }

[a-eid]

Description

trying to run genymotion simulator ..

followed the instructions but getting the following error

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 }

Expected Behavior

for the simulator to run

Observed Behavior

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 }

Environment

• npm ls react-native-scripts:

 [email protected]

• npm ls react-native:

 [email protected]

• npm ls expo:

[email protected]

• node -v:
  8.4.0

• npm -v:
  5.3.0

• yarn --version:
  1.0.1

• watchman version:
  `4.9.0.

Also specify:

1. Operating system: macos sierra
2. Phone/emulator/simulator & version: genymotion

[WilliamAnputra]

+1

[djaffarmr]

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

[anp]

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

[this-miguel]

I'm having the same issue, do you have any pointers?

Just yesterday the emulator was running fine :/

[this-miguel]

this worked for me

source: https://www.bountysource.com/issues/43329081-error-staring-android-emulator
source in github: #112

[brentvatne]

@this-miguel's solution should work!

[AndrewLosikhin]

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

[pinchez254]

I went over to play store in the emulator and viewed expo to see whether i could update it, and I found a message that this version us not supported in your device. Try different emulators..for me i used android 7 emulator instead and That worked for me!

[parappathekappa]

@this-miguel solution fixed one problem, but then I kept getting 'Couldn't adb reverse' error messages and 'Couldn't start project on Android...'. @rednull solution was the only one that actually fixed it. I just wish Genymotion had a wider range of tablets with API 19.

[lualparedes]

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.

[Aziel1234]

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 }

[douglasffilho]

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 }

Conseguiu resolver? estou com o mesmo erro tentando rodar no emulador sem Google Play (API 22 - Lollipop 5.1)

[PiotrSzlagura]

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.

[douglasffilho]

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.

Too bad, I tryed other API versions and got success, but not to API 22. Thanks by answering @PiotrSzlagura

[seb-glanum]

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.

Same issue but I had my emulator already with API 30, so I've just created a new emulator and it's working now !

[learnersaurabh]

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

Thanks @anp , it worked for me

[owivans]

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

[garrettg123]

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.

[boolfalse]

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).

[ICardosoRamos]

GUYS, THIS PROBLEM IS THAT:
IN YOU EAS.JSON FILE, YOU HAVE ALL THE BUILD CATEGORIES, AND YOU CAN CREATE SOME CUSTOM CATEGORY, SO, IF YOU NEED SOME BUILD CATEGORY THAT RUNS WITH THE --DEV-CLIENT OPTION IN THE NPX EXPO START COMMAND, ALL YOU NEED TO GUARANTEE IS THE THE CATEGORY YOU CHOOSE HAS THE "developmentClient: true" FLAG INSIDE OG THE CATEGORY, LIKE:

	"development": {
		"developmentClient": true,
		"distribution": "internal"
	}

SO IF YOU DON'T HAVE THIS THE BUILD WILL NOT HAVE THE COMPATIBILITY TO RUN WITH --DEV-CLIENT OPTION.