soup_menu

@codicier: Toggling the watched state is something I can keep in mind for a future release. In the mean time, if you start playing a video (even for a second or two) it will reset it to be unwatched. If you then watch that video all the way through it will get marked as watched again.

Quick follow-up for the benefit of anyone finding this thread after the fact: the original sorting behavior was restored yesterday (November 1, 2013).

I have it on good authority that the original API behavior will be restored sometime tomorrow. Thanks for hanging in there, duders!

Update: We're Back!

Big ups to the Giant Bomb engineering team for helping get us back to good. They aren't called Top Men for nothing.

I also want to thank all of you. When I saw the app start acting funny I braced myself for 1-star reviews and upset users, but I didn't encounter any of that. The Giant Bomb crew often talk about how they have the best audience and I absolutely agree. You guys are amazing.

The videos API appears to be back up and running, but the default sort order seems to have changed. If the old API behavior can be restored the app will start working correctly again on its own, otherwise I'll need to work on an update. I appreciate everyone's patience while things get sorted out.

Some time this afternoon I stopped receiving 500 and started seeing results again. The only trouble is that the default sort order appears to have changed. Yesterday http://www.giantbomb.com/api/videos/?api_key=<key>&limit=10 would return the 10 videos with the highest publish_date. Now that query is giving the 10 videos with the lowest id sorted in descending order by publish_date. Explicitly setting a sort order (like "sort=publish_date:desc") works as expected, but I was wondering if there was any chance the original behavior might be restored?

Relying on default behavior was perhaps a poor choice on my part, so if that's not an option I would understand, but Apple's review process means that, even if I were to get a new build submitted today, it would likely be at least a week before users of the iOS version of Giant Bomb Video Buddy would be back to good.

@evil_alaska: @counterclockwork87: @zero_: @ted_mosby: Unfortunately, it looks like there may be some issues with the API right now. I've posted in the API Developers forum and will update the app's home page and this thread once I know more. Sorry for the inconvenience.

I've recently noticed some issues with the /api/videos endpoint. There have been two times in the past few weeks (including tonight) when I've encountered stretches in the evening where all requests for videos come back with a status code of 500. The issue doesn't seem especially frequent and it has always resolved itself by the next day, but since I had a chance to do a little investigation tonight I wanted to report my findings in the event that they prove useful:

• The issue doesn't appear to affect the rest of the API, nor does it seem related to my API key. I've tested several other endpoints (chats, objects, games, characters, promos, and people) and they all seem to be functioning normally.
• Requests with additional parameters (format, limit, offset, filter, etc) still come back as 500, but omitting all parameters does produce the expected HTTP 200 / "Invalid API Key" error.
• I can't recall the date I last saw the issue, but I do know that it's been going on tonight since at least 9:30pm CDT.

I know that's not exactly an exhaustive report, so if there's any other information I can provide, please let me know.

@zero_: I ended up using Environment2, a library that parses the vold.fstab and vold.conf files to find all of the mounted filesystems and then exposes them in a manor similar to Android's Environment class. The documentation is in German, but the code is pretty easy to follow and everything worked as expected. The author hasn't specified a license, so you'll need to contact him directly to obtain permission to use it, but he seemed like a nice guy, so I suspect that a polite email would probably be all you need.

@numberthree: Chromecast seems like it could potentially be interesting, but it's not something I'm actively investigating right now. My current thought is to wait until the SDK makes it past being a Developer Preview and then see where things stand. If you do end up making something I'd love to see it. I haven't had a ton of time for experimentation lately, so getting to peek at a Chromecast project could be fun.

@raymath: Bug confirmed. I'm not sure why iOS 7 would have broken that, but I can definitely take a look. It probably won't be right away, but hopefully I'll get a chance to work on an iOS7-focused update toward the end of the month.

@cyberbloke: Thanks for letting me know. Unfortunately, I don't think there's too much I can do to help improve playback performance. This may be a case where iOS 7's additional overhead is just enough to cause trouble on older hardware.