Adding the discussion thread on this issue with Android support - 

From: "developer-support@google.com" <developer-support@google.com>
Date: Wednesday, June 21, 2017 at 6:02 AM
To: Nidhi Khanna <nkhanna@adobe.com>
Cc: Ankit Gupta <glo67316@adobe.com>, Reetika Ghai <rghai@adobe.com>, Shilpi Aggarwal <shilpi@adobe.com>
Subject: RE: [1-8121000017236] Upgraded Android System WebView failing Espresso tests

 

Hi Nidhi,
 
The WebView was disabled since I was on Chrome version 58.0.3029.83.
 
Starting with Chrome version 51 on Android 7.0 and above, the Chrome APK will render Android System WebViews. You cannot enable/disable it manually.
 
I have attached a sample project wherein I am able to load the WebView and enter the text into the input elements by loading the WebView via static way, or by loading the web URL: "Google.com". In either case the test will pass.
 
I have already checked this issue with WebView team, and they confirmed that it's not an WebView issue. I am not sure on why the test is failing with your extended URL : https://secure.echosign.com/public/login. Only Chrome team will be able to answer this question as that's not my area of expertise.
 
You will have to file an issue with the Chrome team on the external tracker for Chromium issues as they might ask you more information on the reported issue. If you have any other questions, please do let me know.
 
 
Regards,
Rohan
Android Developer Support



 

On 06/19/17 05:30:57 nkhanna@adobe.com wrote:

Hi Rohan,

 

Thanks for the information. We are still having issue with our Espresso test.

 

We are using extended URL of https://secure.echosign.com/public/login for oAuth login. You can refer our app on Playstore - https://play.google.com/store/apps/details?id=com.adobe.echosign&hl=en .

 

Also, in the issue you mentioned where Webview is 53 and the Chrome version is 58.0.3029.83., can you please confirm if the Webview is disabled on device?

 

In our case, issue is reproducible when:

·         Android System WebView is enabled and upgraded to 58.0.3029.83

·         Android System WebView is disabled and Google Chrome browser is enabled with version 58.0.3029.83.

 

At a time one of them is in enabled state. We don’t know why the version of Chrome is affecting this.

 

We also tried to have Android System WebView on version 58.0.3029.83 in disabled state with Chrome on 55.x version. But as soon as we enable Google Chrome, Android System WebView gets downgraded to version of Chrome. Hence we are not able to test this scenario.

 

Thanks,

Nidhi

 

 

 

 

 

 

 

From: "developer-support@google.com" <developer-support@google.com>
Date: Friday, 16 June 2017 at 11:58 PM
To: Shilpi Aggarwal <shilpi@adobe.com>
Cc: Ankit Gupta <glo67316@adobe.com>, Nidhi Khanna <nkhanna@adobe.com>, Reetika Ghai <rghai@adobe.com>
Subject: RE: [1-8121000017236] Upgraded Android System WebView failing Espresso tests

 

Hi Shilpi,
 
Thanks for the patience, and I apologize for the delay.
 
It’s been awhile since the last exchange, please let me know if you are still having issues with the espresso test.
 
I researched on this issue and what I found out is:
1.      If we are loading the WebView using static way(say via Asset folder), then the issue is not reproducible.
2.      I also tried to reproduce this issue by loading the web URL-"Google.com" and can confirm that I was able to enter the text into the input elements.
3.      The test fails only with the URL-”https://secure.echosign.com/public/login”. Please let me know if this is the correct URL.
 
Also, my observations were slightly different while testing this issue. We can reproduce the issue even if the Webview is 53 and the Chrome version is 58.0.3029.83. I also see that that the WebView is able to load and locate the ID. I also checked this with the WebView team and they have confirmed that this is not an WebView issue.
 
I suspect that Chrome might have added an additional check which is failing this test. If this is the case, then I will seek out an request to the Chrome's team. Could you please confirm if the URL-”https://secure.echosign.com/public/login” is correct and I will investigate this issue further. If you have any other questions, please do let me know.
 
 
Regards,
Rohan
Android Developer Support
 

 

On 05/14/17 23:34:06 shilpi@adobe.com wrote:

Hi Tarana,

 

Is there an ETA by when the issue would be fixed? Which update of webview can we expect to have this fix?

 

Thanks,

-Shilpi

 

From: "developer-support@google.com" <developer-support@google.com>
Date: Saturday, 13 May 2017 at 7:20 AM
To: Ankit Gupta <glo67316@adobe.com>
Cc: Nidhi Khanna <nkhanna@adobe.com>, Shilpi Aggarwal <shilpi@adobe.com>
Subject: RE: [1-8121000017236] Upgraded Android System WebView failing Espresso tests

 

Hello Ankit,
 
I was able to reproduce the issue, and I confirm that the crash is happening on the latest WebView versions only, as you reported.
 
I have created an internal bug for our engineering team to have a look, and will provide an update to you as soon as I get any details.
 
Thank you for reporting this issue.
 
Have an awesome weekend!

Adding the discussion thread on this issue with Android support -

From: "developer-support@google.com" <developer-support@google.com>
Date: Friday, June 23, 2017 at 2:10 AM
To: Ankit Gupta <glo67316@adobe.com>
Cc: Nidhi Khanna <nkhanna@adobe.com>, Reetika Ghai <rghai@adobe.com>, Shilpi Aggarwal <shilpi@adobe.com>
Subject: RE: [1-8121000017236] Upgraded Android System WebView failing Espresso tests



Hi
Ankit,
 
You should be able to report a problem on Chrome
issue
 tracker with any email ID. I have filed a bug on the external Chome tracker(736044).
 Please star this issue to receive updates on this issue. 
 
Unfortunately, I am not allowed to  attach this mail
 chain on the external tracker. Once I log in the issue
 
Regards,
Rohan
Android Developer Support



On 06/21/17 04:27:55 glo67316@adobe.com wrote:
HI Rohan,

 

On accessing the external tracker url, the login page asks for mail-id with ‘@google.com’ domain. I tried with some of gmail-ids but that do not work. We do not have any mail-id with ‘@google.com’ domain.

 

Could you please log this issue with Chrome team and update us? Also, attach this mail chain thread to the ticket.

 

-Ankit

 

From: "developer-support@google.com" <developer-support@google.com>
Date: Wednesday, June 21, 2017 at 6:02 AM
To: Nidhi Khanna <nkhanna@adobe.com>
Cc: Ankit Gupta <glo67316@adobe.com>, Reetika Ghai <rghai@adobe.com>, Shilpi Aggarwal <shilpi@adobe.com>
Subject: RE: [1-8121000017236] Upgraded Android System WebView failing Espresso tests

 

Hi Nidhi,
 
The WebView was disabled since I was on Chrome version 58.0.3029.83.
 
Starting with Chrome version 51 on Android 7.0 and above, the Chrome APK will render Android System WebViews. You cannot enable/disable it manually.
 
I have attached a sample project wherein I am able to load the WebView and enter the text into the input elements by loading the WebView via static way, or by loading the web URL: "Google.com". In either case the test will pass.
 
I have already checked this issue with WebView team, and they confirmed that it's not an WebView issue. I am not sure on why the test is failing with your extended URL : https://secure.echosign.com/public/login. Only Chrome team will be able to answer this question as that's not my area of expertise.
 
You will have to file an issue with the Chrome team on the external tracker for Chromium issues as they might ask you more information on the reported issue. If you have any other questions, please do let me know.
 
 
Regards,
Rohan
Android Developer Support



 

On 06/19/17 05:30:57 nkhanna@adobe.com wrote:

Hi Rohan,

 

Thanks for the information. We are still having issue with our Espresso test.

 

We are using extended URL of https://secure.echosign.com/public/login for oAuth login. You can refer our app on Playstore - https://play.google.com/store/apps/details?id=com.adobe.echosign&hl=en .

 

Also, in the issue you mentioned where Webview is 53 and the Chrome version is 58.0.3029.83., can you please confirm if the Webview is disabled on device?

 

In our case, issue is reproducible when:

·         Android System WebView is enabled and upgraded to 58.0.3029.83

·         Android System WebView is disabled and Google Chrome browser is enabled with version 58.0.3029.83.

 

At a time one of them is in enabled state. We don’t know why the version of Chrome is affecting this.

 

We also tried to have Android System WebView on version 58.0.3029.83 in disabled state with Chrome on 55.x version. But as soon as we enable Google Chrome, Android System WebView gets downgraded to version of Chrome. Hence we are not able to test this scenario.

 

Thanks,

Nidhi

 

 

 

 

 

 

 

From: "developer-support@google.com" <developer-support@google.com>
Date: Friday, 16 June 2017 at 11:58 PM
To: Shilpi Aggarwal <shilpi@adobe.com>
Cc: Ankit Gupta <glo67316@adobe.com>, Nidhi Khanna <nkhanna@adobe.com>, Reetika Ghai <rghai@adobe.com>
Subject: RE: [1-8121000017236] Upgraded Android System WebView failing Espresso tests

 

Hi Shilpi,
 
Thanks for the patience, and I apologize for the delay.
 
It’s been awhile since the last exchange, please let me know if you are still having issues with the espresso test.
 
I researched on this issue and what I found out is:
1.      If we are loading the WebView using static way(say via Asset folder), then the issue is not reproducible.
2.      I also tried to reproduce this issue by loading the web URL-"Google.com" and can confirm that I was able to enter the text into the input elements.
3.      The test fails only with the URL-”https://secure.echosign.com/public/login”. Please let me know if this is the correct URL.
 
Also, my observations were slightly different while testing this issue. We can reproduce the issue even if the Webview is 53 and the Chrome version is 58.0.3029.83. I also see that that the WebView is able to load and locate the ID. I also checked this with the WebView team and they have confirmed that this is not an WebView issue.
 
I suspect that Chrome might have added an additional check which is failing this test. If this is the case, then I will seek out an request to the Chrome's team. Could you please confirm if the URL-”https://secure.echosign.com/public/login” is correct and I will investigate this issue further. If you have any other questions, please do let me know.
 
 
Regards,
Rohan
Android Developer Support
 

 

On 05/14/17 23:34:06 shilpi@adobe.com wrote:

Hi Tarana,

 

Is there an ETA by when the issue would be fixed? Which update of webview can we expect to have this fix?

 

Thanks,

-Shilpi

 

From: "developer-support@google.com" <developer-support@google.com>
Date: Saturday, 13 May 2017 at 7:20 AM
To: Ankit Gupta <glo67316@adobe.com>
Cc: Nidhi Khanna <nkhanna@adobe.com>, Shilpi Aggarwal <shilpi@adobe.com>
Subject: RE: [1-8121000017236] Upgraded Android System WebView failing Espresso tests

 

Hello Ankit,
 
I was able to reproduce the issue, and I confirm that the crash is happening on the latest WebView versions only, as you reported.
 
I have created an internal bug for our engineering team to have a look, and will provide an update to you as soon as I get any details.
 
Thank you for reporting this issue.
 
Have an awesome weekend!


 

On 05/10/17 05:24:27 glo67316@adobe.com wrote:

 Hi,

 

From past few days we were getting our Espresso automation test failing continuously on some Android devices. Here’s the link to our App on playstore - https://play.google.com/store/apps/details?id=com.adobe.echosign&hl=en

 

Our Android app is having a web login page that consists of a username input field, a password input field and a login button, the Espresso test was unable to enter text in username input field.

Please find below the various code snippets which we have tried in our Espresso test to bring focus in the text field or to enter value in that text field.

 

1)       onWebView().withElement(findElement(Locator.ID, "userEmail")).perform(clearElement()).perform(webKeys(email));

 

2)       onWebView().perform(script("jQuery('#userEmail').focus()"));

onWebView().withElement(findElement(Locator.ID, "userEmail")).perform(clearElement()).perform(webKeys(email));

 

3)  onWebView().withElement(findElement(Locator.XPATH, "//form[@name='loginForm']//input[@id='userEmail']")).perform(clearElement()).perform(webKeys(email));

 

 

The error in logs was – “Caused by: java.lang.RuntimeException: Error in evaluationEvaluation: status: 13 value: {message=Cannot set the selection end} hasMessage: true message: Cannot set the selection end”

 

On some devices, the tests were executed successfully but on some devices, they were not. Upon narrowing down the same we figured that -

 

1)      The devices on which Android System WebView is enabled and upgraded to 58.0.3029.83, the Espresso test fails.

2)      The devices on which Android System WebView is disabled and Google Chrome browser (having latest version 58.0.3029.83) is enabled, the Espresso test fails.

3)      On any other combinations of lower version of either Android System WebView or Chrome browser, the Espresso test executes successfully.

 

Could you please help us in understanding what must have caused this issue with the upgrade of Android System WebView in Android devices?

 

Regards,

Ankit Gupta

Hi,

Any update on this issue.

Hi, I'm not able to determine - from the description here - what the failure you're reporting is. The sample application appears to work fine in my hands.

If you could provide step by step instructions to reproduce the issue, that would be really helpful. Also, if you are experiencing a crash, please provide relevant stack traces or other logs.

Hi,

From past few days we were getting our Espresso automation test failing continuously on some Android devices. Here’s the link to our App on playstore - https://play.google.com/store/apps/details?id=com.adobe.echosign&hl=en

 

Our Android app is having a web login page that consists of a username input field, a password input field and a login button, the Espresso test was unable to enter text in username input field.

Please find below the various code snippets which we have tried in our Espresso test to bring focus in the text field or to enter value in that text field.

 

1)       onWebView().withElement(findElement(Locator.ID, "userEmail")).perform(clearElement()).perform(webKeys(email));

 

2)       onWebView().perform(script("jQuery('#userEmail').focus()"));

onWebView().withElement(findElement(Locator.ID, "userEmail")).perform(clearElement()).perform(webKeys(email));

 

3)  onWebView().withElement(findElement(Locator.XPATH, "//form[@name='loginForm']//input[@id='userEmail']")).perform(clearElement()).perform(webKeys(email));

 

 

The error in logs was – “Caused by: java.lang.RuntimeException: Error in evaluationEvaluation: status: 13 value: {message=Cannot set the selection end} hasMessage: true message: Cannot set the selection end”

 

On some devices, the tests were executed successfully but on some devices, they were not. Upon narrowing down the same we figured that -

 

1)      The devices on which Android System WebView is enabled and upgraded to 58.0.3029.83, the Espresso test fails.

2)      The devices on which Android System WebView is disabled and Google Chrome browser (having latest version 58.0.3029.83) is enabled, the Espresso test fails.

3)      On any other combinations of lower version of either Android System WebView or Chrome browser, the Espresso test executes successfully.

 

Could you please help us in understanding what must have caused this issue with the upgrade of Android System WebView in Android devices?

Hi,

Any update on this issue.

Hi Team,

Could you please update on this issue.

No feedback was received in the last 30 days from reporter "patilr@google.com", so archiving this. Please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot