get "Failed to parse the response from the flyway CLI as json." after upgrade to 7.3.5
nutmix2
Posts: 6 New member
I just "upgraded" flyway desktop from 7.2.4 to 7.3.5 and it has bricked my installation.
If I open any existing project I get "Failed to parse the response from the flyway CLI as json."
If I try to create a new project, I get "Failed to parse the response from the flyway CLI as json."
There is nothing useful in the log files (it doesnt say more about the problem json).
I cant even find any json files in the entire project structure.
I also tried repairing, uninstalling and reinstalling, same error.
If just rebooted the PC, and now I get a slightly different error when I try to open project or create a new project:
Failed to parse the response from the flyway CLI as json.: Failed to parse result 'Error occurred during initialization of VMFailed setting boot class path.' as json: Unexpected token 'E', "Error occu"... is not valid JSON
Any ideas how to fix?
Windows 10.
If I open any existing project I get "Failed to parse the response from the flyway CLI as json."
If I try to create a new project, I get "Failed to parse the response from the flyway CLI as json."
There is nothing useful in the log files (it doesnt say more about the problem json).
I cant even find any json files in the entire project structure.
I also tried repairing, uninstalling and reinstalling, same error.
If just rebooted the PC, and now I get a slightly different error when I try to open project or create a new project:
Failed to parse the response from the flyway CLI as json.: Failed to parse result 'Error occurred during initialization of VMFailed setting boot class path.' as json: Unexpected token 'E', "Error occu"... is not valid JSON
Any ideas how to fix?
Windows 10.
Tagged:
Answers
I've tried creating a project with the latest version (7.3.5) and it works for me so there is something else going on in your setup. How far did you get creating a new project before it failed ? We could use some reproduction steps.
JSON is used to communicate between the CLI and Desktop so it won't appear as a file anywhere.
The issue looks java related. I havent changed anything on my pc other than to install the new version of FW. My java version is:
I'm curious about the java version - we ship a JRE with Flyway so Flyway should use that. It's also Java 17 and not the Java 8 that you are reporting.
One thing to try is to drop to the cli within desktop (there is a button labelled 'open in console') and run and see what it does
Interestingly, if I run the command console and type "flyway info" I just get:
Flyway community edition 10.11.1