Check the docs before asking a question: https://abp.io/docs/latest: yes
- Exception message and full stack trace:
System.UriFormatException: Invalid URI: The URI is empty. at void Uri.CreateThis(string uri, bool dontEscape, UriKind uriKind, in UriCreationOptions creationOptions) at async Task<string> Volo.Abp.Studio.UI.Services.FilePicker.PickSingleFileAsync(Action<FileDialogOptions> configAction) at async Task Volo.Abp.Studio.UI.Commands.OpenSolutionCommandFactory.G38j5j4X3q()
- Steps to reproduce the issue:
1 Open Studio 2 Click "Open Solution"
(New solution opens dialog)
12 Answer(s)
-
0
- The error
System.UriFormatException: Invalid URI: The URI is empty.occurs when ABP Studio attempts to open a file dialog but receives an empty or invalid path/URI. This is not directly related toabp-dynamic-formor dynamic forms in ABP, but rather to the file picker functionality in ABP Studio.
How to resolve:
- Ensure you are using the latest version of ABP Studio, as file dialog issues may be fixed in recent releases.
- When clicking "Open Solution," make sure the dialog is not being blocked by your OS or any security software.
- If the dialog does not appear or fails immediately, try restarting ABP Studio or your computer.
- If the problem persists, check for any custom configuration or environment variables that might affect file dialogs.
For more on dynamic forms in ABP, see the official documentation:
- https://abp.io/docs/latest/framework/ui/mvc-razor-pages/tag-helpers/dynamic-forms
If the issue is specific to ABP Studio's file dialog, it may be a bug. In that case, report it on the ABP GitHub issues page with your OS details and ABP Studio version.
Sources:
- https://abp.io/docs/latest/framework/ui/mvc-razor-pages/tag-helpers/dynamic-forms
This response was generated by AI. If it didn’t solve your problem, feel free to post a new answer — our support team will jump in to help you soon.
- The error
-
0
I've restarted the computer and Studio many times. Studio is updated.
-
0
Hello, does the problem occur only in a specific solution, or are you also unable to open newly created solutions afterward?
-
0
I can open the solutions if they are in the "recent panel".. its if i go to the naked "open solution" button next to 'new solution' button. Either on the welcome screen or from the toolbar.
i just realized i could get to one project via recent.. but not as described.
i've snooped around the Studio json files ( i have it saved in my finder from all my troubles before costing me months of delays ) so i was able to find it.. but i can't quite figure out what to remove/clear this time.
i did do some path renaming recently.
or maybe something in Suite is bugging it. hard to say.
-
0
-
0
oh yeah.. no problem. it's kinda an odd one. i'll schedule the meeting.
I will note I did try clearing the appsettings.json to see if that helped.. but it didn't . was considering a reinstall but simply didn't get that far yet before reporting it.
-
0
In the meantime, you can try deleting the **.abpsln, **.abpmdl, and **.abppkg files in the project and reinitializing the project from the toolbar. Just remember to back up your project before doing so.
-
0
Okay but that would be doing so in over 7 or 8 solutions as i've been trying to test differences in CRMkit on Blazor (? see other ticket) so i have other solutions.
So if you're saying an offending solution is in Studio's way -- then there is something offensive in Studio's file-open code; that is far-too-dependent on what the user may-or-may-not of done with file and folder organization.
-
0
Thank you for your feedback.
Actually, this behavior is the result of a design decision. ABP Studio relies on certain conventions and file/folder structures when opening a solution. This may feel strict, but it allows Studio to provide a consistent and automated experience across different setups.
We can think of it like how project references work in
.csprojfiles. You can add a reference to another project, but if the file path is incorrect or that project is later moved or renamed, the build will fail. Similarly, Studio needs to resolve some paths and metadata correctly to function as expected — otherwise, it may not behave reliably.That said, your feedback is valid, and we’ll consider how we can improve Studio’s resilience in future versions.
-
0
Yeah.. gonna need a try/catch inside that folder-file parsing loop, then . Because I certainly changed the pathnames and filenames of a SLN due to the fact it was IMMENSELY large -- and which of those 20 test slns they are i don't know. . but i could move them all out of the way if thats a test. But remember: you can't control your end-users; be pessimistic. ;-)
Do you need to see my system with this information tho? I think we found the common cause. You've described the dependence on structure and internals pre-opening. I've described i've mucked with a structure/sln for brevity. Yet, that shouldn't stop an end user from ever opening any other solution ever again.
I'm going on holiday an back the 18. If we really need my system to inspect I'm 100% here to help!
Best.
-
0
Hurm. I finished the work i was doing and was able to move the entire folder of slns out of the folder they were in and to the deskop.
in opening the app, Recents panel cleared out --- but i still cant utilize the Open dialogs. Odd. Not the expected result admittedly.
-
0
Thanks for the follow-up — and enjoy your holiday!
You're right, we can't control how users organize their files, and your case clearly highlights that. We'll look into making this part more fault-tolerant, as you suggested. For now, no need to inspect your system — your explanation is already very helpful.
Thanks again!
