Child Item

Upgraded Team Account - breaking shared links using JS SDK

We recently upgraded to a Team account and are experiencing an issue with an automation that previously worked as expected. The automation uploads a file and then immediately generates a shared link using the Dropbox JavaScript SDK’s sharingCreateSharedLink() method.

Since the upgrade, the shared links now show this error when accessed:

"Content Is Uploading"
"Link content can't be viewed because it hasn't finished uploading. You'll be able to view it once it completes."

However, when accessing the file via the shared link, the file is already fully uploaded and visible in the correct folder.

We are passing the pending_upload parameter with the value { ".tag": "file" } in the sharingCreateSharedLink call, as noted in the documentation. The API token has all necessary team permissions.

Has anyone else experienced this issue? Any help would be appreciated!

Find more posts tagged with

Accepted answers

DB-Des

Hi @bbergeron

The method 'sharingCreateSharedLink()' uses a deprecated endpoint. To avoid any further errors or unexpected behavior, we would recommend migrating to using the latest endpoint /2/sharing/create_shared_link_with_settings — the corresponding method in the Node SDK would be: 'sharingCreateSharedLinkWithSettings()'.

All comments

DB-Des

Hi @bbergeron

I'll be happy to help with any issues you're having with the Dropbox API, but I'll need some more information. Please reply with:

the steps to reproduce the issue, including relevant code snippet(s), but don't include any access or refresh token(s)
the full text of any error or unexpected output
5-10 different 'X-Dropbox-Request-Id' response header values encountering the issue

bbergeron

Here are some relevant code snippets:

const response = await dbx.filesUpload({
path: uploadPath,
contents: fileContent,
mode: { ".tag": "add" },
autorename: true,
mute: true,
});

const response = await dbx.sharingCreateSharedLink({
path: uploadPath,
pending_upload: { ".tag": "file" },
});

And here are 5 sets of request ids that correspond to the above response objects:

'x-dropbox-request-id': [ '9626cda55daa4dc6b07e18cf8b418903' ] (filesUpload())
'x-dropbox-request-id': [ 'dfd9b0c6f95744ce9cde046e79d2f5e3' ] (sharingCreateSharedLink())

'x-dropbox-request-id': [ 'aec437fd23914fc39b57a24d88a3d590' ]
'x-dropbox-request-id': [ '94da0146663b42db9355838e6687fdb1' ]

'x-dropbox-request-id': [ '983df16d9eed4cd58027349c6279a761' ]
'x-dropbox-request-id': [ '5bb1d34583c343d0a5c28048422b6577' ]

'x-dropbox-request-id': [ '0beb708036e64f6fbf0779a9a8bea509' ]
'x-dropbox-request-id': [ '100ab664418e45929917a725f43d7e97' ]

'x-dropbox-request-id': [ '53970f590c8d4a4c91350b50ec726c78' ]
'x-dropbox-request-id': [ 'f029eefd6aac4dd39f83ff16a1736f1e' ]

DB-Des

Hi @bbergeron

bbergeron

Thanks for the info, we moved to using the sharingCreateSharedLinkWithSettings() method and that solved our issue.

Brandon