New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 915129 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 3
Type: Bug



Sign in to add a comment

Video not showing in WebView with chrome client but works fine on Custom chrome tab.

Reported by rishabhm...@gmail.com, Dec 14

Issue description

Device name: Redmi Note 4 Buid/NRD90M
Android version: Android 7.0
WebView version : 70.0.3538.110
Application: ConnectUsPro
Application version: 1.1.48

URLs (if applicable):
https://play.google.com/store/apps/details?id=com.connectuscom.uc.professional

Its video calling feature was working fine until I updated my chrome to version 71. After that only my video was displaying on video call activity and other side's video was not showing. But when I am opening the same link on Google Chrome for Android, it works fine.

Steps to reproduce:
(1) Use webview with chrome client.
(2) Open the meeting url link.
(3) Open the same link using google chrome.

Expected result:
 I expected Webview with chrome client to have the similar behaviour as that of 
 a chrome tab.

Actual result:
  Video of other side not visible in the webview. Attached is the screenshot.


 
1544770356404.JPEG
129 KB View Download
Screenshot_2018-12-12-20-32-54-868_com.connectuscom.uc.professional.png
250 KB View Download
Labels: Needs-triage-Mobile
Cc: chelamcherla@chromium.org
Labels: WV-Triaged Needs-Feedback
@ rishabhmaurya.maurya: Didn't find an option to register new account, could you please provide link or sample credentials to test this issue. Please also provide screencast of the issue, this would help in further triaging of the issue.

Thanks!
Project Member

Comment 4 by sheriffbot@chromium.org, Dec 17

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: -chelamcherla@chromium.org sindhu.chelamcherla@chromium.org ntfschr@chromium.org
Labels: Neededback
Does your app use webrtc?
Yes, it uses WebRTC.
Labels: -Neededback
Cc: mcasas@chromium.org
Components: Blink>WebRTC
We had another report about webrtc in https://issuetracker.google.com/issues/121331520. Maybe something broke?

Could someone from the WebRTC team take a look (perhaps mcasas@)? We have instructions at http://go/clank-webview/how-do-i-get-webview-version.
Owner: niklase@chromium.org
Status: Untriaged (was: Unconfirmed)
forwrding to niklase@ to triage. thanks ntfschr@ !
Labels: Needs-Feedback
Status: Assigned (was: Untriaged)
Does your application use URL.createObjectURL by any chance? (It was deprecated in 65 and removed in 71. We have had reports of some applications failing because of this)
No, not at all.
By navigating throught the source I found that the included file 
https://code.createjs.com/soundjs-0.6.2.min.js uses createObjectURL(), which has been removed in 71 (the alternative is to use the srcObject field).
Perhaps this is what is causing the problem.
Cc: niklase@chromium.org
Owner: guidou@chromium.org
Assigning to myself temporarily until we confirm or discard createObjectURL() as the root cause.
I haven't used createObjectURL anywhere in the application. It cannot be the root cause.
Are you using srcObject directly to assign the mediastream to the video element?
If so, you are not using createObjectURL. If not, you might be using it through a library.

Sign in to add a comment