Closed rafal-watorski closed 3 years ago
I'm not sure why BGG used response code 202 instead of simply 200 in this case. It's quite confusing, because 202 was usually used when XMLAPI/XMLAPI2 requests were accepted for processing and you needed to request the data later...
Any chance of getting a new release with this fix included? I have a new device and can't log in with this app because of this.
Good point, we could get a new release (a RC, I guess), but we would need help from @ccomeaux because I never did it before in this repository, so I'm not sure if this should happen from develop branch and how to name it.
I have they key to make sure the APK matches the previous one to allow for an upgrade instead of a new application install. That said, I've got an RC set to go, I just need to give it a test. Sorry it's taken so long, but over the last year, lots of small things no longer worked.
I will release something from the develop branch soon, but there have been so many changes that I didn't feel comfortable try to hot fix for the login.
You can also release a beta if you would like some of us to test the changes ;)
Just created a release if you wanted to give it a spin. https://github.com/ccomeaux/boardgamegeek4android/releases/tag/6.8.1
Thanks, that's got my new phone logged in!
Also works on my device!
Works on Xperia XZ1C Android 9, too! ♥ Thanks
BGG changed the login POST a little bit, so it stopped working in the app. It seems that only a small change is needed in the NetworkAuthenticator.java in
buildRequest
function."https://www.boardgamegeek.com/login"
to"https://boardgamegeek.com/login/api/v1"
application/x-www-form-urlencoded
toapplication/json