As per popular demand we are publishing Canary (edge) release of Android Studio, we decided it to be a separate package
Please allow classic confinement for android-studio-canary
As per popular demand we are publishing Canary (edge) release of Android Studio, we decided it to be a separate package
Please allow classic confinement for android-studio-canary
+1 from me, as this is identical to the existing android-studio snap, but from a newer upstream build. It’s coming from snapcrafters, so has our oversight.
It’d be nice to have an explanation as to why this separate snap model is being pursued in favour of just using edge to model Canary
The goal of canary is to enable developer to test our the newer builds without compromising their stable install of Android Studio.
Much like Microsoft have VS Code and VS Code Insiders as separate snaps.
Granting use of classic. This is now live.