FilePicker defaultFolderAbsolutePath does not work Out of context

[Ofer-Gal]

Category

[ ] Enhancement
[X] Bug
[ ] Question

Version [ 3.3.0 ]

Expected / Desired Behavior / Question

Assigning defaultFolderAbsolutePath to a folder not in the current context, should work regardless of where the webpart is running at.

Observed Behavior

Assigning defaultFolderAbsolutePath to a folder not in the current context, causes errors and shows no files.

Steps to Reproduce

if I run the webpart from https://ecgmcdev.sharepoint.com/_layouts/15/workbench.aspx
and defaultFolderAbsolutePath='https://ecgmcdev.sharepoint.com/teams/1689.006/DPCDocuments'
Shows error:
This folder is empty " and the console show

dist/node_modules/@pnp/spfx-controls-react/lib/services/FileBrowserService.js:234
[FileBrowserService.getSiteLibraryNameByInternalName]: Err='Something went wrong when executing request. Status='404''
dist/node_modules/@pnp/spfx-controls-react/lib/services/FileBrowserService.js:148
[FileBrowser._getListItems]: Something went wrong when executing request. Status='[HTTP]:404 -  [CorrelationId]:d84ef39f-d095-1000-0e66-d2dcff945c5b [Version]:16.0.0.21715'
dist/node_modules/@pnp/spfx-controls-react/lib/services/FileBrowserService.js:234
[FileBrowser._getListItems]: Something went wrong when executing request. Status='[HTTP]:404 -  [CorrelationId]:d84ef39f-10f2-1000-13fd-01686a7b6fd7 [Version]:16.0.0.21715'
dist/node_modules/@pnp/spfx-controls-react/lib/services/FileBrowserService.js:234
[FileBrowser._getListItems]: Something went wrong when executing request. Status='[HTTP]:404 -  [CorrelationId]:d94ef39f-8093-1000-13fd-05580cc2f387 [Version]:16.0.0.21715'

But if I run the webpart from https://ecgmcdev.sharepoint.com/teams/1689.006/_layouts/15/workbench.aspx
I see the files in the https://ecgmcdev.sharepoint.com/teams/1689.006/DPCDocuments library. like expected.

Thanks!

[ghost]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[AJIXuMuK]

Thank you @Ofer-Gal for reporting the issue.
It has been fixed and will be included in the next release.