original_release_date started returning null

Avatar image for ykrasik
#1 Posted by ykrasik (6 posts) -

I've been using the GiantBomb API for a while. I use 2 endpoints - 'games' & 'game'. For both these endpoints, the field 'original_release_date' almost always contained the release date of the game.

I've recently noticed that for most games this field now returns null, even for games for which in the past it returned values. I can't say how long ago this started happening, but it definitely did. I have an automated test that I run every once in a while to see that my API integration is correct, and that test started failing for this reason.

It looks like for most cases I can workaround by using the 'expected_release_year', 'expected_release_month' & 'expected_release_day' fields, which return non-null values (even for games which have already been released, which is slightly confusing).

Can anyone confirm that there were api or data changes on the side of GiantBomb?

Avatar image for verbl
#2 Edited by verbl (50 posts) -

I noticed the same problem with the API: "original_release_date": null, can anyone solve this problem ?

Avatar image for dansl
#3 Posted by dansl (51 posts) -

Same Issue, looks like only thing I can pull for the "release date" is "expected_release_xxx" but "original_release_date" is null. Did something change or is this a bug?

Avatar image for frobie
#4 Posted by frobie (243 posts) -

There isn't an original_release_date field. You will need to cobble together the date using the expected_release_* fields.

The logic for the original_release_date is that it will be null if we do not have the full release date available. If we only have a partial release date, then it gets displayed via the expected_release_* fields.

There seems to be a bug in the api docs where expected_release_day is not listed as part of the games endpoint, I'll get that fixed.

Staff
Avatar image for ykrasik
#5 Posted by ykrasik (6 posts) -

Thanks for your reply. Can you please just clarify - was this field removed? I'm certain it was returning release dates before.

Avatar image for frobie
#6 Posted by frobie (243 posts) -

You may be thinking about the release endpoint which does contain a release_date field.

Staff
Avatar image for realph
#7 Posted by realph (319 posts) -

@frobie: I've noticed this has been broken in recent months too. There definitely is an `original_release_date` for the `/games` endpoint, it's right here in the API docs.

Can you please let us know when this will be fixed, because we can't guarantee the `expected_release_*` fields will be accurate. Thanks!

Avatar image for dansl
#8 Posted by dansl (51 posts) -

@frobie: I'm 100% positive that the original_release_date is broken/changed somehow. For instance BioShock https://www.giantbomb.com/api/game/17280 used to return 2007-8-21, but it now returns NULL...

Avatar image for dansl
#9 Posted by dansl (51 posts) -

Any updates to this? Should I just always assume the expected date is now the original release date? Don’t want to change my code just to end up reverting it if this gets “fixed”.

I have tested many games and the majority are not returning an Original release date using the /game endpoint. The games I tested had previously returned a date before this issue, now they just return null.

Avatar image for realph
#10 Posted by realph (319 posts) -

@frobie Is this going to get fixed anytime soon?