allow wildcards in appWaitActivity

Issue

I have a trouble launching my android app on Appium 1.6.0 or later. [ADB] Error: Activity used to start app doesn't exist or cannot be launched! Make sure it exists and is a launchable activity I understand that appWaitActivity is required and the problem may be fixed by setting a correct activity, however, I think it is very difficult to set all activities to appWaitActivity for a number of reasons:

• My app includes an Ad SDK which contains multiple activities.
• I tried driver.currentActivity(); but it returns various values. It may be a timing issue, though.
• This Ad SDK is developed by an outside developer so there is a possibility that the activity name of the SDK may be changed.

It would be great if Appium provide an option to skip the activity check or a setting to specify appWaitActivity like 'com.mydomain.*, com.sdkdomain.*'.

Environment

• appium 1.6.0 or later
• Desktop OS/version used to run Appium:Mac OS X El Capitan
• Node.js version (unless using Appium.app|exe): v6.9.2
• Mobile platform/version under test: android
• Real device or emulator/simulator: both

[imurchie]

This seems like a good feature to have, to be able to send in a wildcard. Adding it to our work.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.