Child Item

Re: Suddenly getting "v1_retired" error

Sam80

It looks like this may be occurring again now when making requests with `grant_type=refresh_token`.

Find more posts tagged with

API

Abuse

Comments

Greg-DB

Thanks for letting us know. I'll bring this up with the team. Can you also let me know if you're seeing this on all such calls, or only a portion? If it's not all calls, can you let me know roughly what percent of these calls fail like this for you?

Sam80

Only a portion of them. They have been reported by other users of our app, from the number of reports I would estimate about 10% of calls.

Greg-DB

Thanks! I'll let you know once I have any news on this.

Andreas W.4

Hi,

I observe the same issue for about 24 hours when I refresh the access token.

Is there any news on this issue?

Thanks for the feedback!

Andreas

Greg-DB

@Andreas W.4 Thanks for the note. I don't have an update on this yet. I'll reply here once I do.

landdogger

Can confirm that I’m also getting this error intermittently. I’m using the Python SDK.

Truncated stack trace is below. The issues seems to be around refreshing access tokens.

self.refresh_access_token(scope=self._scope)
File "/home/pi/.local/share/virtualenvs/photo-gallery-jYGSq-8r/lib/python3.9/site-packages/dropbox/dropbox_client.py", line 403, in refresh_access_token
self.raise_dropbox_error_for_resp(res)
File "/home/pi/.local/share/virtualenvs/photo-gallery-jYGSq-8r/lib/python3.9/site-packages/dropbox/dropbox_client.py", line 627, in
raise_dropbox_error_for_resp
raise BadInputError(request_id, res.text)

Greg-DB

@landdogger Thanks for the information!

SirCrumpet

We're also seeing this {"error": "v1_retired"} response quite regularly.

From a few quick twitter/github issue searches it seems to be affecting quite a few users - would be great to get an update on resolution (and/or indication on https://status.dropbox.com 🙂) if possible.

Thanks!

Greg-DB

@SirCrumpet Thanks for the note. I don't have an update on this yet, but I'll follow up here once I do.

mick_bg

Let me add my voice to the chorus. It's been days and the situation is getting worse. Even without syncing, I get the error. I'm using Maestral.

Greg-DB

@mick_bg Thanks for the note. The team is looking into it. I'll follow up here once I have any news.

craigz

Chiming in as another Maestral user. This error started popping up infrequently a few weeks ago and it's been happening more and more often, especially over the past couple days. Today alone it's happening about 3-4 times per hour which is beyond frustrating.
In addition to happening periodically when I'm personally doing nothing whatsoever with Dropbox, it also occurs nearly every time I add something to my synced folder.

Greg-DB

@craigz Thanks for the information!

chaos-cloud

We are also experiencing this problem. It occurs sporadically from time to time when fetching new oauth2 access token.

Greg-DB

@chaos-cloud Thanks for the note!

jlang

Also seconding here. This is a persistent problem using the API. Please look into it ASAP.

Greg-DB

@jlang Thanks for the note. Engineering is looking into it.

eli-

Adding my voice to the sea of others – pretty desperate for this to get fixed! Thanks for looking into it, hopefully all will be working again shortly. 🙂

Greg-DB

@eli- Thanks for the message. We're working on it and I'll follow up here once I have an update.

Greg-DB

Thanks for reporting this issue. This issue is now fixed and should be working properly. Please let us know if you're still seeing any issues.

Apologies for any inconvenience this may have caused, and thanks again for bringing this to our attention.