Shell command failing inside of tasker to launch app - works on ADB Shell

[Cheney Joseph]

This command works from adb shell but gives error 253 from within tasker:

monkey -p nl.vrowl.vrcinema -c android.intent.category.INFO 1

This is for a third party application I have side loaded onto oculus go. I'm open to any other solution for launching the app, I have tried to use autolauncher but had difficulty unlocking from oculus go.

This is from the manifest.xml:

package="nl.vrowl.vrcinema"

<activity
    android:theme="@ref/0x0103000a"
    android:name="com.unity3d.player.UnityPlayerActivity"
    android:excludeFromRecents="true"
    android:launchMode="2"
    android:screenOrientation="0"
    android:configChanges="0x40003fff"
    android:hardwareAccelerated="false">

    <intent-filter>

        <action
            android:name="android.intent.action.MAIN" />

        <category
            android:name="android.intent.category.INFO" />
    </intent-filter>
</activity>

[Cheney Joseph]

Running shell:

"am start -n nl.vrowl.vrcinema/com.unity3d.player.UnityPlayerActivity" works from adb but when I do with shell in tasker I get an Error 1

[Marta Hintz]

try running it as an intent? just spit balling here, as I don't do intents very well.  

System>Send Intent

Action:android.intent.action.MAIN
Cat:Default Mime Type: Data: Extra: Extra: Package:nl.vrowl.vrcinema
Class:com.unity3d.player.UnityPlayerActivity
Target:Activity

Marta

[Cheney Joseph]

Worked perfectly, thanks Marta!