>>"Connect Identifier" was checked instead of "Network Alias" (using connection Type TNS). Switching back to "Network Alias" solved the problem.
That's a known requirement - if you attempt that connection method it will require going to OCI/thick to connect.
I'll ask the developer to look at the path check logic to make sure that's taken care of. Also note, we can only check the first entry on the path, so the warning message may not apply to most users.