In using Android Studio Eel, I made a new Empty Co...
# android-studio
k
In using Android Studio Eel, I made a new Empty Compose project. I was surprised at all the work it took just to get it to build. And why don’t we have the option to create kts build files yet?
Started to use catalog files and while it will compile, the editor still shows errors (even though it is correct)
i
Version catalogs have only been supported in the IDE starting in Giraffe
(and that's the same reason kts files aren't generated yet - the IDE experience still isn't there yet, even in Giraffe)
k
I’m a bit gun shy about using Beta or Canary versions as they tend to have lots of issues. I’m not really a fan of Gradle, even though I know it’s powerful. Seems like programming is getting harder and not easier
One of the reasons I’ve been really enjoying Flutter is it’s a breath of fresh air. The yaml file way of adding dependencies is so easy
c
What unexpected work did you have to do to get it to build? It should ideally not require much work at all since it is a new project template
k
Compiling right away failed. I had to change the JDK to 11 to get it to compile
c
I see. By default, Studio should be using the embedded JDK, which in Electric Eel’s case is 11. Do you have other JDKs installed on your machine?
k
Yes, I installed Azul 8 & 11
c
Are those installation locations exposed as env variables?
k
I believe I have JAVA_HOME set
c
I remember having the jdk issue and/or filing a bug. but yeah i think studio should be using the embedded jdk but it wasn't until a more recent giraffe version. @kevindmoore I'd definitely file bugs though. esp for beta and canaries, the team is pretty darn fast to respond to me in issuetracker.
k
Doesn't beta & canary require specific versions of gradle?
c
you can use stable versions of AGP which i dont believe require any specific gradle version AFAIK
but... i also typically am using latest canaries etc. AS stable is like 9 months out of date with latest intellij etc. theres so many bug fixes, and perf improvements in the latest that we just always use latest canary.
of course YMMV, but we've been using canaries for liek the last 3 years and only had major issues like twice. and the two times prevented us from using AS. its not like we somehow shipped soemthing bad because of a canary.
k
I used to have all 3 versions and would switch between them when one would have a problem
c
Yeah, i get it. if you file a bug. ill star 😄