#kelvin_error

1 messages · Page 1 of 1 (latest)

rigid deltaBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1375296589857292461

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

haughty citrus
#

Hi @lucid zealot have you consider upgrading the compose compiler?

#

Look for classpath "org.jetbrains.kotlin:compose-compiler-gradle-plugin in your build.gradle file and see if you can use a higher version?

lucid zealot
#

hi Jack, thank for the quick reply, meanwhile i'm using Kotlin version 1.8.0

#

which mean that i don't need to update "org.jetbrains.kotlin:compose-compiler-gradle-plugin" as mention right?

haughty citrus
#

I have a different understanding of the error message. I think it's telling us to use a Compose Compiler version that's compatible with kotlin 1.8.0

rigid deltaBOT
lucid zealot
#

gradlew clean throw error when trying with compose-compiler

Screenshot_2025-05-23_at_12.38.23_PM.png
#

my project gradle build set up:

buildscript {
ext {
buildToolsVersion = "34.0.0"
minSdkVersion = 21
compileSdkVersion = 34
targetSdkVersion = 34
ndkVersion = "25.1.8937393"
kotlinVersion = "1.8.0"
}
repositories {
google()
mavenCentral()
}
dependencies {
classpath("com.android.tools.build:gradle")
classpath("com.facebook.react:react-native-gradle-plugin")
classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlinVersion"
classpath 'com.google.gms:google-services:4.4.2'
classpath "org.jetbrains.kotlin:compose-compiler-gradle-plugin:1.4.0"
}
}

allprojects {
repositories {
google()
maven {
url("$rootDir/../node_modules/detox/Detox-android")
}
maven {
url("https://maven.fpregistry.io/releases")
}
maven {
url("https://www.jitpack.io")
}
}
}

apply plugin: "com.facebook.react.rootproject"

haughty citrus
#

Ah, you are using kotlin < 2.0, so you don't need to use classpath "org.jetbrains.kotlin:compose-compiler-gradle-plugin:1.4.0"

lucid zealot
#

yesye

#

yeah, then back to the original problem 🥹

haughty citrus
#

Can you add androidx.compose.compiler:compiler:1.4.0 to your app dependencies?

lucid zealot
#

let me

haughty citrus
#

If it doesn't work, change the kotlin version to 1.7.20

lucid zealot
#

try both, same issue 🥹

haughty citrus
#

what's the error after changing kotlin version to 1.7.20?

lucid zealot
#

same error:

Task :stripe_stripe-react-native:compileDebugKotlin FAILED
e: This version (1.3.2) of the Compose Compiler requires Kotlin version 1.7.20 but you appear to be using Kotlin version 1.8.0 which is not known to be compatible. Please fix your configuration (or suppressKotlinVersionCompatibilityCheck but don't say I didn't warn you!).

haughty citrus
#

Hmm, looks like your project somehow is still using kotlin 1.8.0

lucid zealot
#

i clean every single times with gradlew clean 🥹

haughty citrus
#

Can you prepare a sample react native project for me to run and reproduce the issue? I’ll send a link for you to create a support ticket, you can then share the project with stripe support, and I’d continue assisting you through emails?

rigid deltaBOT
#

Hello @lucid zealot, we have sent you a direct message, please check it at https://discord.com/channels/@me/1375341942019194925

  • 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
lucid zealot
#

we already discuss here

#

create ticket done with given link from chat bot

haughty citrus
lucid zealot
#

yes i did

#

look like it might work for Expo, no change in react-native side 🥹