alecgdouglas

@digthedoug: Hey there, sorry for the late response. I have support for the sync'd progress API in a half-finished state and just haven't had the chance to work on in quite a while (work has been pretty crazy). Actually, it's been long enough that I'd probably start over if I were to pick the work up again.

Honestly, I'm starting to feel a bit guilty about not having the time to keep improving this app, so maybe it's time to finally let someone else contribute. I haven't put the effort into cleaning up the codebase enough to make it public anywhere (hint: it's not great), but it's currently private on BitBucket. If you're interested in working on the sync functionality, I could grant you access and you could tinker with it. DM me if that's something you'd like to do.

@alpharudy: Heh, that's very kind of you to offer. No donations needed, but I appreciate it :)

@theironyuppie: @btsjigs: Thank you both for the kind words :)

@jbick89: Sorry for not closing the loop on this earlier. It seems that the issue was on the Giant Bomb side and has been resolved by them. Definitely let me know if you're still running into issues though.

@jbick89: Hey there - thanks for letting me know. I was able to reproduce this and I'm looking into it now. I'll try to get a fix out ASAP - sorry about this!

@fireworksordie: That screenshot is very helpful. I just pushed out another update to the beta pool (1.142) that will hopefully fix the issue (again, difficult to test since I don't have a device that has the old data on it). It's a bit of a hacky fix but should be okay until I refactor the app so this is less of a problem.

Let me know if you're able to watch these videos once you get the update - thanks!

@fireworksordie: Yep, that's a known issue - I suspect the redirects for video URLs that were retrieved before the switch to https are incorrect. I'm not 100% sure since I don't have any devices that have data from before the switch to https, but from what I can gather, it's like this:

For examle, the API used to return:

http://giantbomb-pdl.akamaized.net/video/vf_persona4_01_3500.mp4

Which gets redirected to:

https://www.giantbomb.com/cdnAuth/video/vf_persona4_01_3500.mp4 (which isn't a valid resource)

but the actual correct URL is:

https://giantbomb-pdl.akamaized.net/video/vf_persona4_01_3500.mp4

I actually pushed out an update to the beta pool just this morning that has a potential workaround. Check that you have version 1.141 and if so, try watching one of the videos that was giving you this error (e.g. Papa Vinny's Pizza Party) and let me know if it works.

Failing all that, if you're feeling reckless you can just clear app data and have the app re-retrieve the video data which will provide you with the correct (https) video URLs. You'll also probably need to manually refresh a couple times to backfill your database with older videos.

@blacklagoon: If a new video isn't showing up, you can try manually refreshing the videos by going to the bottom row on the main screen and clicking on the refresh button.

Regarding the crashes - I just pushed an update that should fix the top two crashes I was seeing reported through the Android developer console. Hopefully the one you were seeing has been fixed now. The version with the fix is 1.13.

@dave_tacitus: Thanks for the heads up. Hopefully the crash rate should be reduced once you receive version 1.13.

@w1ssy: Sorry for the delayed response. If you're the person that emailed gbenthuasiast (at) gmail.com then I just responded. Just need to know exactly which Mi Box you have.

@johnny_rico_121: Hi there - sorry to hear that. That sounds quite odd. The only thing I can think for you to try would be to clear the app cache, retry, and if that doesn't work, then clear app data and retry (warning: this will reset all of your current video progress).

As a general note - I'm sorry for the lack of updates lately, I know it's been a few months since the last one. I've been, well, playing a lot of video games in my spare time instead of programming, so I hope you can understand ;)

The progress sync feature has been stalled for quite a while now but that's still on the top of my TODO list since it's nearly complete.

@narthollis: Thanks for the kind words. I could probably shorten the authorization URL a bit in a future release - thanks for the feedback :)

@paliv: I appreciate you taking the time to let me know - thanks!

@karspankey: You're very welcome, thanks for giving it a try!

@lebkin: I'm really glad to hear you're enjoying it! I know the Roku app has been facing some issues lately, but if you haven't already checked it out the GBTV app for Apple TV looks promising: https://www.giantbomb.com/forums/general-discussion-30/ios-app-introducing-gbtv-a-new-giant-bomb-video-ap-1808300/

@ramsaya92: Hm I'm not sure about either of those apps (Video Bomb and Video Buddy are both developed by different people) - are you saying that the GB Enthusiast app also crashes on Fire TV? I haven't seen this issue. I'm about halfway through watching the Exquisite Corps video on my Fire TV and haven't noticed any problems.

@mustainium: Haha that's great! Giant Bomb is pretty much the only reason I always take my Fire TV Stick with me when I travel now ;)

Same null result from the current-live API for the "Honey, Who Shanked Murder Island" stream today.

@mister_v: Looks like the API isn't returning an HD URL for that video, hopefully that'll get updated soon from GB's end but in the meantime try watching it on "High" or "Low" quality.

(The app should totally handle that more gracefully, I'll put that on my to-do list!)