Skip to content

Problems with { and } characters in OneDrive paths #168

@scaccomatto75

Description

@scaccomatto75

Checks

  • I tried to fix the problem by reading the Errors.log and restarting QuickSwitch as administrator

Description without log

MS Windows 11 25H2
QuickSwitch v1.9-x64

OneDrive doesn't properly handle certain characters, such as { and }.
To make paths with these characters work, I believe it internally converts them to %7B and %7D encoding, while still displaying { and } to the user.
However, QuickSwitch doesn't read the characters { and } at the user level, but at the OneDrive level, and therefore uses %7B and %7D encoding. When trying to use a path containing them, I assume at the user level, it generates the "path does not exist" error.
I assume a reconversion function should be added for all characters OneDrive handles using % encodings.

Example:

  • existing route: C:\Users\Jbb\OneDrive\My {Path}
  • proposed route: C:\Users\Jbb\OneDrive\My %7BPath%7D

To test, simply insert { or } into the name of a folder in OneDrive and then try to make it appear in the list of folders suggested by QuickSwitch and use it.

Same problem with:

  • & --> %26
  • # ---> %23

In this case, it also interprets the folder name as the name I want to assign to the file.
If I try to save the file TestFile.txt using the path C:\Users\Jbb\OneDrive\My Test #001:

  • desired effect: C:\Users\Jbb\OneDrive\My Test #001\TestFile.txt
  • achieved effect: C:\Users\Jbb\OneDrive\My Test %23001.txt

The same thing happens if I use the "&" character in the path.

Errors log

Replace this line with the log contents.

Images

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions