cordova-plugin-inappbrowser: [Tests/CI/Travis] android-7.0 tests are failing

This is the configration that is failing:

  "os": "linux",
  "env": "PLATFORM=android-7.0",
  "jdk": "oraclejdk8",

Last successful build was: https://travis-ci.org/apache/cordova-plugin-inappbrowser/builds/344652192 (Feb 22)

First failing build was: https://travis-ci.org/apache/cordova-plugin-inappbrowser/builds/357149499 (Mar 21)

(end of page #1 of https://github.com/apache/cordova-plugin-inappbrowser/commits/master right now)

Error message on Travis was:

...
..............................................
cordova-paramedic: connecting to app
cordova-paramedic: waiting for test results
cordova-paramedic: Tests failed to complete; ending appium session. The error is:
Error: Seems like device not connected to local server in 300 secs
    at null._onTimeout (/tmp/paramedic/lib/paramedic.js:467:24)
    at Timer.listOnTimeout (timers.js:92:15)
Running Appium tests on Sauce Labs
Couldn't find Appium tests, skipping...
Completed tests at 10:02:21 AM
Getting saucelabs jobs details...
============================================================================================
Job name: travis-plugin-inappbrowser-436.10
Job ID: 11b69418b01a4cc1b09607b000b9e40c
Job URL: https://saucelabs.com/beta/tests/11b69418b01a4cc1b09607b000b9e40c
...

Commit was: https://github.com/apache/cordova-plugin-inappbrowser/commit/65a825a1934ef93d886225c9c56f98fcec50ef38 So nothing concerning Android, so probably more a testing environment thing.

Most commits after that one were failing with the same test failing. Some succeeded without a real reason. Some other more recent commits succeeded because the test was just removed.

More recent test run that is failing, where the video and logs are still available on Saucelabs:

cordova-paramedic: connecting webdriver
...........................
cordova-paramedic: connecting to app
cordova-paramedic: waiting for test results
cordova-paramedic: Tests failed to complete; ending appium session. The error is:
Error: waitForTests: Seems like device not connected to local server in 540 secs
    at null._onTimeout (/tmp/paramedic/lib/paramedic.js:467:24)
    at Timer.listOnTimeout (timers.js:92:15)
Running Appium tests on Sauce Labs
Couldn't find Appium tests, skipping...
Completed tests at 1:25:20 PM
Getting saucelabs jobs details...
============================================================================================
Job name: travis-plugin-inappbrowser-516.10
Job ID: 8a2a6c5d12714125b366852914355361
Job URL: https://saucelabs.com/beta/tests/8a2a6c5d12714125b366852914355361
Video: https://assets.saucelabs.com/jobs/8a2a6c5d12714125b366852914355361/video.flv
Appium logs: https://assets.saucelabs.com/jobs/8a2a6c5d12714125b366852914355361/selenium-server.log
Logcat logs: https://saucelabs.com/jobs/8a2a6c5d12714125b366852914355361/logcat.log
============================================================================================

The screenshot indicates that the tests run and and finish just fine.

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 16 (16 by maintainers)

Commits related to this issue

Fix inappbrowser on Android 7 (#50) Android 7.0 tests were failing for `cordova-plugin-inappbrowser`: https://github.com/apache/cordova-plugin-inappbrowser/issues/307 Long research showed that this h... — committed to apache/cordova-paramedic by janpio 6 years ago
feat!: remove deprecated whitelist usage (#307) — committed to saschal-j5int/cordova-plugin-inappbrowser by erisu 3 years ago
feat!: remove deprecated whitelist usage (#307) (cherry picked from commit 2cdb0403a81821e144998c8d9a00d338d6ece3ee) — committed to saschal-j5int/cordova-plugin-inappbrowser by erisu 3 years ago

Most upvoted comments

Found the actual workaround you probably meant - we did not bust the permissions for the splashscreen plugin because it was hanging on Android 7. Expanded that to inappbrowser, and voila, it works 🥇

janpio on Oct 2, 2018

The command looking for “Allow” button should fail shortly, as it does in dialogs, but for some reason it times out after a minute.

alsorokin on Oct 2, 2018

Noticed one more thing in our failing test run on Saucelabs:

For the successful dialogs plugin this is just:

Does this maybe indicate a failure/timeout in that step that stops execution?

janpio on Oct 1, 2018