Child Item

Not able to access the folders inside scoped app folder

There is a scoped app folder , and Im trying to access a zip file in a folder called "myfolder" in the Apps folder . In the script , I gave the dropbox path as /Apps/myfolder/download.zip , however while Im running the script it says :

Invoke-RestMethod : {"error_summary": "path/not_found/...", "error": {".tag": "path", "path": {".tag": "not_found"}}}

The app has read and write access . Why does this error occur . Also this app is created by another person and has been shared .

Find more posts tagged with

API

Abuse

Comments

Здравко

Hi @nive,

Too few info has been provided for direct answer. First of all, what type of access your application has, "App folder" or "Full Dropbox"? You gave the path where you put the zip file, but what exactly you have passed to as argument? Provide something more complete as a example - what's executing (including all params), and the result. Mask confidential things like access tokens, everything else left as is.

Take in mind that if you have selected "App folder", application name is important too.

PS: If I have to bet, you made 2 mistakes. 1 - file placed on inaccessible for the application place, 2 - ignoring path change as result of path rooting for path in application folder. Of course, just a guess. Let's see...

nive

@Здравко

My teammate has created a "App folder" and the app name is "CISCAT" . The app has been shared and also access tokens are generated .

There is a folder inside /Apps called "CIS_CAT" that I need to access . This is the powershell code Im using to access the /Apps folder .

$dropboxToken = $response.access_token
$dropboxFilePath = "/Apps/CIS_CAT/CIS-CAT-Assessor-windows-GUI-jre-v4.30.0.zip"
$localDestination = "\\CIS-CAT\CIS-CAT-Assessor-windows-GUI-jre-v4.30.0.zip" # shared drive
# Construct the Dropbox API request URL
$apiUrl = "https://content.dropboxapi.com/2/files/download"
# Set the headers for the API request
$headers = @{
Authorization = "Bearer $dropboxToken"
"Dropbox-API-Arg" = '{"path":"' + $dropboxFilePath + '"}'
}
# Make the API request to download the file
Invoke-RestMethod -Uri $apiUrl -Headers $headers -OutFile $localDestination

I get the error as "path not found" . Should the Apps folder and its contents be shared too ?

Здравко

Hi again @nive,

You give different values for the path in Dropbox: In your first post "/Apps/myfolder/download.zip", but in second - "/Apps/CIS_CAT/CIS-CAT-Assessor-windows-GUI-jre-v4.30.0.zip"! This is important since you application name is "CISCAT", it can see only folder "/Apps/CIS_CAT/", as a root, and its content, but nothing outside. One note here: either application name missing one underbar or in the folder name is one more underbar! 🧐 I will suppose typing error. So, your application can never see a folder like "/Apps/myfolder/" or any of the folder content! Take this in mind. Here I'm not sure if my first bet above (inaccessible place) is correct; I will let you to decide.

Further since your application have access to "App folder" only, it appears to be the root of the accessible namespace! As a result you have to strip out from your path any leading part that contains the application folder itself - something you haven't done. Following this rule, the following line:

$dropboxFilePath = "/Apps/CIS_CAT/CIS-CAT-Assessor-windows-GUI-jre-v4.30.0.zip"

... should look something like:

$dropboxFilePath = "/CIS-CAT-Assessor-windows-GUI-jre-v4.30.0.zip"

i.e. stripped "/Apps/CIS_CAT" your application specific folder that appears as root from your application view point. You can think as this folder is automatically prepend to specified path. That's why with your code you're trying to download a file like "/Apps/CIS_CAT/Apps/CIS_CAT/CIS-CAT-Assessor-windows-GUI-jre-v4.30.0.zip", that of course doesn't exist. That's where the error comes from. 😀 The second bet confirmed true. 😉

Hope this helps.

Add: Take in mind that access tokens are short lived. For long term access, if you need such, consider refresh token usage.

nive

Hello @Здравко @Здравко

Correct me if I'm wrong , So the app name "CISCAT" and the folder name inside /Apps should be the same ? Asking so , because the folder name is CIS_CAT( with an underscore) . And thank you for the path correction , Ill try that .

Also when I try to create "App folder" or "full dropbox" in my dropbox account , I dont see the Apps folder getting created . is there any reason that Im not able to see it in my account ?

Thank you for your response .

Здравко

@nive wrote:
Hello @Здравко @Здравко
Correct me if I'm wrong , So the app name "CISCAT" and the folder name inside /Apps should be the same ? Asking so , because the folder name is CIS_CAT( with an underscore) . And thank you for the path correction , Ill try that .
...

Hm...🤔 Yes and no. In general that's the rule. As can be seen in Dropbox documentation:

App folder
A dedicated folder named after your app is created within the Apps folder of a user's Dropbox. ...

So, Yes, when created such a folder should have the same name as the application name.

On other side the application name can change and that change is not retroactive. Also the user can change any shared folder name (app folder behave like a shared folder between the user and the application) without this change affect any other peer. So, No, in spite typically the same, in some corner cases, the name can be different without issue.

In all cases you have to make sure the particular folder belong to your application if there's any doubts. An easy way is just upload a dummy file in you application namespace root and see where this file will bring up. Another way is to list the content of your application namespace root and see what's the result matching to.

@nive wrote:
...
Also when I try to create "App folder" or "full dropbox" in my dropbox account , I dont see the Apps folder getting created . is there any reason that Im not able to see it in my account ?
...

First, take in mind that when your application has "Full Dropbox" access, nothing is created automatic. Application' root and account' root coincide. So, you cannot expect something to be created automatically, without your application's explicit action.

As mentioned already, when "App Folder" is in use, application' root doesn't match to account' root (or user' home). That's why a folder, responsible for mounting application' root, gets created on application link to particular account. By default this mount point has the form "/Apps/<YOU APP NAME>", where "<YOU APP NAME>" is your application name at link moment.

I don't know if you noticed, I mentioned just before, that app folder "gets created on application link to particular account", not on application creation (as is in your question)! Doesn't matter that the application is created in your account context, it's not linked to there automatic! You have to link it there the same as you may link it to any other account if that's what confuses you. Did you link your application to your account? 🧐😉

Hope this sheds additional light.

DB-Des

Hi there!

In addition to the information that Здравко has provided, I would recommend ensuring your app is an app with "App folder" access and not "Full Dropbox" access.

You can confirm this in the developer account's App Console. The app should have "Permission type: App folder".

nive

Hello @Здравко

Thank you so much for your solution . I fixed the issue . I greatly appreciate your quick help 🙂

nive

Hello @DB-Des ,

Thank you for looking into it . I was able to fix it .

karver

can you tell me how you fixed the issue, i am facing the same problem

karver

i need to download zip file from dropbox

this is the error i am receiving :

Invoke-RestMethod : {"error_summary": "path/not_found/...", "error": {".tag": "path", "path": {".tag": "not_found"}}}

My script looks like this

function Get-DropboxFolder{

[CmdletBinding()]

Param(

[string]$DropboxFolder,

[string]$OutputFolder,

[string]$FolderPath

)

$body = '{"path":"/'+$DropboxFolder+'"}'

Write-Output $body

$AuthToken = 'xxxxxxxx'

$token = "Bearer $AuthToken"

#The file will be downloaded as ZIP to the Temp folder of the user

$Tempfolder = "$env:temp\Downloaded_File.zip"

if (!(Test-Path $FolderPath)) {

Write-Verbose "Downloading the folder…"

Invoke-RestMethod `

-Method POST `

-Uri "https://content.dropboxapi.com/2/files/download" `

-Headers { "Authorization" = $token; "Dropbox-API-Arg" = $body} `

-OutFile $Tempfolder -ContentType ""

#The file will be extracted and then removed from the temp

write-verbose "Extracting the folder…"

Expand-Archive -LiteralPath $Tempfolder -DestinationPath $OutputFolder -Force

Remove-Item $Tempfolder -Force

Write-Verbose "The folder has been downloaded."

}

else{

Write-Verbose "Folder Exists"

}

$DropboxFolder = "Apps/WAE-DE-dev-win11/file.zip"

$OutputFolder = "$env:HOMEDRIVE\Softwares"

$FolderPath = "$OutputFolder\Software01"

Get-DropboxFolder -DropboxFolder $DropboxFolder -OutputFolder $OutputFolder -FolderPath $FolderPath -Verbose

Greg-DB

@karver Apps with the "app folder" access type can only access the contents of the special app folder that gets automatically created for it. If your app has the "app folder" access type, then it will only be able to access files in the app folder, and the root for any path value supplied by that app will automatically be the app folder root. You can find more information on app permissions here. For example, If your app has the app folder access type and you're trying to access something you can see on the Dropbox web site at "/Apps/<app folder name>/folder/example.csv", you should only send the path value as "/folder/example.csv".

So in your case, instead of this line:

$DropboxFolder    = "Apps/WAE-DE-dev-win11/file.zip"

try it like this:

$DropboxFolder    = "file.zip"

Здравко

Hi @karver,

You have 2 errors, at least. The first one is obvious - you have pointed something that doesn't exist (likely it's the same as explained before; not mandatory, of course). The other one is the fact that you're trying to download folder content using method suitable for files only! To be able download a folder as zip file take a look on /2/files/download_zip. 😉

Hope this gives direction.