Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Issue with S7 Video Viewer with Android

Avatar

Level 2

Hello,

we have just replaced the S7Video Viewer with a version hosted locally (v3.2.1), but unfortunately i got an issue with the video player on android.

It works well on all platform, including IOS (launch the native player).

But when it comes to Android - no way to make it works, it seems to play, ... but never play

This is a code example of how it is init :

   var s7videoviewer = new s7viewers.VideoViewer({

                'containerId' : $video.attr('id'),

                'params' : {

                    'VideoPlayer.ssl' : 'on',

                    'serverurl' : 'https://company-h.assetsadobe2.com/is/image',

                    'contenturl' : 'https://company.assetsadobe.com/',

                    'config' : 'etc/dam/presets/viewer/Video',

                    'videoserverurl' : 'https://gateway-eu.assetsadobe.com/DMGateway/public/company',

                    'posterimage' : asset,

                    'asset' : asset,

                    'autoplay' : autoplay.toString(),

                    'waiticon' : 1

                }

            });

s7videoviewer.init()

Here is an page example where you can see the video player :

http://tiny.cc/aguapy

Any idea ?

Thanks in advance,

1 Accepted Solution

Avatar

Correct answer by
Administrator

Engineering team looked at your code. It's difficult for them to troubleshoot w/o being able to access the actual embed code.

Please create a support ticket for this to get them debug this fully.

-Kautuk

View solution in original post

6 Replies

Avatar

Administrator

Asked internal experts to have a look at this one!!

-Kautuk

Avatar

Level 2

I reverted our stage environment with the previous version we were using (s7sdk 2.1) instead of s7sdk 3.2 as i need to do a deployment tomorrow.

I will re=-update again by tomorrow.

Avatar

Level 2

Hello,

Here is an update :

I tried to use the last version of the s7viewer in order to have a player HLS compatble.

But this player is not working on Android.

(On real device, it launch the native player on IOS, but nothing happens on Android (tested multiples devices), you can also reproduce using the developer panel of Chrome).

You can have an example here :

LINK (not the top video, the one in the middle of the page)

Here are parameter that we are using

            var s7videoviewer = new s7viewers.VideoViewer({

                'containerId' : $video.attr('id'),

                'params' : {

                    'ssl' : 'on',

                    'serverurl' : 'https://xxxx-h.assetsadobe2.com/is/image',

                    'contenturl' : 'https://xxxx.assetsadobe.com/',

                    'config' : 'etc/dam/presets/viewer/Video',

                    'videoserverurl' : 'https://gateway-eu.assetsadobe.com/DMGateway/public/xxxx',

                    'posterimage' : asset,

                    'asset' : asset,

                    'autoplay' : autoplay.toString(),

                    'progressivebitrate' : '3000',

                    'initialbitrate' : '3000'

                }

            });

We rely on this script :

s7d1.scene7.com/s7viewers/html5/js/VideoViewer.js

I noticed some weird 403 call (desktop or mobile)

https://xxxx.assetsadobe2.com/is/image/content?req=message&message=,0,LOAD,506,expeditions,5.8.4,3.3...

So multiple solutions :

- It’s a bug of the current S7Viewer, but i guess we already rely on the last version

- Can we deactivate the native player on mobile/touch device ? (keep the desktop player even on mobile)

Small additions if you force a desktop user agent on Android it works well

Thanks in advance for your support

Avatar

Level 2

Still the same issue,

i just posted an update

Avatar

Correct answer by
Administrator

Engineering team looked at your code. It's difficult for them to troubleshoot w/o being able to access the actual embed code.

Please create a support ticket for this to get them debug this fully.

-Kautuk