Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/v2/account/wallet -- gems totally broken #274

Closed
lye opened this issue Mar 29, 2016 · 3 comments
Closed

/v2/account/wallet -- gems totally broken #274

lye opened this issue Mar 29, 2016 · 3 comments
Labels

Comments

@lye
Copy link
Contributor

lye commented Mar 29, 2016

We moved where gem quantities live and the backend component that services API requests wasn't updated.

Whoops.

@Archomeda
Copy link
Contributor

Archomeda commented Oct 22, 2016

(keeping this up-to-date)

Recently it has been fixed for most people apparently (ref 1) (ref 2).

But mine are still inaccurate (ref). And it's unknown why (ref).
At the time of writing, my gems should be at 800. But the API still says 1028, which was the amount I had a long time ago (probably at the end of 2015 - beginning of 2016).

As of today (2 Nov) the API now shows my 800 gems correctly. Hopefully it stays up-to-date 🎉

@queicherius
Copy link
Contributor

Someone just wrote me with another report of this issue, so either it's still broken or it broke again. 😢

@tivac
Copy link
Contributor

tivac commented Nov 20, 2016

It's probably a caching thing given @Archomeda's experience. This original issue is resolved, at least. Further issues should be opened up on a case-by-case basis.

@tivac tivac closed this as completed Nov 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants