Upgraded my app to 3.0.0-rc-1 and I keep getting this error after launching my app (minified with pr...

# ktor

[Jan]

Upgraded my app to 3.0.0-rc-1 and I keep getting this error after launching my app (minified with proguard):

kotlin.reflect.jvm.internal.KotlinReflectionInternalError: Function 'createClientPlugin' (JVM signature: createClientPlugin(Ljava/lang/String;Lkotlin/jvm/functions/Function0;Lkotlin/jvm/functions/Function1;)Lio/ktor/client/plugins/api/ClientPlugin;) not resolved in file class io.ktor.client.plugins.api.CreatePluginUtilsKt: no members found

[Jan]

Project: https://github.com/jan-tennert/EinkaufszettelNext

[Aleksei Tirman [JB]]

I get the following exception while running the :composeApp:packageRelease task:

FAILURE: Build failed with an exception.

* What went wrong:
A problem was found with the configuration of task ':composeApp:packageRelease' (type 'PackageApplication').
  - Type 'com.android.build.gradle.tasks.PackageApplication' property 'signingConfigData$gradle_core.signingConfigData.storeFile' specifies file '/home/stexe/projects/EinkaufszettelNext/einkaufszettel.keystore' which doesn't exist.
    
    Reason: An input file was expected to be present but it doesn't exist.
    
    Possible solutions:
      1. Make sure the file exists before the task is called.
      2. Make sure that the task which produces the file is declared as an input.

[Jan]

Right, forgot that's how it worked. Can you pull the latest changes and try again? I made the release build use the debug signing config now.

[Aleksei Tirman [JB]]

Now, the packageRelease task is completed successfully. What Gradle task shall I execute to reproduce the error?

[Jan]

Install the APK on an Android device and try to run it. Then I run into the Ktor error (as seen in logcat).
Not happening with the debug build, so I assume proguard

[Aleksei Tirman [JB]]

Is it possible to reproduce the error on the Android emulator?

[Jan]

Yea probably

[Jan]

Also, I just realized you probably only see an obfuscated error not showing the stacktrace, so to see the full stacktrace you might have to set

isDebuggable = true

in composeApp/build.gradle.kts at around line 126

[Aleksei Tirman [JB]]

I haven't seen the error yet

[Aleksei Tirman [JB]]

I've filed an issue (https://youtrack.jetbrains.com/issue/KTOR-7479) to address this problem

[Jan]

Thank you very much!