Qonversion.shared.offerings not giving any callback at all.

[michaldrabik]

Hi team. So we wanted to try out your product. We have set up everything according to docs but encountering a problem when trying the most simple thing which is getting offerings.

I think this pic is fastest way to showcase it. setupQuonversion() is called after App super.onCreate()

You can observe the LogCat and notice that neither callback is being triggered.
Any ideas on how to even check what might be wrong?

Regards

[SpertsyanKM]

Hello, @michaldrabik! Do you have any offerings set up on the Qonversion dashboard?

[michaldrabik]

@SpertsyanKM Yep, all there. Also just double checked that the project key is valid. Still a no go. Basically method is called and nothing happens.

[SpertsyanKM]

I've checked your scenario and everything worked fine for our sample app. To dig deeper into your concrete case could you please contact us via the support (a chat icon at the bottom right angle of our main page), as we'll need some sensitive information about your project.

[michaldrabik]

OK, just to confirm - also played with sample app and it seemed to be working all right too for me.

[michaldrabik]

Closed accidentally

[SpertsyanKM]

For the history:

the problem was caused by the conflict with the Hilt library. It requires disabling the default initializer in Android WorkManager that in turn stops ProcessLifecycleOwner working, which is used in Qonversion SDK, including initialization.

<!-- If you want to disable android.startup completely. -->
<provider
    android:name="androidx.startup.InitializationProvider"
    android:authorities="${applicationId}.androidx-startup"
    tools:node="remove">
</provider>

That's why Qonversion initialization gets stuck and no offerings callback is executed (neither any other callbacks would).

The solution, provided by @michaldrabik :

<provider
    android:name="androidx.startup.InitializationProvider"
    android:authorities="${applicationId}.androidx-startup"
    android:exported="false"
    tools:node="merge">
    <!-- If you are using androidx.startup to initialize other components -->
    <meta-data
        android:name="androidx.work.WorkManagerInitializer"
        android:value="androidx.startup"
        tools:node="remove" />
</provider>

[astuetz]

Hey there, I'm running into the exact same problem. Our setup already does what's mentioned on the comment above (regarding androidx.startup) but still Qonversion.shared.offerings never calls any of the onSuccess or onError callbacks.

I'm actually trying to get the offerings inside a WorkManager CoroutineWorker. The app was fully terminated before the worker is called, but I can see that our Application gets created and also initializes Qonversion before Qonversion.shared.offerings is called.

If the Worker runs while the app is active (e.g. in foreground), everything works as expected.

edit: mentioning @SpertsyanKM directly so this will hopefully get seen, I didn't want to open another Issue as it's the same problem (but probably different cause)

Any ideas on what could cause this?
Thanks!

[SpertsyanKM]

Hello, @astuetz. Is it possible to provide a kind of minimal reproducible example of the issue? The mentioned kind of problem needs step-by-step reproduction to be able to find any issues in code, so the example would be very appreciated.

You can send it directly to my email - kamo@qonversion.io.

[astuetz]

Hi @SpertsyanKM, I uploaded a minimal sample project on GitHub:
https://github.com/astuetz/qonversion-workmanager-sample

See the readme for steps to reproduce. Our use case for getting the offerings inside a Worker would be to show a notification to the user including some price info.