Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android Chrome with SKIN env variable causes Chrome to crash on startup #222

Open
mikk150 opened this issue Jan 29, 2020 · 4 comments · May be fixed by #223
Open

Android Chrome with SKIN env variable causes Chrome to crash on startup #222

mikk150 opened this issue Jan 29, 2020 · 4 comments · May be fixed by #223
Labels

Comments

@mikk150
Copy link

mikk150 commented Jan 29, 2020

If I start android docker container with docker run --rm -p 5900 --device /dev/kvm --env ENABLE_VNC=true --env SKIN=1200x1920 selenoid/chrome-mobile:79.0 or run selnoum with {"capabilities": {"skin": "WXGA720"}

Then chrome crashes on startup

I think chrome should be installed right after android starts each time, so we can use SKIN variable

@mikk150
Copy link
Author

mikk150 commented Jan 29, 2020

for other ppl, it would be really awesome to be able to set from capabilities(and from ENV also of cource) an APK file to download and install it to device, so they can use always same image to test their application that has been built from CI/CD

@vania-pooh
Copy link
Member

@mikk150 Appium used in these images allows to specify your app using app capability (pass HTTP URL to APK there).

@mikk150
Copy link
Author

mikk150 commented Jan 30, 2020

@mikk150 Appium used in these images allows to specify your app using app capability (pass HTTP URL to APK there).

That does not change the fact that SKIN variable is not working

@vania-pooh vania-pooh added the bug label Jan 30, 2020
@yevhen-sydorenko-symphony

@vania-pooh Any updates here? Looks like the issue is still reproducible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants