Hi,
I want to start that type of intent:
adb shell am start -a android.intent.action.VIEW -d “app://screen1”
It actually works (and opens a deeplink) in the terminal with regular ADB - but why is that actually not working when I set all needed(?) capabilities for Appium?
app = new File(appDir, "app.apk");
capabilities.setCapability("app", app.getAbsolutePath());
capabilities.setCapability("platformName", "Android");
capabilities.setCapability("deviceName","Android");
//capabilities.setCapability("platformVersion", "5.0.4");
//capabilities.setCapability("appPackage", "com.test.qa");
capabilities.setCapability("appActivity", "");
capabilities.setCapability("intentAction", "android.intent.action.VIEW");
capabilities.setCapability("optionalIntentArguments","-d \"app://screen1\" com.test.qa");
capabilities.setCapability("intentCategory","");
It simply ignores that intent and starts the app/tests regularly. Any ideas ? Do you support both explicit and implicit intents?
The terminal tells me Appium is using:
adb -s SH51EWM01926 shell am start -S -a android.intent.action.VIEW -f 0x10200000 -n com.test.qa/com.test.qa.navigation.home.HomeActivity -d “app://screen1” com.test.qa
So basically that:
“-n com.test.qa/com.test.qa.navigation.home.HomeActivity”
more or less is the problem ?
How can I get rid of that then ? Usually I would set an empty capability for overwriting the defaults, but for that there is no capability…
Thanks a lot in advance! Best, Daniel