With SKIE 0.5.3, we’re starting to see this crash when building tests on iOS (I was running

./gradlew lib:iosSimulatorArm64Test

):

Task liblinkDebugTestIosSimulatorArm64

FAILED

e: Compilation failed: lateinit property declarationBuilder has not been initialized

* Source files:

* Compiler version: 1.9.10

* Output kind: PROGRAM

e: kotlin.UninitializedPropertyAccessException: lateinit property declarationBuilder has not been initialized

at co.touchlab.skie.context.MainSkieContext.getDeclarationBuilder(MainSkieContext.kt:77)

at co.touchlab.skie.context.KotlinIrPhaseContext.<init>(KotlinIrPhaseContext.kt:27)

at co.touchlab.skie.entrypoint.SkieIrGenerationExtension.generate(SkieIrGenerationExtension.kt:13)

at org.jetbrains.kotlin.backend.konan.PsiToIrKt.psiToIr$lambda$16(PsiToIr.kt:212)

at org.jetbrains.kotlin.psi2ir.Psi2IrTranslator.generateModuleFragment(Psi2IrTranslator.kt:107)

at org.jetbrains.kotlin.psi2ir.Psi2IrTranslator.generateModuleFragment$default(Psi2IrTranslator.kt:84)

at org.jetbrains.kotlin.backend.konan.PsiToIrKt.psiToIr(PsiToIr.kt:217)

at org.jetbrains.kotlin.backend.konan.driver.phases.PsiToIrKt$PsiToIrPhase$2.invoke(PsiToIr.kt:102)

[…]

It works fine with SKIE 0.5.2. Is this likely to be something that we need to fix in the Gradle config, or does this look like a bug in SKIE?

Hi! Yeah this is a bug in 0.5.3, fix will be out soon.

Thank you 🚀

Hi! Please give 0.5.5 a try.

Yep, 0.5.5 fixes the issue for us. Thank you!

@Damiano Giusti ☝️

@Samuele Perricone unfortunately this doesn’t solve my issue. @Filip Dolník I face a problem with skie 0.5.3 and it seems not to be resolved on skie 0.5.5. basically the

linkDebugFrameworkIosArm64

fails, in the error message it lists a lot of errors like these, and then prints a stacktrace. I attached everything to the snippet. I don’t have issues locally on my Mac, but when I try to build the project on a Bitrise machine with the M1 stack I get this error. I tried to clean the build cache just to be sure that the Skie version bump on the same branch didn’t cause issues. The M1 machine runs Xcode 14.3.1

Hi, this seems to be a very different problem that we have not encountered yet. Just to make sure, this problem first appeared in 0.5.3? If so, could you please try reverting back to 0.5.2, then run the task and if it works, then update to 0.5.5 and run it again. (To see if the issue is reproducible). Also, what Xcode version do you have on your local machine?

Yes, this problem first appeared in 0.5.3. I reverted to 0.5.2, builded, then upgraded to 0.5.5 and builded again, and this time it worked

Seems like it. Anyway, let us know if you run into this problem again as in that case it might be some bug in our Gradle plugin.

@Filip Dolník is it expected to see just the 0.5.3 in the releases? I saw there are 0.5.4 and 0.5.5 just as tags, but would be nice to improve the versioning convention to differentiate stable releases and other builds https://github.com/touchlab/SKIE/releases

No, that’s not expected. There should be a Github release for all versions. It’s just that deployment is automated via the tags, but creating the release (and writing release notes) is not. So it’s just that we haven’t had the time to put the release notes up yet. 😄 We follow a regular SemVer scheme. All of the mentioned versions are meant as regular releases. The 0.5.4 and 0.5.5 were released in quick succession because the 0.5.3 introduced multiple critical problems, and right when we had 0.5.4 we found another one - so the last two days were, let’s say, busy 😄

OK, sure, thanks for clarifying. I wanted just to understand the reason of a missing release and be sure to not include alpha releases

yeah, those have a suffix (for example preview, etc.). I’ll create a task to mention this in the docs.