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

**URL:** https://discourse.nodered.org/t/announcement-dropbox-node-versie-2-1-0-beta-refresh-token-refactored/73312
**Category:** Developing Nodes
**Created:** [6 January 2023 22:05 UTC](https://discourse.nodered.org/t/announcement-dropbox-node-versie-2-1-0-beta-refresh-token-refactored/73312 "2023-01-06T22:05:50Z")
**Posts on this page:** 1
**Showing post:** 18

<div class="post-metadata">

### Author: ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [7 January 2023 22:52 UTC](https://discourse.nodered.org/t/announcement-dropbox-node-versie-2-1-0-beta-refresh-token-refactored/73312/18 "2023-01-07T22:52:35Z")

</div>

> [@Buckskin](#):
>
> `This app has reached its user limit.`

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 Console ([Login - Dropbox](https://www.dropbox.com/developers/apps))._

I suspect this was my problem: Paul had accessed his test dropbox account via domain A (e.g. https;[//domain.from.paul](https://domain.from.paul)) and I wanted to access the same dropbox account via domain B (e.g. [https://domain.from.bart](https://domain.from.bart)). Which seems not to be allowed. Did you do anything similar in your test?

The setting looks like this in my own Dropbox account, so I assume I can also use it only via one domain:

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/4/1/419f64f27bda00c47bc23141ca5a838f88ea3096.png)

> [@Buckskin](#):
>
> Tried on Pi and got
> 
> ```auto
> npm WARN dropbox@10.34.0 requires a peer of @types/node-fetch@^2.5.7 but none is installed. You must install peer dependencies yourself.
> 
> ```

I have no clue. I haven't used node-fetch in my code. I see [here](https://github.com/dropbox/dropbox-sdk-js/blob/main/package.json#L108) 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](https://github.com/dropbox/dropbox-sdk-js/blob/master/src/auth.js#L323) 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?

---

_[View the full topic](https://discourse.nodered.org/t/announcement-dropbox-node-versie-2-1-0-beta-refresh-token-refactored/73312)._