"Dropbox no longer working (v1 to v2 api / v1 no longer active)"

kaymankayman MemberPosts:662Unicorn
edited June 2019 inHelp

Hi guys,

Seems like dropbox changed from v1 to v2 recently, and since then the connection is giving a error 400 return code.
有一个更新的吗een for the component or is there a workaround?

Tagged:

Answers

  • sgenzersgenzer Administrator, Moderator, Employee, RapidMiner Certified Analyst, Community Manager, Member, University Professor, PM ModeratorPosts:2,959Community Manager

    hmm I just tested it and it all worked fine.





    <宏/ >















    Maybe try creating a new connection?


    Scott

  • Thomas_OttThomas_Ott RapidMiner Certified Analyst, RapidMiner Certified Expert, MemberPosts:1,761Unicorn

    I never used the RM dropbox connector but Dropbox has been changing it's API.

  • kaymankayman MemberPosts:662Unicorn

    Nope. I actually already tried with new connection. It failed on my server giving me following :

    could not connect to Dropbox. reason {error:v1 retired}

    Then I created a new account, worked fine but when testing I got error 400.

    Looking at this page :https://blogs.dropbox.com/developers/2017/09/api-v1-shutdown-details/

    it mentions both v1 and error 400 so my wild guess is that the dropbox component uses v1 instead. No clue how you got it working but I'm not as lucky.

  • sgenzersgenzer Administrator, Moderator, Employee, RapidMiner Certified Analyst, Community Manager, Member, University Professor, PM ModeratorPosts:2,959Community Manager

    hmm interesting. I was doing it on Studio, not Server. Maybe try Studio so we can isolate?

  • kaymankayman MemberPosts:662Unicorn

    Studio shows 'could not connect blablabla, unexpected response code 400'

    So it works on neither one of them, but the returned errors are just different.

  • sgenzersgenzer Administrator, Moderator, Employee, RapidMiner Certified Analyst, Community Manager, Member, University Professor, PM ModeratorPosts:2,959Community Manager

    hello@kayman- ok I started from scratch and created a new connection, new token, etc.. It all works as expected. I know that's very frustrating to hear and I don't know what else to tell you. Perhaps firewall?

    Scott

  • kaymankayman MemberPosts:662Unicorn

    Nope, I have it on both my test server (7.5 ubuntu / open connection) as production server (7.6 ubuntu server / windows studio / proxy)

    Maybe it is a pashed roll out from Dropbox, last week it still worked for me so could also be location based.

Sign InorRegisterto comment.