| Summary: | dev-util/android-studio-2023.1.1.4 is a 'canary build' (which upsets the flutter plugin) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Bill Binder <bill> |
| Component: | Current packages | Assignee: | Jason A. Donenfeld <zx2c4> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | perfinion |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge --info | ||
The latest non-canary AGP breaks reproducible builds of code, so I bumped on up to canary which has the fix. Annoying, but Google won't backport the fix to the betas. |
Created attachment 862373 [details] emerge --info Android Studio 2023.1.1.4 reports this when a flutter project is opened: Unsupported Android Studio Version Canary versions of Android Studio are not supported by the Flutter plugin. This did not happen with any previous version of Android Studio. The flutter plugin is version 73.1.1. So far, the only concrete problem I've found is that the "/opt/android-studio/jre" directory is named "jbr" these days so the flutter plugin can't find it - adding a symlink "jre" sorts that. Can we retain the latest "non-canary" ebuild in portage, and be able to see which is which.