New issue
Advanced search Search tips

Issue 775158 link

Starred by 0 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Lastest update of Adroid webview is causing errors in our APP

Reported by marcoshe...@gmail.com, Oct 16 2017

Issue description

Good afternoon

As the subject says, in the last update of Android webview for Android 5 and 6, and the last update of Chrome for Android 7, is causing trouble in our application.

We devepeloped an  emergency app, that is using Android webview application to show google maps, in our application we use google maps to show where  an incident is ocurring and tracking car as ambulances responding this incident.

With this last part is where Android webview latest update is causing us troubles,  because we are using signalR client services technology  and signalR server technology to do the track of the units that wants to be tracked, in order to read from the server where is exactly the position of the unit, how ever in the last update of the Android webview the instance of signalR is doing nothing when its start to track on the client side.

With this i mean that the connetion hub try to start and nothing happen not even a single error is showed.

my request header just go my version app and an authorization token that we use to autenticate an user.
The response retrieve an HTML with 3 url's one of them is the Javascript that the map will use, the other one is the CSS and the last one is the map https://maps.googleapis.com/maps/api/js?

checking on chrome inspect on the network conectivity i realized that on the old version of android web view the start conection of signalR is being executed just after the QuotaService.RecordEvent is executed just like this image shows
image

But in the newest version is not longer happening, just execute QuotaService.RecordEvent and nothing else.

image

Actually the start and the negotiate part from signalR never happens.



We already check in several forums if there’s a way to fix this, even asked signalR developers on github issues.

https://github.com/SignalR/SignalR/issues/4026#issuecomment-336957423

This error start to happen the same day that the last update of Android webview and Chrome were released, on september 25.
In order to validate if these application are causing us this troubles we downgrade to the versión of factory, the default versions of these apps in our cellphones, an xperia ultra xa with Android 7, a Samsung s5 with Android 5 and other one with Android 6, we run our application again in order to validate, and the tracking was done correctly.

i would like to know if there a way tp  fix this in our application, because it’s seems that  the last update for Android webview is not working correctly with signalR client services technology.

If you need to check some code  just ask for it.

Hope to have news about this and you can help us because we’re having issues with a lot of clients, that are Android users.

Marcos Hernandez
software engineer 
Definity First
Monterrey Mexico.
 
image1.png
27.5 KB View Download
image2.png
7.5 KB View Download

Comment 2 by ctzsm@chromium.org, Oct 16 2017

Labels: Needs-Feedback
Hi Marco, as I suggested in the Email thread, is that possible for you to get a minimized sample app to demonstrated the issue? Thanks!

It is not very easy for us to understand the underlying issue without a solid step to repro the issue.
i'm goint to work with the team in order to give you an apk for your team, as soon as it's ready i will attach it.
Project Member

Comment 4 by sheriffbot@chromium.org, Oct 16 2017

Cc: ctzsm@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "ctzsm@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Comment 6 by ctzsm@chromium.org, Oct 17 2017

Labels: Needs-Feedback
Adding back Needs-Feedback to wait for further updates from the reporter.
we realize that the error happens when we try to start the connection to signalR in javascript with this 

$.connection.hub.start() // this is ussing websockets

But just few lines below that we execute this line

window.location.href = "loadedmap://1"; //this line make everything goes wrong

this goes to android code and execute just a method that is telling the user that the map was already loaded, but for that line signalR conection hub start does not start anymore

i don't know if new android webview is doing something wrong with the href or if signalR lose target for that  new location.href

this is just happening with new android webview

we already create a dummy app in order to replicate the error and that's when we realize that is caused for href executed before signalR start

Do you know if new android webview is doing something weird when an window.location.href is executed in javascript code?



Project Member

Comment 8 by sheriffbot@chromium.org, Oct 27 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "ctzsm@chromium.org" to the cc list and removing "Needs-Feedback" label.

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

Comment 9 by torne@chromium.org, Nov 1 2017

Cc: boliu@chromium.org
Labels: Needs-Feedback
Are you handling that URL in shouldOverrideUrlLoading and returning true? I'm guessing that's what you mean by "this goes to android code and execute just a method that is telling the user that the map was already loaded"?

Can you provide an app that reproduces this, so we can look at the Java code and debug it?

Also, when you say "the last update" for WebView, which specific version are you referring to? On what version number was it working and on which version number did it break?


---

Bo, I'm wondering if this is PlzNavigate related? Are we maybe cancelling pending network requests when we get this navigation, even though the app is ultimately aborting the navigation in shouldOverrideUrlLoading (assuming my speculation is correct)
which version of webview has the problem here? PlzNavigate is only enabled in m63, which was only shipped to dev when this was original filed, and given it was on android 5 and 6, it's not likely those users are getting dev channel builds.
Labels: WV-Triaged
@marcoshernandezmora -- Could you please respond to Comment 9 & 10 and update the issue which would help us to triage the issue further.
Thanks in Advance.
Status: WontFix (was: Unconfirmed)
Closing this issue as WontFix, due to lack of response from reporter.

@marcoshernandezmora : Please feel free to log a new issue if you face any.

Thanks!!

Sign in to add a comment