Some balabala

Why write an article about updating an IDE? Is not every time Google upgrade IDEbug a lot of friends crazy fun. You are too young to grasp, let me as a guinea pig to record the upgrade process and post-upgrade problems. This is a large number of screenshots, everyone after dinner when the cartoon have a look. Feel free to discuss your own problems in the comments section

Upgrade 4.0.2 => 4.2

The operating system of macOS 10.15.7 is macOS 10.15.7. Because the plug-in directory is changed in 4.1 As, plug-ins are lost or damaged. So don’t check the upgrade plugin check when upgrading, just upgrade the IDE, and then reinstall the plugin. Note the backup configuration! Note the backup configuration! Note the backup configuration!

1. checkUpdate

2. Automatically merge patches

3. After the upgrade is complete, all the plug-ins are lost, and the custom shortcut keys and other configuration of livetemplates are still in place.

4. It’s ok. I have a backup.

Changes after upgrade

1. Start icon, this aesthetic no one. Long good-looking not what use, good is the king 🐶

2. The default code font has been changed to the official recommended font. Compared with my previous (MAC delivered), it is recommended under Winsource code pro

After the upgradeBefore the upgrade

3. Version console

4. GradleDependenciesYou can see that’s good, but the originalassembleReleaseThe task is missing

5. commitCan use a separate TAB or the original way, ICONS all show c++ finally fixed, ocd saved

6. Multiple devices are supported

7. The screen recording function is back

8. IDE can be directpullRequest? The current test only supportsgithub

9. Database debug this sumX 4.1.Version no difference, other changes not found

10. Third-party library method calls can view dependencies

11. The XML editor has an app night theme switch

Bug after upgrade

1. X 4.0.All plug-ins will be lost when the version is upgraded upward. Plug-ins may not work in WIN, so you need to reinstall them

MacOS = > juejin. Cn/post / 695901…

2. GradleThe palettegradleAll orders are missing

Experimental => Do not build Gradle task XXX => Deselect the check box, and then Rebuild

3. Custom templates may not be available, it is said that the new VERSION of THE API has not been officially opened

4. The new version may generate a large number of Java processes and fail to exit after being closed

5. Because the IDE has upgraded the built-in JRE, which is not compatible with Gradle-plugin 2.x version, the project may not run the compilation

Upgrade Gradle-plugin with an IDE that supports older versions of JRE 1.8

To complement…

feeling

The overall feeling is good, there may be some bugs have not been found, can be used normally at present. It is much better than the nightmare version 4.1.x. Also, it is better to back up all configurations if you want to upgrade. If necessary, you can use dual-application mode. See you in the comments section for any other questions and I’ll add them to the bugs list.