Superwall.configure() doesn't complete. Getting nativePurchaseController error

[FedericoGuerri]

Hi,
I'm experiencing this issue where Superwall.configure() doesn't complete. The problem seems related/same as issue#288.

Superwall.configure() is called with:

• the right api key,
• products have been linked to playstore products
• manifest is updated with permissions and superwall activity tags (as mentioned in the sdk guide and as I've already done with other apps)
• for the parameter applicationContext I'm using my class CustomApplication (relevant code below)

@HiltAndroidApp
public class CustomApplication extends AbstractCustomApplication implements Configuration.Provider, SuperwallDelegate, Application.ActivityLifecycleCallbacks {

    @Inject
    HiltWorkerFactory workerFactory;

    @Inject
    WearDevice wearDevice;

AbstractCustomApplication extends MultiDexApplication
Configuration.Provider is from package androidx.work
Application.ActivityLifecycleCallbacks is from package android.app

If i set SuperwallOptions as:

SuperwallOptions().apply {
     logging.level = LogLevel.debug
 }

I get in logs:

💬 [!!Superwall] [receipts] DEBUG: Refreshing receipts
‼️ [!!Superwall] [nativePurchaseController] ERROR: Unable to query for purchases.
💬 [!!Superwall] [productsManager] DEBUG: Billing client connected

And of course the sdk cannot present paywall and such as it's not properly initialized:

Handling event from Delegate -> SuperwallEventInfo(event=PaywallPresentationRequest(
status=com.superwall.sdk.paywall.presentation.internal.PaywallPresentationRequestStatus$Timeout@54a4e17, reason=com.superwall.sdk.paywall.presentation.internal.PaywallPresentationRequestStatusReason$SubscriptionStatusTimeout), params={is_superwall=true, status_reason=subscription_status_timeout, 
source_event_name=after_splash, 
pipeline_type=getPresentationResult, status=timeout, 
app_session_id=ffe325a9-a597-458f-af8f-9b6f29268c17})

[linear]

SW-4151

[ianrumac]

Hi @FedericoGuerri

I've tried to reproduce this but am not able to - issues like this are usually not related to Hilt but to another dependency being created - we've resolved the issue in #288 with the customer, in their case this was fixed by removing this from their manifest:

<provider
    android:name="androidx.startup.InitializationProvider"
    android:authorities="${applicationId}.androidx-startup"
    android:multiprocess="true"
    tools:node="remove">
</provider>

One other possibility would be a library that depends on an older version of Google Play Billing, due to Google breaking compatibility between versions. Are you possibly using Play Billing or any other billing library too?