Plugin not installable in Android Studio 2021.1.1 Patch 1 due to plugin incompatibility in META-INF

[daald]

Short description

The plugin version 0.34.1-2019.1 - the newest so far - ist not installable in Android Studio 2021.1.1 Patch 1 due to incompatibility

Expected behavior

The plugin installs smoothly and works

Version information

• IDEA Version: 2021.1.1 Patch 1
• JDK Version: 11.0.14.1
• OS Type & Version: Ubuntu 20.04.4 LTS 64bit
• Lombok Plugin Version: 0.34.1-2019.1
• Lombok Dependency Version: lombok-plugin-0.34.1-2019.1.jar

Steps to reproduce

1. Install Android Studio - in my case on my Ubuntu x64 machine it's a snap
2. Try to find the plugin in the Marketplace - not existing
3. Try to download it and install it manually -> no success because the plugin is not compatible

Working Workaround

Do what's described here: https://stackoverflow.com/a/71025235/1353930

1. Download the plugin
2. Modify the plugin.xml file in the jar
3. Install it

Sample project

Please provide a sample project that exhibits the problem.
You should also include .idea folder so we can inspect the settings.

• Sample project provided
• I am able to reproduce this error on the sample project by following the steps described above

Additional information

Here is the error message in the plugin list and the version information from Android Studio:

https://i.stack.imgur.com/qGFak.png

Stacktrace

If you are experiencing an issue and IntelliJ throws an error please provide the stacktrace.

[Dayslar]

Hello guys, I have compiled a fix for lombok and with your permission I will drop it here so that you do not have to collect it ever
lombok-plugin-0.34-2020.2-new.zip
y

[sebasira]

I'm also having this issue

[sebasira]

I've found this video that shows a workaround.

It involves unistalling the plugin, manually modifying the METAINF file and then installing the plugin from disk.

If it's actually that simple to resolve... could you please provide an official update to the plugin?

Note: I suspect that if the version checking exists in the file it has to be for a reason, and I don't know if this manual procedure could break the plugin functionality in some way