[ANNOUNCEMENT] Dropbox node versie 2.1.0 (beta) - refresh token refactored

[Buckskin]

@BartButenaers

I have no clue. I haven't used node-fetch in my code. I see here that the dropbox (sdk) library uses @types/node-fetch as a peer dependency. But I haven't changed anything about that: the dropbox node was already using the dropbox javascript sdk library in the past.

I assume it now occurs for you because here it seems that the dropbox SDK uses node-fetch to refresh the access token (based on your refresh token).

But I don't use npm enough to troubleshoot this. Hopefully somebody else can give some tips...
Should I perhaps add the node-fetch library as a dependency to the dropbox node?

Tried npm install --save @types/node-fetch prior to npm install and copied .package-lock.json from the working version of dropbox I already had and all the error messages went away. (No problem with the user limit either)

Sorry forgot to mention - Thank you for all the work you put into this, my Dropbox Backup is now working again.

[BartButenaers]

@Buckskin

Tried that and it worked although I may have messed up somewhere else before (now shows 1 / 500).

Ok, thanks for the confirmation! Very useful feedback.
Think it is better if we also add this on the readme page.

@Buckskin

One suggestion And set the required app permissions, it would probably be worth putting in that

Yes again something for the readme page.
I had the same problem during my developments. Could save some headaches for others...

@Buckskin

Tried npm install --save @types/node-fetch prior to npm install and copied .package-lock.json from the working version of dropbox I already had and all the error messages went away.

Again thanks again for confirming this. Although I don't understand why I didn't have that error...
And not sure how to solve it: add @types/node-fetch to the package.json of the dropbox node perhaps.

[BartButenaers]

@Paul-Reed,
Thanks for separating the discussions!

This new version has been implement to solve the Github issue from @stephenn . If he can test it and confirm it works, then I consider this to be ready to be published on npm.

[Buckskin]

I have just installed the new Dropbox node on a Pi running Buster with no problems.

This instance of Node-RED is also using @TotallyInformation s alternate-node-red-installer. All that was required was to cd into the <root folder name>/data directory instead of ~/.node-red

I found that it is possible to use an access token generated when setting up an earlier Dropbox node.

Is it OK to delete the node-red-web-nodes directory once the Dropbox node has been installed?

[stephenn]

@BartButenaers

If he can test it and confirm it works, then I consider this to be ready to be published on npm.

I have only ever installed palettes from within Node Red GUI. What are the instructions to install from this different source?

[Paul-Reed]

@stephenn

What are the instructions to install from this different source?

I have posted the instructions above... [ANNOUNCEMENT] Dropbox node versie 2.1.0 (beta) - refresh token refactored - #7 by Paul-Reed

[stephenn]

Got it! I missed that in all of the technical talk. Cross your fingers!

[Paul-Reed]

@Buckskin

Is it OK to delete the node-red-web-nodes directory once the Dropbox node has been installed?

No!, that comes later when the new version is published to npm.

As @Colin has suggested;

Once it has been released to npm then

npm remove node-red-node-dropbox
npm install node-red-node-dropbox

and you can delete the node-red-web-nodes folder.

[stephenn]

SUCCESS!!!!! Great work!!!!!! Thank you!!!!!

[BartButenaers]

Thanks for testing @stephenn!
I assume you have tested it without SSL, i.e. plain http? And no localhost domain?

[stephenn]

There were the 3 redirect URLs still in Dropbox.

I don't know which one was used

[BartButenaers]

Hi @stephenn,
I don't use redirect url's anymore, because these were causing all the troubles. So if you remove them it should still work.
I was just wondering if your url (to acces your flow editor ) was http or https, when you tested this new version?

[stephenn]

It's still just HTTP and everything worked. My flow runs automatically at 1:30am on Mondays and that flow worked without my intervention again a few hours ago. Your hard work is MUCH appreciated.

[BartButenaers]

Dropbox node version 2.1.0 is now available in the palette:

Thanks to @dceejay for publishing it!

[alfakenzo]

Hi,
i cant set in firefox to prefer http so i get always arroer that client is not allowed

[BartButenaers]

Hi @alfakenzo,

• What do you mean by "cannot set in firefox to prefer http"?
• Can you explain details about how your setup works in detail (if you connect to your flow editor with http, and so on...). Otherwise we won't be able to help you.

Bart

[alfakenzo]

I try to use the function inside nodered to set the config with 2.1.1. I do every step but when i press the outh2 link i get always a error page. I got it only 1 time running with to get a refresh key. but since that no more

[Paul-Reed]

@alfakenzo

i get always a error page

You haven't given us much information about your issue....

What did the error page say? what sort or error? can you give us a screenprint?
Tell us about your system, and are you using http or https for your server

[Buckskin]

If the error is to do with This app has reached its user limit then have you tried the fix that @BartButenaers suggested. This worked for me. Check out this reply further up this topic

[ANNOUNCEMENT] Dropbox node versie 2.1.0 (beta) - refresh token refactored

I had a similar issue last week when I used the dropbox app from @Paul-Reed to test. But then I switched to my own app and the issue hasn't occured anymore. I am not using Dropbox myself so I am not a specialist. But read this somewhere: If you have created your own Dropbox app, you can only connect to it from one domain and for 1 Dropbox account. However you can increase the number of accounts/domains without applying for production by clicking on 'Enable additional users' in the App Conso…