Sorry guys, but probably I’m missing something.
AFAIK, the Linux distro is throwing the expected exception (using 2026r1.2 here):
@Javier_Menendez Hi Javier. Does your fix in 2026r2 also fix it for the v1 API GetFolderItem function?
Hi @kevin_g
We don’t tend to include specific fixes / features for API 1 or even deprecated features that have new replacements/equivalents.
As noted on the ticket, it occurs with PathModes.Shell. The documentation doesn’t suggest this exception is limited to PathModes.Native so this behavior is inconsistent.
fAppData = new FolderItem("/some/bad/path", FolderItem.PathModes.Shell)
I am unable to write cross-platform code if I have to keep making platform-specific workarounds.
I know (bad customer service IMHO but thats a different story).
Maybe I should have asked if the FolderItem Constructor and GetFolderItem use the same underlying code.
Ah, ok. That makes sense. I missed that piece of information. I reopened the issue so it can be fixed also when using the new Constructor based on the path mode. Thank you for pointing it out, @Tim_Parnell ! 
5 Likes