Hi Juliane,
Thank you for reaching out to us.
Have you replicated the same behavior using our sample apps? Would you be able to share with us a screen recording of the behavior as well as the version of the Android SDK you are using?
On the other hand, please be reminded that in starting adsManager, Initializing the container must be done via a user action on mobile devices. Please check here for more information.
Regards,
|
||||||
The team had a look at what you suggested and we think we found how to fix the issue. But we need the relevant team on your end to fix it.
.........
The exception which we can see using the Remote Debugging tool is -> ima-video.js:1 Uncaught (in promise) DOMException: play() can only be initiated by a user gesture.
was fixed in our sample application having a plain webview with below settings -
webViewSettings.setMediaPlaybackRequiresUserGesture(false);
Attached is the video properly playing as expected using the above settings in Android native code on the webview (there is another video in my initial message showing the issue).
Can something similar be done in Google News Android App to fix this issue?
There was a similar issue in Flipboard that the support team fixed and I believe this is what they've done.
Hi Julianne,
Thank you for responding back to us.
We could not see any supposed attached screen recording of the behavior from your last response. Additionally, can you confirm what version of the SDK you are using? We would also require the sample app you are using that can reproduce the same behavior to check and test on our end. And please share the steps we need to take in order to replicate the issue.
You may send the requested information via "Reply To Author" button or directly send it to our testing alias: imate...@gmail.com. Let us know here once it has been submitted.
Regards,
Hi Juliane,
Thank you for responding back to us.
Just to clarify, did you mean that you are using two applications: one that has a fixed for the error by using webViewSettings.setMediaPlaybackRequiresUserGesture(false); and another one (Google News Android App) where the issue is still reproducible, is that correct?
Additionally, have you followed the instruction in our guide that to fully support Ad playback on mobile browsers, starting AdsManager should be triggered by a user interaction?
Could you also please confirm which SDK and SDK Version you are using? We would also need the sample project application that can reproduce the same behavior you are reporting, along with the steps to replicate the issue.
On the other hand, you can also test on our sample apps and share the details of the app you use that can replicate the issue. If it is not reproducible there, we would highly recommend to pattern your work againsts our sample apps to avoid implementation issues.
Kindly address all the asks above in order to speed up the process of the investigation.
You may send the requested information via "Reply To Author" button or directly send it to our testing alias: imate...@gmail.com. Let us know here once it has been submitted.
Regards,
Just to clarify, did you mean that you are using two applications: one that has a fixed for the error by using webViewSettings.setMediaPlaybackRequiresUserGesture(false); and another one (Google News Android App) where the issue is still reproducible, is that correct?
[Fox Sports]: We are not using any native App to load our articles. Our articles are loaded in Google News App and that has issue loading our videos.
Additionally, have you followed the instruction in our guide that to fully support Ad playback on mobile browsers, starting AdsManager should be triggered by a user interaction?
[Fox Sports]: we don’t start AdsManager, it is starting in google’s js(https://3p.ampproject.net/2110290545003/vendor/ima-video.js), we only use below tag:
<amp-ima-video 2 id={nodeId} 3 width="1.77" 4 height="1" 5 layout="responsive" 6 data-tag={adsUrl} 7>
Could you also please confirm which SDK and SDK Version you are using? We would also need the sample project application that can reproduce the same behavior you are reporting, along with the steps to replicate the issue.
[Fox Sports]: We don’t have any native App so not using ima sdk. Not Applicable
OSGn: the other hand, you can also test on our sample apps and share the details of the app you use that can replicate the issue. If it is not reproducible there, we would highly recommend to pattern your work againsts our sample apps to avoid implementation issues.
[Fox Sports]: We don’t have any native App so not using ima sdk. Not Applicable
Hi Juliane,
Pardon me but I am a little confused on your response here. You must have a web app or native app in order to use our SDK of your choice (HTML5, Android, iOS). And only if you are using our SDK we can help you. However, you mentioned that you do not have any app, and you do not use IMA SDK. So I am uncertain how you are using the SDK. In that sense, I am not sure as well how we can help you as most of the issues with IMA are getting investigated and resolved via a replication of the issue on the apps where it is reproducible.
You may want to check our Get Started guide to know how you can use IMA SDK in your applications.
Do not hesitate to come back to us with any clarifications on the issue.
Regards,