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 latest is running version 6.0 #7

Open
jzombie opened this issue Apr 20, 2021 · 4 comments
Open

Android latest is running version 6.0 #7

jzombie opened this issue Apr 20, 2021 · 4 comments
Labels
documentation Improvements or additions to documentation

Comments

@jzombie
Copy link
Contributor

jzombie commented Apr 20, 2021

The .airtap.yml of the following configuration runs Android 6.0 remotely, which is a rather old version of Android.

All other tests are passing; running on latest versions I think.

sauce_connect: true
loopback: airtap.local
providers:

  • airtap-sauce
    browsers:
  • name: firefox
    version: latest
  • name: chrome
    version: latest
  • name: safari
    version: latest
  • name: iphone
    version: latest
  • name: microsoftedge
    version: latest
  • name: android
    version: latest

android-version

Edit: Sometimes when the Android 6 client fails, you can see the error message (other times it times out). However, I'm not looking to test Android 6.0.

client error (Sauce Labs Android Browser on Android 6.0 on Android GoogleAPI Emulator): { message: 'Uncaught SyntaxError: Unexpected token {',
source: 'http://airtap.local:45919/airtap/test.js',
lineno: 9,
colno: 16,
error:
{ name: 'SyntaxError',
stack: 'SyntaxError: Unexpected token {' } }

Edit: Confirmed that issue is not reproducible when downgrading airtap to version 3.0.0 and running Sauce Connect Proxy 4.6.5.

@vweevers vweevers added the bug Something isn't working label Apr 21, 2021
@jzombie
Copy link
Contributor Author

jzombie commented Apr 22, 2021

This was resolved by using the following configuration (borrowed from https://github.com/feross/simple-peer):

(android was changed to and_chr)

sauce_connect: true
browsers:

  • name: firefox
    version: latest
  • name: chrome
    version: latest
  • name: safari
    version: latest
  • name: edge
    version: latest
  • name: and_chr
    version: latest
  • name: ios_saf
    version: latest
    providers:
  • airtap-sauce
    presets:
    local:
    providers: airtap-manual
    browsers:
    • name: manual

@jzombie jzombie closed this as completed Apr 22, 2021
@jzombie jzombie reopened this Apr 22, 2021
@jzombie
Copy link
Contributor Author

jzombie commented Apr 22, 2021

Leaving issue open. Maybe the README should reflect the various browser options.

@vweevers
Copy link
Member

Ah, yes. I didn't read the issue description carefully enough. It's not a bug, but a breaking change that's documented in airtap's upgrade guide: https://github.com/airtap/airtap/blob/master/UPGRADING.md#changes-to-matching-of-browsers.

You're right that it deserves to be documented in a README too.

@vweevers vweevers added documentation Improvements or additions to documentation and removed bug Something isn't working labels Apr 22, 2021
@jzombie
Copy link
Contributor Author

jzombie commented Apr 22, 2021

Thanks! New to this, but really enjoying testing w/ airtap-sauce.

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

No branches or pull requests

2 participants