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

kaymankayman Member Posts: 662 Unicorn
edited June 2019 in Help

Hi guys,

 

Seems like dropbox changed from v1 to v2 recently, and since then the connection is giving a error 400 return code.
is there an update foreseen for the component or is there a workaround?

Answers

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

    hmm I just tested it and it all worked fine.  

     

    <?xml version="1.0" encoding="UTF-8"?><process version="7.6.001">
    <context>
    <input/>
    <output/>
    <macros/>
    </context>
    <operator activated="true" class="process" compatibility="7.6.001" expanded="true" name="Process">
    <process expanded="true">
    <operator activated="true" class="generate_data" compatibility="7.6.001" expanded="true" height="68" name="Generate Data" width="90" x="313" y="136"/>
    <operator activated="true" class="write_csv" compatibility="7.6.001" expanded="true" height="82" name="Write CSV" width="90" x="447" y="136"/>
    <operator activated="true" class="cloud_connectivity:write_dropbox" compatibility="7.5.002" expanded="true" height="68" name="Write Dropbox" width="90" x="581" y="136">
    <parameter key="connection" value="Dropbox Connection"/>
    <parameter key="file" value="/test.csv"/>
    </operator>
    <connect from_op="Generate Data" from_port="output" to_op="Write CSV" to_port="input"/>
    <connect from_op="Write CSV" from_port="file" to_op="Write Dropbox" to_port="file"/>
    <portSpacing port="source_input 1" spacing="0"/>
    <portSpacing port="sink_result 1" spacing="0"/>
    </process>
    </operator>
    </process>

    Maybe try creating a new connection?


    Scott

  • Thomas_OttThomas_Ott RapidMiner Certified Analyst, RapidMiner Certified Expert, Member Posts: 1,761 Unicorn

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

  • kaymankayman Member Posts: 662 Unicorn

    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 Moderator Posts: 2,959 Community Manager

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

  • kaymankayman Member Posts: 662 Unicorn

    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 Moderator Posts: 2,959 Community 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 Member Posts: 662 Unicorn

    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 In or Register to comment.