I’m trying to figure out how to start a Unity app from ADB, ideally so I can pass custom intent parameters for automated device testing. So far, I’m stuck just on starting a Unity app via ADB. I am well aware that this is possible, and it MUST be possible because apps like Sidequest are able to accomplish this on the exact same app, on the exact same phone, that I can’t make this work on.
I’m currently using an unmodified Unity Android Manifest, which I can confirm both launches normally from a Pixel 4a and can launch from Sidequest. I’ve tried the following commands that many people claim should work
adb shell am start -n com.Futurus.AIntent/com.unity3d.player.UnityPlayerActivity
adb shell am start -n "com.Futurus.AIntent/com.unity3d.player.UnityPlayerActivity"
adb -d shell am start -f 0x10000000 -n com.Futurus.AIntent/com.unity3d.player.UnityPlayerActivity
adb shell am start -n com.Futurus.AIntent/unityplayer.UnityActivity -a android.intent.action.MAIN
Every single command I’ve tried claims that the activity class does not exist, despite the fact that it matches what’s in the compiled manifest that I looked at in Android Studio. If I try to resolve-activity I get No activity found which seems like it cannot possibly be true because the app runs when opened via tap or Sidequest.
I’m a complete loss, below I’ve copy-pasted the analyzed manifest from Android Studio. As best as I can tell, I’m performing the start command correctly but for the life of me it will not open. Any help is greatly appreciated
I’m using Unity 2021.3.4f1 on Win11, ADB through Powershell if any of that matters.