Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Player throws error in the Google search console #7547

Open
almoloo opened this issue Nov 5, 2024 · 4 comments
Open

Player throws error in the Google search console #7547

almoloo opened this issue Nov 5, 2024 · 4 comments
Labels
flag: seeking PR We are actively seeking PRs for this; we do not currently expect the core team will resolve this priority: P3 Useful but not urgent type: bug Something isn't working correctly
Milestone

Comments

@almoloo
Copy link

almoloo commented Nov 5, 2024

Have you read the FAQ and checked for duplicate open issues?
Yes.

If the problem is related to FairPlay, have you read the tutorial?

N/A

What version of Shaka Player are you using?

4.11.7

Can you reproduce the issue with our latest release version?
I have not yet tried the latest release version.

Can you reproduce the issue with the latest code from main?
I have not yet tried the latest code from main.

Are you using the demo app or your own custom app?
I’m using my own custom app.

If custom app, can you reproduce the issue using our demo app?
I can not test this issue on the demo app.

What browser and OS are you using?
Observed in Google Search Console’s rendering tool.

For embedded devices (smart TVs, etc.), what model and firmware version are you using?
N/A

What are the manifest and license server URIs?

If necessary, I can provide these privately.

What configuration are you using? What is the output of player.getNonDefaultConfiguration()?

I can provide this configuration if needed.

What did you do?

Integrated Shaka Player (version 4.11.7) on my website to play MPEG-DASH videos, which functions correctly on my site but encounters an error in Google Search Console.

What did you expect to happen?
I expected Google Search Console to render my page without error as it is doing now with jwplayer.

What actually happened?

In Google Search Console’s rendered view, the following error appears:

Shaka Error MANIFEST.CONTENT_UNSUPPORTED_BY_BROWSER ()
    at new shaka.util.Error ([hidden_url]:1:73707)
    at shaka.media.ManifestFilterer.checkPlayableVariants_ ([hidden_url]:1:293598)
    at $jscomp.generator.Engine_.program_ ([hidden_url]:1:292796)
    at $jscomp.generator.Engine_.nextStep_ ([hidden_url]:1:11407)
    at $jscomp.generator.Engine_.next_ ([hidden_url]:1:10371)
    at $jscomp.generator.Generator_.next ([hidden_url]:1:11852)
    at t ([hidden_url]:1:12271)

Are you planning send a PR to fix it?
Not at this time.

@almoloo almoloo added the type: bug Something isn't working correctly label Nov 5, 2024
@shaka-bot shaka-bot added this to the v4.12 milestone Nov 6, 2024
@avelad
Copy link
Member

avelad commented Nov 6, 2024

The error you get is that there is some format that is not supported. In order to help you we need more information:


**What are the manifest and license server URIs?**
<!-- NOTE:
  You can send the URIs to <[email protected]> instead,
  but please use GitHub and the template for the rest.
  A copy of the manifest text or an attached manifest will **not** be
  enough to reproduce your issue, and we **will** ask you to send a
  URI instead.  You can copy the URI of the demo app to send us the
  exact asset, licence server, and settings you have selected there.
  Avoid geo-blocked content if at all possible, as the contributors who diagnose
  Shaka Player issues may not be able to access it.
  If you send the URIs to email, the response time and resolution
  will be much higher.
-->

@avelad avelad added the status: waiting on response Waiting on a response from the reporter(s) of the issue label Nov 6, 2024
@almoloo
Copy link
Author

almoloo commented Nov 6, 2024

The error you get is that there is some format that is not supported. In order to help you we need more information:


**What are the manifest and license server URIs?**
<!-- NOTE:
  You can send the URIs to <[email protected]> instead,
  but please use GitHub and the template for the rest.
  A copy of the manifest text or an attached manifest will **not** be
  enough to reproduce your issue, and we **will** ask you to send a
  URI instead.  You can copy the URI of the demo app to send us the
  exact asset, licence server, and settings you have selected there.
  Avoid geo-blocked content if at all possible, as the contributors who diagnose
  Shaka Player issues may not be able to access it.
  If you send the URIs to email, the response time and resolution
  will be much higher.
-->

Here is a sample manifest, and there's no license server:
https://s24.namasha.com/dash/7319859993/Manifest.mpd

<?xml version="1.0"?>
<!-- MPD file Generated with GPAC version 0.7.0-rev0-gbd5c9af-master  at 2021-08-24T06:24:10.216Z-->
<MPD xmlns="urn:mpeg:dash:schema:mpd:2011" minBufferTime="PT1.500S" type="static" mediaPresentationDuration="PT0H3M3.228S" maxSegmentDuration="PT0H0M10.000S" profiles="urn:mpeg:dash:profile:isoff-on-demand:2011">
 <ProgramInformation moreInformationURL="http://www.namasha.com">
  <Title>generated by namasha</Title>
 </ProgramInformation>

 <Period duration="PT0H3M3.228S">
  <AdaptationSet segmentAlignment="true" maxWidth="1280" maxHeight="720" maxFrameRate="24" par="16:9" lang="und" subsegmentAlignment="true" subsegmentStartsWithSAP="1">
   <ContentComponent id="1" contentType="video" />
   <ContentComponent id="2" contentType="audio" />
   <Representation id="1" mimeType="video/mp4" codecs="avc1.640028,mp4a.40.2" width="1280" height="720" frameRate="24" sar="1:1" audioSamplingRate="44100" startWithSAP="1" bandwidth="959746">
    <AudioChannelConfiguration schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"/>
    <BaseURL>720p_dashinit</BaseURL>
    <SegmentBase indexRangeExact="true" indexRange="1457-1716">
      <Initialization range="0-1456"/>
    </SegmentBase>
   </Representation>
   <Representation id="2" mimeType="video/mp4" codecs="avc1.42C01E,mp4a.40.2" width="852" height="480" frameRate="24" sar="640:639" audioSamplingRate="44100" startWithSAP="1" bandwidth="685347">
    <AudioChannelConfiguration schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"/>
    <BaseURL>480p_dashinit</BaseURL>
    <SegmentBase indexRangeExact="true" indexRange="1455-1714">
      <Initialization range="0-1454"/>
    </SegmentBase>
   </Representation>
   <Representation id="3" mimeType="video/mp4" codecs="avc1.42C01E,mp4a.40.2" width="640" height="360" frameRate="24" sar="1:1" audioSamplingRate="44100" startWithSAP="1" bandwidth="461037">
    <AudioChannelConfiguration schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"/>
    <BaseURL>360p_dashinit</BaseURL>
    <SegmentBase indexRangeExact="true" indexRange="1451-1710">
      <Initialization range="0-1450"/>
    </SegmentBase>
   </Representation>
   <Representation id="4" mimeType="video/mp4" codecs="avc1.42C01E,mp4a.40.2" width="426" height="238" frameRate="24" sar="1904:1917" audioSamplingRate="44100" startWithSAP="1" bandwidth="277647">
    <AudioChannelConfiguration schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"/>
    <BaseURL>240p_dashinit</BaseURL>
    <SegmentBase indexRangeExact="true" indexRange="1455-1714">
      <Initialization range="0-1454"/>
    </SegmentBase>
   </Representation>
   <Representation id="5" mimeType="video/mp4" codecs="avc1.42C01E,mp4a.40.2" width="256" height="144" frameRate="24" sar="1:1" audioSamplingRate="44100" startWithSAP="1" bandwidth="159402">
    <AudioChannelConfiguration schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"/>
    <BaseURL>144p_dashinit</BaseURL>
    <SegmentBase indexRangeExact="true" indexRange="1450-1709">
      <Initialization range="0-1449"/>
    </SegmentBase>
   </Representation>
  </AdaptationSet>
 </Period>
</MPD>

@shaka-bot shaka-bot removed the status: waiting on response Waiting on a response from the reporter(s) of the issue label Nov 6, 2024
@avelad
Copy link
Member

avelad commented Nov 7, 2024

@joeyparrish do you have any idea?

@joeyparrish joeyparrish added priority: P3 Useful but not urgent flag: seeking PR We are actively seeking PRs for this; we do not currently expect the core team will resolve this labels Nov 7, 2024
@joeyparrish
Copy link
Member

I do not know what would cause this, but I assume that the search console is embedding your page in an iframe, and it may not have the necessary rights to play media, or there may be modifications in the environment of that frame that break the player or its polyfills in some way.

I have no experience with the Google Search Console, and I assume I won't be able to access your dashboard to debug it myself.

If you can use a debug build of Shaka Player, and enable verbose logging in your app, you may be able to give us logs of the failure in context of Google Search Console. That might help us figure out what is causing the incompatibility.

But since this isn't affecting actual visitors to your site, only the rendering of your page for your eyes only in Google Search Console, I'm marking this at a low priority (P3).

@joeyparrish joeyparrish removed their assignment Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flag: seeking PR We are actively seeking PRs for this; we do not currently expect the core team will resolve this priority: P3 Useful but not urgent type: bug Something isn't working correctly
Projects
None yet
Development

No branches or pull requests

4 participants