[DX] GAP-22: Bucket binding folderPath empty string causes misleading FolderNotFound validation error

[AlexBizon]

Summary

An empty folderPath in a bucket binding ("folderPath": "") causes a misleading "FolderNotFound" validation error in the Package Requirements screen. The error message suggests the folder doesn't exist or the user lacks access, but the real cause is that the validator cannot resolve which folder to look in.

Error (Package Requirements screen)

ValidationResult: "FolderNotFound"
"Folder might not exist or user access is restricted"

Root Cause

An empty folderPath does not default to "the process's own folder" during Package Requirements validation. The validator requires an explicit folder path to look up the bucket. After setting folderPath to "Shared/Solution Invoice App", the error changed to ValidationResult: "NotFound" (bucket not yet created in that folder) — a clearer, more actionable error.

Workaround

Always provide an explicit folderPath in bucket bindings:

{
    "resource": "bucket",
    "key": "Invoices",
    "value": {
        "name": { "defaultValue": "Invoices" },
        "folderPath": { "defaultValue": "Shared/Solution Invoice App" }  // explicit, not ""
    }
}

Suggested Fix

1. Treat empty folderPath as "same folder as the process" during validation — this is the most reasonable default behavior
2. Or emit a clearer error when folderPath is empty: "folderPath is required for bucket binding validation. Provide the folder path where the bucket will be deployed."
3. Update uipath init to document this requirement in the generated bindings.json (e.g. via a comment or README)

The current error message ("Folder might not exist or user access is restricted") sends developers down the wrong debugging path — they check folder permissions and bucket existence rather than the binding configuration.

Impact

• Severity: Medium
• Misleading error message causes wasted debugging time
• Easy to hit since uipath init generates bindings.json without any folderPath values