ccomeaux / boardgamegeek4android

BoardGameGeek application for Android (unofficial)
GNU General Public License v3.0
228 stars 47 forks source link

Using "Players" screen to rename players with 30+ plays frequently shows "UndeclaredThrowableException" in notification bar #50

Closed pvince closed 8 years ago

pvince commented 9 years ago

Not sure what other information to give for this. I am using a Nexus 5 running android 5.1 using version 5.0.2 of the app.

Steps to reproduce:

  1. Go to the Players tab
  2. Select a Player with 30+ plays
  3. Tap the "Edit" button, Modify the name, then accept the changes.
  4. Status bar will start ticking up "Uploaded Plays - Uploaded # Plays" (in reproducing for this defect, the count got up to 18)
  5. Eventually play count will stop ticking up and a notification will be displayed with the error "Uploaded Plays - java.lang.reflect.UndeclaredThrowableException"

If I wait a bit then force a complete resync of my plays a number of the players 'Plays' will still have the old name.

pvince commented 9 years ago

Uh... I just realized that at this moment https://boardgamegeek.com/ is experiencing a bit of an error:

503 Service Unavailable

Our apologies for the temporary inconvenience. The requested URL generated 503 "Service Unavailable" error due to overloading or maintenance of the server.

I wonder if this might be the cause of my problems, although, if it is, then it seems odd to me that I am even able to successfully edit any plays right now.

Or, perhaps the large number of edits with the corresponding large number of POST requests caused the BoardGameGeek server to temporarily throttle // block my IP address?

pvince commented 9 years ago

Continued attempts to bulk rename users seems to point the finger at BoardGameGeek throttling the requests and returning a 503 error after X number of requests in some Y period of time.

In my latest attempt to bulk rename users after 10 play updates, I got the notification bar exception message. When I attempt to go to BoardGameGeek in my desktop's browser, I get the 503 error.