Something went wrong. Try again later

conmulligan

This user has not updated recently.

2292 11722 101 18
Forum Posts Wiki Points Following Followers

conmulligan's forum posts

Avatar image for conmulligan
conmulligan

2292

Forum Posts

11722

Wiki Points

18

Followers

Reviews: 0

User Lists: 11

#1  Edited By conmulligan

@ev77: Yep, the API key is still being appended. Could very well be a tvOS-specific issue! You might be able to gain some insight by inspecting the `accessLog()` on `AVPlayerItem` — each event has a `uri` property that contains the canonical asset URL for that point in time.

Avatar image for conmulligan
conmulligan

2292

Forum Posts

11722

Wiki Points

18

Followers

Reviews: 0

User Lists: 11

@ev77: Generally speaking, my AVPlayer configuration still works — I'm just passing an `AVPlayerItem` with the destination URL and AVPlayer follows the redirect like you'd expect. It does have some trouble resuming playback if you leave a video paused for an extended period of time that I suspect might be caused by these changes, but I haven't really investigated yet.

Avatar image for conmulligan
conmulligan

2292

Forum Posts

11722

Wiki Points

18

Followers

Reviews: 0

User Lists: 11

I'm not sure if this is related to any of the issues previously reported, but it looks like video URLs served from the cdn.jwplayer.com domain have an extremely short expiry date (approx. 5 minutes). I'm guessing this is as an alternative to passing an API key? In any case, this is likely behind some of the playback issues people have been experiencing in client apps.

Avatar image for conmulligan
conmulligan

2292

Forum Posts

11722

Wiki Points

18

Followers

Reviews: 0

User Lists: 11

Avatar image for conmulligan
conmulligan

2292

Forum Posts

11722

Wiki Points

18

Followers

Reviews: 0

User Lists: 11

#5  Edited By conmulligan
Avatar image for conmulligan
conmulligan

2292

Forum Posts

11722

Wiki Points

18

Followers

Reviews: 0

User Lists: 11

@nhlmaniac: Hey, thanks for flagging this! Unfortunately it appears to be an OS issue without a clear workaround, so there may not be anything I can do at the moment. I've reported the issue to Apple though, so hopefully it gets cleared up in Beta 4.

Avatar image for conmulligan
conmulligan

2292

Forum Posts

11722

Wiki Points

18

Followers

Reviews: 0

User Lists: 11

Avatar image for conmulligan
conmulligan

2292

Forum Posts

11722

Wiki Points

18

Followers

Reviews: 0

User Lists: 11

Hey folks, version 1.10 is live on the store now. This update adds new video quality options, (optional) push notifications when Giant Bomb is hosting a Twitch stream, and an updated home screen which includes active Twitch streams and GB Infinite. The full changelog is below!

  • Added new Mobile and Medium quality options for supported videos.
  • You can now optionally receive notifications when Giant Bomb is hosting a Twitch stream.
  • The home screen now includes active Twitch chats and GB Infinite.
  • Added an “Open in YouTube” menu option for supported videos.
  • Fixed an issue where real staff names aren’t used when a video has multiple upload credits.
  • Fixed an issue where the player would enter an invalid state after resuming the app when the “Pause in Background” setting in enabled.
  • Improved UI performance.
  • Improved registration flow.
  • Significantly improved database read performance.
  • Optimized disk writes.
  • Miscellaneous UI tweaks.
Avatar image for conmulligan
conmulligan

2292

Forum Posts

11722

Wiki Points

18

Followers

Reviews: 0

User Lists: 11

Hey! I'm not sure if this is related to any Chromecast issues previously reported, but for at least the past few weeks there's been an issue casting livestreams using both the site player and third-party apps. Archived video appears to be unaffected.

I did a little digging and my best guess is that it's being caused by a misconfigured CORS header; specifically, the `access-control-allow-origin` header is set to only allow requests from https://www.giantbomb.com, which may be preventing cast receivers from accessing the HLS manifest:

< access-control-allow-origin: https://www.giantbomb.com

In contrast, an archived video URL includes a wildcard CORS header:

< access-control-allow-origin: *

Hope this is helpful!

Avatar image for conmulligan
conmulligan

2292

Forum Posts

11722

Wiki Points

18

Followers

Reviews: 0

User Lists: 11

@elwood: Ok, so I have good news and bad news. The good news is that I've been able to reproduce the issue, and I think I've identified the root cause. The bad news is that it appears to be a configuration issue on GB's end, which means there's nothing more I can really do to address it. I'll report the issue though and hopefully top men can take a look!