App crashes on Android when making a purchase with Kotlin Multiplatform SDK

Hi ​@Md-Atif, thanks for reporting. Sorry to hear you're experiencing crashes. Some questions:

1. Are you able to reproduce this crash locally? 
2. What is hosting your AppButtonUI? Is it an Activity, a Dialog, or some other component? 
3. Do you have a requirement to disable automatic WorkManager initialization?
   1. If not, could you try removing that snippet from your AndroidManifest.xml file?
   2. If you do, could you double check the final AndroidManifest.xml file in your app and make sure it contains com.revenuecat.purchases.kmp.di.PurchasesInitializer?

Thanks in advance!

​@JayShortway Thanks for the reply. 
1. No, I checked but I can’t reproduce it.
2. The UI is made using compose multiplatform so it’s one activity and composable functions. The button is a common composable where I am using it in all my app.​

3 No, I don’t use WorkManager in my app. First time when I got these errors so I checked the community answers and found this conversation App Crashes on Android using KMP SDK So I added these lines from this conversation.
After removing these lines following is included in final merged Manifest. 

<provider
            android:name="androidx.startup.InitializationProvider"
            android:authorities="abma.facescore.pro.androidx-startup"
            android:exported="false" >
            <meta-data
                android:name="com.revenuecat.purchases.kmp.di.PurchasesInitializer"
                android:value="androidx.startup" />
            <meta-data
                android:name="dev.jordond.connectivity.tools.ContextProviderInitializer"
                android:value="androidx.startup" />
            <meta-data
                android:name="androidx.emoji2.text.EmojiCompatInitializer"
                android:value="androidx.startup" />
            <meta-data
                android:name="androidx.lifecycle.ProcessLifecycleInitializer"
                android:value="androidx.startup" />
            <meta-data
                android:name="androidx.profileinstaller.ProfileInstallerInitializer"
                android:value="androidx.startup" />
        </provider>

​​​​​​

Is there a possibility that these error maybe due to these lines in the manifest?

        <provider
            android:name="androidx.startup.InitializationProvider"
            android:exported="false"
            android:authorities="${applicationId}.androidx-startup"
            tools:node="merge">

            <meta-data
                android:name="androidx.work.WorkManagerInitializer"
                android:value="androidx.startup"
                tools:node="remove" />

        </provider>

Hi ​@Md-Atif, thanks for answering the questions! If you don't use WorkManager, there's no need to add that snippet to your AndroidManifest.xml. Better to remove it, to completely avoid the chance of an error. 

The final AndroidManifest.xml looks good. The com.revenuecat.purchases.kmp.di.PurchasesInitializer is correctly declared. I don't expect the issue to be caused by the AndroidManifest.xml. 

Could you share the implementation of AppButtonUI?

Hello ​@JayShortway I have added 2 screen shots with 1st post. Please have a look at them

Let me share it again here 

Hi ​@Md-Atif, the screenshot shows how you're calling AppButtonUI, but I'd like to see how it's implemented. I want to understand what AppButtonUI is doing exactly, specifically with the buttonClick parameter it gets.

Here is the code

 

@Composable
fun AppButtonUI(text: String, buttonClick: () -> Unit, modifier: Modifier = Modifier) {
    Button(
        onClick = buttonClick,
        modifier = modifier
            .fillMaxWidth()
            .height(56.dp),
        colors = ButtonDefaults.buttonColors(
            containerColor = colorSoftBlue,
            disabledContainerColor = colorButtonDisable
        ),
        shape = CircleShape,
    ) {
        Text(
            text = text,
            style = plus_jakarta_sans__semi_bold_lh20_white_14,
            fontFamily = FontFamily(Font(Res.font.plus_jakarta_sans_semibold)),

            )
    }
}

Thanks for sharing that! Nothing immediate stands out. I suspect that Button is a plain Material button, nothing custom?

This crash could be caused by the app being backgrounded before the purchase() function runs. I'm not seeing any indication in the code you shared that this is the cause here, but maybe it gives you any ideas? Are you able to see the foreground/background stats for this crash in your crash reporting tool? Also, if you're using Crashlytics you might have some breadcrumbs indicating what the user was doing (e.g. whether they backgrounded the app) when the crash occurred.   

Lastly, which version of Compose are you using?

Yes it’s a plain Material3 Button. Currently I am using Compose Multiplatform 1.10.0-alpha01 and revenueCat 2.1.1+17.0.0

Here is data for the latest crash

Thanks for this! A little bit higher up on the screen you should see stats for all crashes. It contains things like which devices and Android versions it happens on, but also whether it happens in the foreground or background. Could you share that as well? 

One curious thing from the breadcrumb you shared is that the user is pressing the purchase button for the ANNUAL product, then sees the Google Play purchase sheet (ProxyBillingActivity), and while that sheet is showing they somehow select the WEEKLY product. Do you have any idea what's going on there?

Here are the states

 

About the breadcrumb data my guess is that by default the Annual is selected user clicks on the continue button then close the billing sheet and select the weekly package and after that the app crashes so I think upon Continue button click the app then crashes.

Finally it’s reproduced. Thanks for the help and support. But I am wondering who would do such fast clicks like it really needs fast clicks to reproduce it

Thanks for confirming that it reproduces on your end! I've opened a PR with a fix in the SDK. I'll make sure to release it ASAP. If you can't wait, you could try to disable the purchase button as soon as it is clicked the first time. That might be the most elegant fix either way, but of course the SDK shouldn't crash. Apologies for the trouble, and thanks for your patience! 

Sure! And thanks again for your time and support

2.1.5+17.7.0 has been released with the fix. Thanks again! 

Thanks for the support. Sure will now update it