xxfast
08/02/2022, 11:25 PMkotlin-dsl
and the IDE seems to contradict itself when it (and the build) says that it cant this reference even when the source has it.
Unresolved reference: iosSimulatorArm64
I'm using AS Chipmunk with Kotlin 1.7.10, Gradle 7.4.2, AGP 7.2.1 on a M1 macxxfast
08/02/2022, 11:39 PMbuildSrc/build.gradle.kts
repositories {
mavenCentral()
maven("<https://kotlin.bintray.com/kotlinx>")
maven("<https://maven.pkg.jetbrains.space/public/p/compose/dev>")
}
plugins {
`kotlin-dsl`
}
build.gradle.kts
buildscript {
repositories { .. }
dependencies {
classpath(Android.buildTools) // "com.android.tools.build:gradle:7.2.1
..
classpath(Jetbrains.Kotlin.gradlePlugin) // org.jetbrains.kotlin:kotlin-gradle-plugin:1.7.10
..
}
}
xxfast
08/03/2022, 6:44 AMkotlin-dsl
with buildSrc
it has a embeddedKotlinVersion
set to 1.5.10 but cant figure out why a ./gradlew assemble
cant see iosSimulatorArm64
even from the terminal
think im gonna walk away from this for now, this build tooling is too big of a 🐉 for meJoakim Forslund
08/03/2022, 7:34 AMeygraber
08/03/2022, 2:46 PMkotlin-dsl
xxfast
08/03/2022, 11:04 PMembeddedKotlinVersion
set to 1.5.10. Then I switched to Gradle 7.5 and now i see embeddedKotlinVersion
set to 1.6.21, but i'm still seeing
Unresolved reference: iosSimulatorArm64
eygraber
08/03/2022, 11:08 PMxxfast
08/03/2022, 11:11 PMiosSimulator64
?eygraber
08/03/2022, 11:45 PMSebastian Sellmair [JB]
08/05/2022, 7:49 AMxxfast
08/06/2022, 12:46 AMxxfast
08/06/2022, 3:01 AMdev.petuska.npm.publish
) was outdated. After updating that, it finally recognised iosSimulatorArm64
Spent solid two days on trying to fix this build tooling, and here are some lessons learned
• Don't trust the IDE - always see if you can ./gradlew assemble
from terminal instead of syncing on AS. The IDE will eventually catch up but relying on it to tell you - what is wrong - is a loosing battle
• If you have a multi-platform-multi-module setup, first try to isolate the issue to a single module by unloading other modules. In my project, i had a :core
module, which is consumed by a number of :feature
modules and an :app
module on the very top that consumed the features. I started with diagnosing with just :core
and worked my way back. Wasted so much time synching forever just to realise that i forgot to update a feature module
• Always ask out for help 😅 this community has been super helpful and I would've just given up if it weren't for people volunteering to help me out. Thank you @Sebastian Sellmair [JB] @eygraber @Joakim Forslund