#niclnicl_error

1 messages ยท Page 1 of 1 (latest)

vagrant troutBOT
#

๐Ÿ‘‹ 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/1459168388503965767

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

sinful lynx
#

Sorry I just saw that some parts were't fully written out. Let me know if you need further information.

merry ridge
#

๐Ÿ‘‹ happy to help but unfortunately I'm not really familliar with Kotlin, I'm asking a colleague to take a look ๐Ÿ™‚

sinful lynx
#

Thank you Tarzan ๐Ÿ™‚

vagrant troutBOT
vital shuttle
#

๐Ÿ‘‹ Hi there! Do you still have this issue even without the Stripe dependency?

sinful lynx
#

Hi Arran,

I haven't tested without the Stripe dependency yet. The build error specifically occurs at the :stripe_stripe-react-native:compileDebugKotlin task, so it appears isolated to Stripe SDK. All other native modules (Expo Location, Camera, Notifications, Firebase, etc.) compile successfully with Kotlin 1.9.25.

I'm using Expo SDK 52 with expo-build-properties plugin to manage native dependencies. My app.config.js sets:

expo-build-properties: {
android: { kotlinVersion: "1.9.25" }
}

The Compose Compiler 1.3.2 appears to be bundled within stripe-react-native 0.54.1 itself. I don't see a way to override it via expo-build-properties.

Can I add a composeCompilerVersion override to expo-build-properties? Or does stripe-react-native need to update its bundled Compose Compiler to support Kotlin 1.9.x?

vital shuttle
#

Got it, thanks for that extra info!

sinful lynx
#

yes I saw the same thread already.

There seems to be no official solution and I'm quite frankly a bit lost. The mentioned workarounds do seem to work for other people but there is no definitive production ready solution.

#

I believe that the problem lays on stripe's side as it's composer is quite outdated

vital shuttle
#

Yeah, agreed that it seems odd. Though I'm not finding explicit references to that compiler version throughout our codebase

#

Would a Kotlin upgrade be possible for you?

sinful lynx
#

Thanks!

I'll try and will let you know.