3.5.x Desktop Upgrade to 4.2.x shows APOC compatible version as 3.5.x

[brandon]

Small bug-ish thing:

in the new Desktop, when I take a 3.5.x database, upgrade to 4.2.x, APOC is still installed as 3.5.x. The right column for plugins still shows APOC compatible version as 3.5.x instead of 4.x APOC. Neo4j 4 cant start with APOC 3.x jar in the plugins dir. Complains about missing host in settings. Not a helpful or correct warning. Deleting the 3.5. APOC jar out of the local db plugins dir was the only way to fix this issue.

[andrew_bowman]

Thanks for spotting that, can you create an issue on our github for us to track?

github.com

neo4j-devtools/neo4j-desktop

s

The Neo4j Graph Platform, on your desktop OS. . Contribute to neo4j-devtools/neo4j-desktop development by creating an account on GitHub.

[brandon]

Actually found the issue reported in 2019. Just added that its still an issue but the errors in Neo4j 4.x are different now.

github.com/neo4j-devtools/neo4j-desktop

DB Upgrade doesn't upgrade APOC which DB will fail to start

opened 05:01PM - 18 Jan 19 UTC

MichaelRBlack

When you upgrade versions of Neo4j, the APOC plugin doesn't get upgraded which will cause your database to fail to start....

Id also suggest to the neo4j core team to check the plugin compatibility early enough to log this error before the app crashes.