[FilePicker]Files keep loading when previewing all files in OneDrive.

[wangliantaoTTT]

Category
[]Enhancement

[x] Bug

[]Question

Version
Please specify what version of the library you are using:
3.21.0

Expected / Desired Behavior / Question
When using the FilePicker control from @pnp/spfx-controls-react, users should be able to browse and select files from OneDrive normally. The OneDrive tab should load and display the user's files or folders for selection.

Observed Behavior
All other tabs in the FilePicker — such as Recent, Site, and Upload — work as expected and load properly.
When switching to the OneDrive tab in the FilePicker, it shows a loading spinner indefinitely and never displays the files.
Meanwhile, no error is thrown in the UI, but a backend call fails with the following response:

{
"error": {
"code": "-2147024894, System.IO.FileNotFoundException",
"message": "ファイルが見つかりません。" // File not found
}
}

Add the FilePicker control to a custom SPFx property pane or component.

Ensure OneDrive tab is visible (hideOneDriveTab: false).

Click on the OneDrive tab.

Observe that it stays stuck in loading and never shows any file list.

[github-actions]

Thank you for submitting your first issue to this project.

[wangliantaoTTT]

This is the code I used

[wangliantaoTTT]

I think I’ve found the root cause of the issue.
If the system language is set to Japanese, the Title retrieved for the OneDrive library becomes a Japanese string (e.g. "ドキュメント").
As a result, the constructed URL includes this localized name, leading to a broken path.
However, the correct folder path suffix should always be "Documents" regardless of the system language.

Use EntityTypeName instead of Title when building REST API URLs to avoid issues on non-English systems.

[NishkalankBezawada]

Hello @wangliantaoTTT,

I was able to replicate the issue, and will soon come-up with the solution for the same.

@joelfmrodrigues and @michaelmaillot can you assign this to me.

Thanks,
Nish

[michaelmaillot]

Hello,

Thanks @wangliantaoTTT for raising this and thanks @NishkalankBezawada for working on it!