#beeeeeeeeeeee2
obsidian helmBOT
Hello! We'll be with you shortly. 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.
- beeeeeeeeeeee2, 23 hours ago, 4 messages
tulip wagon
it's only related to the previous conversation in the sense that the reason i am trying to upgrade my version is because the "appearance" prop was not supported on android up until 2 weeks ago
ancient hollow
hi! generally I'd upgrade all the things to all their latest versions(like the error message mentions) like the Gradle pluigin, that's what I do anytime I change anything in a React Native project.
In any case the problem seems to come from that emoji package and it must be something else in your app that is requiring that 1.4.0 version of it(that version then requires API version 34), since Stripe does not
tulip wagon
is this package not required by the stripe package?
tulip wagon
i dont see this lib anywhere in our android/build.gradle nor app/build.gradle though. and the error goes away when downgrading stripe. do you have any idea why that might be
ancient hollow
it could be depended on transitively by some other library you use
possibly you can add something like implementation('androidx.emoji2:emoji2:1.3.0').force // Avoid using 1.4.0 since that requires targetSdkVersion 34 to your android/build.gradle, but I'm not sure
if I was facing this problem I'd probably just give up and set my app to use compileSdkVersion:34 (and then upgrade the Gradle plugin if that's needed too) really. That's not the same as the version your app targets, to be clear(it's not the minimum version of Android that your app can run on)
tulip wagon
i did try doing that but that fails with a different can of worms :/
i'll try to be explicit about the emoji lib i guess yeah. hopefully that works
ancient hollow
i did try doing that but that fails with a different can of worms :/
yeah that seems to be what mobile development is all about in my experience thusfar
tulip wagon
yeah that seems to be what mobile development is all about in my experience thus...
haha yeah, unfortunately thats been my experience as well
i think forcing 1.3.0 on our end as well might be the way to go, yeah. im getting a different error right now but its some emulator issue, I think it just crashed (the emulator not the build)
yeah forcing 1.3.0 seems to do the trick 🥳 thanks for the help @ancient hollow
ancient hollow
awesome!