alecgdouglas

@soralapio: You'll need to 'refresh' a few times to pull in older videos. This is the other side of the cache problem.

The refresh button is on the very bottom row.

Hey all,

Sorry for the lack of any response here - last year I had a kid and the time I have available for working on this app is hovering somewhere below 0 hours. I'd definitely make an effort to carve out time if anyone has a pull request for me on the open source BitBucket repo (https://bitbucket.org/alecgdouglas/gbenthusiast) but beyond that, I just can't.

@flammabled has the workaround for the 404 issue - you need to clear app data. You'll also probably have to refresh the video feed (bottom row, "Actions" -> "Refresh Videos") a few times in order to fetch the older videos as well.

Unfortunately, because progress syncing hasn't been implemented, clearing app data will also wipe out your progress on videos so you'll want to make note of where you are in videos before doing this.

I haven't had time to look into the 404 issue beyond just verifying that it fixed it for me too, but my guess is that the cached URL for older videos saved in the app is no longer valid after some migration occurred on Giant Bomb's end.

This is a side-effect of a more fundamental problem with how the app fetches and manages data from the GB API, and is also related to how you need to refresh the videos a few times before you get older videos showing up at all.

Issue to fix this: https://bitbucket.org/alecgdouglas/gbenthusiast/issues/53/refactor-remove-local-storage-query-from

I had someone looking into this and he made some progress but it looks like his fork hasn't seen any activity since June 2019, so it's probably up for grabs again.

@odc: I've all but stopped actively developing features for the app. I'm happy to take a look at pull requests and manage releasing updates, but between my newborn and work I just haven't had time to work on this.

Feel free to try finishing out video progress sync - I'm sure there are a lot of users out there that would appreciate that! :)

@pythagosaurus: Hey there, really sorry to hear all the trouble you're having getting videos to play in the app. It sounds like you've done all the troubleshooting I could suggest, and since I don't have a Shield to test on myself and it sounds like it's working for most other Shield users, I'm not really sure what else can be done.

It sounds like you should easily be able to stream the highest quality, but out of curiosity, does the same happen even if you select the lowest quality?

Do you have any issues streaming other media on that device?

@envincebal: Just a heads up - you shouldn't post your API key (assuming that is your actual API key). That's tied to your account and can be abused, causing issues for you GB account.

It would be great if the API had better support for adding the GiantBomb TV steam to apps.

I realize you can get some info about the current stream from the /chats endpoint, but right now the only useful information is the channel_name value. This is fine if you know for sure that it's going to be either a Twitch channel name or the ID of a YouTube video, but there's no way to be sure which one it is (or if it's for some other streaming service).

GB devs - could you add another key:value pair to the chats response that indicates which platform GB TV is running on, or add a dedicated GB TV API endpoint that has this information?

Thanks

@animatr0ni0: You'll be happy to hear that someone from the community has picked up that issue and currently has an update that's in review.

Can't give an ETA (it's largely up to them and their schedule), but it's being worked on :)

@flammabled: Thanks for the heads up - I tried making them public. Let me know if you can see them now.

@dizagaox: Sure, that's something I considered - if not an embed, then maybe an intent to the YouTube app. However, the issue with that is if it's not officially supported by the API then there's no expectation that the specific YouTube link won't change and break that functionality in the app that will require a fix and a new update to be pushed out.

Buuuuut also, as I wrote that I dug a little more into the API and found that the /chats API could make this work with official support, so I filed this issue if anyone is interested in picking it up:

https://bitbucket.org/alecgdouglas/gbenthusiast/issues/54/add-button-to-open-giant-bomb-infinite-in

@fireworksordie: Thanks for looking into that - glad to hear it was just an issue on GB's end :)

@jaytima: As far as I'm aware, there isn't yet a supported way to implement GB Infinite support. Maybe once it's out of beta?

@dizagaox: Thanks!

@flammabled: Good question - I just decided to make the repo public as my time has been too occupied with other things to give the app the attention it needs. Feel free to take a look and send a pull request if you'd like to contribute (might be a good idea to discuss your intention with me first though so there's less chance of you wasting your time though!)

https://bitbucket.org/alecgdouglas/gbenthusiast