I would recommend to continue in a thread instead ...
# jewel
l
I would recommend to continue in a thread instead of the whole channel! Let's continue here
So, maybe not correlated, but do not use
currentOs
only. This way, once you will ship the plugin, it will only have the runtime of the machine it was built on. Add all available OSs:
Copy code
implementation(compose.desktop.linux_x64)
... // ecc...
To be honest I do not really have a clue! It is possible that AS already has some
androidx.compse
symbols in its calsspath and messes up everything. To avoid this issue in Package Search, we have shadowed many packages so that they have different FQN to avoid IntelliJ classpath shenanigans. Have a look at the Gradle configuration of the PKGS plugin.
w
Ah bummer but I undertand! I tried to change some deps around thinking I could jiggle the handle but no luck. Ill take a look and see what comes out of it!
Figured it out - I was installing the
build/libs
jar instead of the zip from
distributions/
when installing in Android Studio 🙃
🦜 1