soup_menu

@pythagean: Unfortunately, support for SD cards has long been a bit wonky on Android. The app does attempt to detect if an SD card exists and, if it can find one, it will add a "Download to SD Card" option to the settings, but if that option isn't showing up I'm afraid the app won't be able to save videos to the card.

@rongalaxy: Other obligations have put GBVB pretty solidly on the back-burner, so I don't think we're likely to see official support for Android 7's splitscreen mode any time soon. However, if you have a video playing app installed that can handle splitscreen mode (I believe VLC can do this), you could try long-pressing the play button in GBVB to open the video in the other app rather than using the internal player. I think that may be enough to get you up and running.

It appears that when the API is queried over HTTPS it will return image URLs that use the HTTPS protocol. Unfortunately, when attempting to access an image over HTTPS, the server responds with a status code of 200, but an empty payload. For example:

http://www.giantbomb.com/api/image/scale_large/621001-1056454795_00.gif

https://www.giantbomb.com/api/image/scale_large/621001-1056454795_00.gif

If an identical query was recently made over HTTP, it looks like a cached response will be used and HTTP URLs will be returned even to queries made over HTTPS, but tweaking the query (offset, length, etc.) will have the server sending back HTTPS URLs again.

Any chance the API could be forced to always return HTTP URLs for images or the server could be updated to serve images over HTTPS?

@frobie: It appears that when the API is queried over HTTPS it will return image URLs that use the HTTPS protocol. Unfortunately, when attempting to access an image over HTTPS, the server responds with a status code of 200, but an empty payload. For example:

http://www.giantbomb.com/api/image/scale_large/2869787-demd.jpg

https://www.giantbomb.com/api/image/scale_large/2869787-demd.jpg

If an identical query was recently made over HTTP, it looks like a cached response will be used and HTTP URLs will be returned even to queries made over HTTPS, but tweaking the query (offset, length, etc.) will have the server sending back HTTPS URLs again.

Any chance the API could be forced to always return HTTP URLs for images or the server could be updated to serve images over HTTPS?

Hey all, I wanted to pop into the thread to try to comment on some of the issues that have been cropping up in the last week or so. Based on this thread in the Bug Reporting forum, it appears that there's been some trouble in API-city of late. I'm afraid I don't know any more than what can be found in there at the moment, but the good news is that Giant Bomb's team is on the case.

Hey all, I wanted to pop into the thread to try to comment on some of the issues that have been cropping up in the last week or so. Based on this thread in the Bug Reporting forum, it appears that there's been some trouble in API-city of late. I'm afraid I don't know any more than what can be found in there at the moment, but the good news is that Giant Bomb's team is on the case.

@likwidtek: You're very welcome. Re: Apple TV, I'm afraid I don't have anything cooking right now.

@likwidtek: I suspect the problem is that the APK linked from the first post was a few versions out of date. I just uploaded the current build, so if you re-download and sideload that one you should be up and running in no time. Sorry for the inconvenience!

@vivek: I'm afraid I'm not sure what Apple TV app you would have downloaded. As I mentioned, I'm not currently working on an Apple TV version of GBVB, so you would need to contact that other app's developer if you have questions about it.

Hey all. It's been a while since I've had a chance to check in on the thread, so I wanted to pop by real quick and try to answer one or two questions that had cropped up.

On the topic of Apple TV, I'm afraid that isn't something that's currently on the road map. Never say never, but right now I'm a little too busy to undertake a project like that.

Regarding the 20 video per day limit, it's a temporary situation. Updating the app to work with the new API will take some time and, as I mentioned in the in-app news, it may require changing or removing some features (I'm intentionally remaining vague at the moment because I'm not yet certain exactly how things will shake out). In order to avoid delaying deployment of the new API or having GBVB go dark until I can get it updated, a compromise was made to keep the old API working, but to impose a limit on use. I know it's not ideal, but the number should hopefully be high enough to not cause too much trouble for users while still allowing Giant Bomb to move forward with the changes.

As always, thanks for being a stand-up bunch of users! You guys are alright in my book.

@rincewind: Not without some API changes, I'm afraid.