Steve M. Dropboxer

The root should be "", not "/".

The error is "malformed_path." What's the value of dest_path?

Oh, I also see /2-beta-2/ in your URL. I'm not sure whether that's still expected to work, but you should really switch to /2/. Again, the HTTP response would tell you if that's the problem. Note that /create_folder has been deprecated in favor of /create_folder_v2, so I'd recommend switching to that too:…

What's the response from the server? Does the call succeed or fail? If it's failing, the response will probably tell you what's wrong. If I had to guess, it's `Bearer'+this.accessToken. You seem to be missing a space there... try 'Bearer '+this.accessToken instead.

See https://dropbox.github.io/dropbox-sdk-dotnet/html/M_Dropbox_Api_DropboxOAuth2Helper_ProcessCodeFlowAsync.htm.

What is CRect? My best guess would be that the library you're using to make HTTP requests omits the Content-Type header when there's no POST body.

Did you mean "this does not rename"? Make sure you're uploading different content. Dropbox does not consider there to be a conflict if you upload content identical to what's already in that file, and the rename will only occur on conflict.

It appears to me that the dbox module also uses the deprecated API v1. (If this code doesn't need to work past June, that's okay to ignore.)

Actually, I made an assumption about the library you're using... but I see that you said you were using version 1.3.14, but the library I mentioned has a current version of 0.1.8. Could it be that you're using a different library?

I've redacted the access token in your previous post, but since it was visible for some time, you should really disable that access token to make sure no one else can access your account. I believe the bug is in the node-dropbox library, which is written by a third-party. This line seems…

You might want to take a look at https://github.com/dropbox/dropbox-js/blob/0af3014a14771f951d533d812001efb04bf68978/src/auth_driver/cordova.coffee. That's from the old deprecated JS SDK, but it hopefully shows the pattern for using Cordova's InAppBrowser control.

'Does it mean that every private (aka not shared) folder has it own namespace and this namespaces are in hierarchy?" No, a folder doesn't represent a new namespace unless it's a shared folder or team folder. In your example, assuming none of those folders are shared, everything is part of the same namespace.

Yes, the JavaScript SDK is actively supported.

Are you able to get other URLs to work? Are you able to share a URL that fails?

Do you see the same issue with the example app (https://github.com/dropbox/dropbox-sdk-obj-c/tree/master/Examples/DBRoulette)? How are you checking whether there's already an auth'd user? (Please share code if you can.)

I'm glad you got it sorted out! Thanks for being patient with my lack of VBA knowledge.

Try this instead? I have a suspicion that returning a String is the issue... the upload sees a string and tries to encode it as UTF-8, leading to the changes to the content making the file unusable. I don't think I've ever used VBA before, so this is code adapted from the web that I have not tested yet. Apologies if there…

Oh, sorry, I see that you already included ReadBinary. :-) Sorry!

Is "ReadBinary" something you wrote yourself? I can't seem to find a definition for it. If you could either share the code or point to the documentation, that would help. (This sort of error is typically caused by decoding or encoding the file wrong, so I wonder if ReadBinary is doing something incorrectly.)

You only need to obtain the access token once. It looks like your code echos the access token, so just copy that (or get a token by clicking the "generate token" button on the app console) and then change your code to just this: $accessToken = "<the token you obtained>"; $dbxClient = new dbx\Client($accessToken,…

Oh, it looks like things are working correctly then. A forward slash is the path separator, so the path /foo/bar/baz means a file named "baz" in a folder called "bar" within a folder called "foo". The path you're passing has six slashes, and it seems like you expect four of them to be path separators and two of them to not…

I can't reproduce the issue. Could you share your code? For reference, here is the code I used that worked successfully. (The file was in the expected location as observed on dropbox.com.) const Dropbox = require('dropbox'); const dbx = new Dropbox({ accessToken: '<REDACTED>' }); dbx.filesUpload({ path:…

Just use client instead of Dropbox.authorizedClient: client.sharing.createSharedLinkWithSettings(...)

uosuser, please create a new thread to get help with your issue, and please share the body of the 400 response. (The body should be JSON that describes the error.)

Also, you may want to drop the .withPath(") in both calls if you're just trying to search for all links.

Untested, but I believe it's just this: client.sharing().listSharedLinksBuilder() .withPath(") .withDirectOnly(true) .withCursor(resultList.getCursor()) .start(); See the documentation: https://www.dropbox.com/developers/documentation/http/documentation#sharing-list_shared_links.

You can use https://www.dropbox.com/developers/documentation/http/documentation#sharing-list_shared_links passing the path to the file. If you only want links to that exact path (and not parent folders), use direct_only=true.

Are you by chance using https://github.com/dropbox/dropbox-js? (In general, it would probably help if you told people what library you're actually using.) Assuming you are, AccountInfo is a class. You'll need an instance of that class. I think you're looking for code like this (completely untested):…

Access tokens do not take time to be active. They're active as soon as they're issued. My best guess is that you were somehow still using an old token (from a disabled app).

Are you sure that's the app you're using (that's the app key in your code, and you're using an access token for that app)? You do have a disabled app (but not the one with that app key), and it does show recent attempts to use it. Something to double-check: make sure your code is actually using the access token you've…