https://kotlinlang.org logo
Join Slack
Powered by
Just want to say that I now have AGP 7.2.0 working...
# multiplatform
m
Just want to say that I now have AGP 7.2.0 working in IntelliJ and my Android code can now recognize all the MPP symbols 🙌. Thanks to everyone who worked on this 💙 android 10 K
👍 2
🎉 3
🦜 6
K 13
m
You are a lucky guy then. I cannot confirm that from my side yet.
m
It's very recent 🙂 More details at https://issuetracker.google.com/issues/165921901
m
Good news! Waiting for Android Studiio 😃
🤞 1
m
Well, I am using the exact same version of IJ. How did you configure the AGP? Isn’t a dependency on “com.android.tools.buildG7.2.1” enough?
m
I'm using 7.2.0
m
I used that before. Isn’t 7.2.1 the latest?
m
Maybe, I kind of lost track 😅
m
Probably there is just more than one issue and they have not yet fixed all of them.
m
If you have a reproducer somewhere, I can try to look into it
m
I’ll try to find one.
👍 1
@mbonnin A simple example project which shows the problem can be found here: https://github.com/mipastgt/JavaForumStuttgartTalk2022/tree/main/PolySpiralMpp I’ve also attached a screen shot which clearly shows that IJ is reporting errors on the code although the app is running nicely in the emulator.
m
Arf, Compose...
My setup is slightly different. The symbols are in other JVM modules used from the AGP one
(and no compose, not sure if that has anything to do with it...)
Can confirm same behaviour
Funny that it can find "runtime" but not "foundation" 🤔
m
I am glad that you can confirm this behaviour (and your dark theme does not make a difference 😉). So I am not alone and there is indeed still a problem and I am not seeing ghosts.
m
Yea sorry for the "false joy"...
😭 1
😁 1
It's slowly getting there though...
m
Just in case someone wants to track my issue: https://youtrack.jetbrains.com/issue/KTIJ-22296
⭐ 2
r
The project took quite a while to download all artifacts (1hr 15 min), I don't know why maven.pkg is slow. Your project works fine on my part using Intellij 2022.2 RC. Everything gets resolved, only the macOS and iOS 
platform
stuff that aren't getting resolved. Which I assume is because I'm on Windows.
The ones that don't get resolved are things that use 
platform
inside 
main.macos.kt
and 
main.uikit.kt
. Everything else seems to work fine on my part. Info about my machine:
Copy code
IntelliJ IDEA 2022.2 RC (Community Edition)
Build #IC-222.3345.90, built on July 20, 2022
Runtime version: 17.0.3+7-b469.32 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11 10.0
GC: G1 Young Generation, G1 Old Generation
Memory: 990M
Cores: 8
Registry:
    debugger.new.tool.window.layout=true
    ide.experimental.ui=true

Non-Bundled Plugins:
    wu.seal.tool.jsontokotlin (3.7.4)
    net.antelle.intellij-xcode-dark-theme (1.2.4)
    dev.polek.adbwifi (1.2.5)
    com.intellij.plugins.expui (0.4)
    org.jetbrains.plugins.hocon (2022.1.0)
    club.nutsoft.Github3Theme (1.1.9)
    Docker (222.3345.90)
    com.squareup.sqldelight (1.5.3)
    com.haulmont.jpab (2022.3.1-222)
    androidx.compose.plugins.idea (222.3345.90)

Kotlin: 222-1.7.10-release-334-IJ3345.90
v
I'm also mostly fine, I still have this one: https://youtrack.jetbrains.com/issue/KTIJ-22250/Support-dependency-propagation-for-androidjvm-source-sets-depending-on-multiplatform-libraries Dependencies aren't propagated between jvm/android modules when exposing them via api, although Sebastian has already fixed this and it's scheduled either for 2022.3 EAP or 2022.2.1 Overall it's gotten so much better though! ❤️ 2022.2 RC works really well
r
Spoke too soon. The compose dependencies are broken in 
androidMain
but weirdly only some some compose dependencies. Like 
foundation
and 
material
don't work but 
runtime
works. Also the project no longer has the issue with resolving 
commonMain
stuff as other dependencies and classes defined in 
commonMain
work as expected in 
androidMain
. This was broken in older versions of IntelliJ and AS but works in 2022.2 RC. The attached screenshot would have been broken in older versions but works fine in IJ 2022.2 RC. Might some other weird issue with the Gradle configuration.
m
The issue which I have presented above has just been fixed 🙏😀 (See comments in issue).
m
Not until next IntellJ version or so though (because requires more recent agp). But yeah looks cool 😃😃
24 Views
Open in Slack
PreviousNext
Powered by