Android app doesn't start up, times out looking for androidProcess

[GoogleCodeExporter]

Issue Description:
'unknown error: Failed to get PID for the following process: :auth
 (Driver info: chromedriver=2.6.232908,platform=Mac OS X 10.8.5 x86_64)' 

Steps to reproduce (if relevant, you MUST provide a simplified html page or
link to public site):
get the Salesforce apk: 
https://play.google.com/store/apps/details?id=com.salesforce.chatter
start an Android19 emulator on a mac (can currently only do ARM and I currently 
chose 'Nexus S' device ~ snapshots don't work)
install the apk
with eula.xml (attached) run command: 
adb push eula.xml /data/data/com.salesforce.chatter/shared_prefs/eula.xml
(this is to auto-dismiss the eula and have the app start directly on the 
'login' webview)
start chromedriver
run python snippet:

from selenium import webdriver as w
caps = {'androidPackage':'com.salesforce.chatter', 'androidActivity': 
'com.salesforce.chatter.Chatter', 'androidProcess': ':auth'}
d = w.Remote('http://localhost:9515', {'chromeOptions':caps})

(chromedriver log attached).

If you manually start Salesforce1 again and wait for it to load you will see 
the process  com.salesforce.chatter:auth  when running `adb shell ps`

Is there anyway to set the timeout differently?

Original issue reported on code.google.com by luke.semerau on 19 Nov 2013 at 5:43

• Merged into: #634

Attachments:

• chromedriver.log
• eula.xml

[GoogleCodeExporter]

Did you try supplying the full "com.salesforce.chatter:auth" as the 
androidProcess? We expect an exact match between the process name you see in ps 
and what you supply in androidProcess.

Original comment by craigdh@chromium.org on 19 Nov 2013 at 11:40

[GoogleCodeExporter]

just tried it with the exact process name that I can see when I manually start 
the app:

"com.salesforce.chatter:auth"  and it still times out and fails to start (log 
attached for that)

After manually starting the app (after pushing the eula.xml)  and waiting for 
the app to load I can see the process listed (shell_ps.txt attached).

Also, I'm realizing my methodology won't work with pushing the eula.xml file, 
since you guys are issuing the command `adb shell pm clear 
com.salesforce.chatter`  which will delete the eula.xml file.

So, this is likely a duplicate of #634  and once that is in place then I'll be 
able to use chromedriver on my app.

Original comment by luke.semerau on 20 Nov 2013 at 6:44

Attachments:

• chromedriver.log
• shell_ps.txt

[GoogleCodeExporter]

Original comment by craigdh@chromium.org on 20 Nov 2013 at 7:29

• Changed state: Duplicate