Hi @ahmad-4cd8c2, thanks for reporting this! We haven’t been able to reproduce either, but we’re working on some optimizations that might help reduce the chances of this happening https://github.com/RevenueCat/purchases-android/pull/1496. In the meantime, please let us know if you’re able to repro or have access to debug logs. Also, if you have information about in what devices/android versions this is happening could be useful.

Hi @toni-rico 

The crash above happened on:

OnePlus OP516FL1 (OnePlus 10 Pro 5G)

Android 13 (SDK 33)

Also the following change is the only one I have made to my code at the last app version, can it be the reason? 

instead of checking for one active entitlement, I now check for two as the following: 

         await Purchases.setLogLevel(LogLevel.debug);
         PurchasesConfiguration configuration;
         configuration = PurchasesConfiguration("xxxxx")
           ..appUserID = userDatabase.firebaseId
           ..observerMode = false;
         await Purchases.configure(configuration);
         CustomerInfo purchaserInfo = await Purchases.getCustomerInfo();

         var isPro = purchaserInfo.entitlements.active.containsKey("Pro");
         var isProS = purchaserInfo.entitlements.active.containsKey("Pros");


         if(isProS){
           var begDate = purchaserInfo.entitlements.allt"Pros"]?.originalPurchaseDate;
           var expDate = purchaserInfo.entitlements.allt"Pros"]?.expirationDate;
           await subscribe(Pros);
           notifyListeners();
           return;
         }

         else if (isPro)  {
           var begDate = purchaserInfo.entitlements.allt"Pro"]?.originalPurchaseDate;
           var expDate = purchaserInfo.entitlements.allt"Pro"]?.expirationDate;
           await subscribe(Pro);
           notifyListeners();
           return;
         }

Before, I was only checking for one entitlement like this: 

var isPro = purchaserInfo.entitlements.active.containsKey("Pro");

Is there anything wrong I have done here? 

Im still trying to reproduce it on my machine. 

Hi @ahmad-4cd8c2, 

No, that code seems fine. That shouldn’t cause any excess memory usage or anything like that. This crash seems to have happened while creating a secondary thread for some background processing we need to do. This may happen if the app has excessive memory usage.

Is this the only crash like this or do you have other similar Out of memory exception crashes that you can share? Maybe there is something else in your app that’s using a lot of memory? 

@toni-rico 

I finally debugged it and here is the log I got: 

I/>Purchases] - INFO(27252): Purchases instance already set. Did you mean to configure two Purchases objects?
D/>Purchases] - DEBUG(27252): ℹ️ Debug logging enabled
D/bPurchases] - DEBUG(27252): ℹ️ SDK Version - 7.2.4
D/2Purchases] - DEBUG(27252): ℹ️ Package name - ***********
D/*Purchases] - DEBUG(27252): 👤 Initial App User ID - 10211***********
D/*Purchases] - DEBUG(27252): ℹ️ Purchases configured with response verification: DISABLED
D/tPurchases] - DEBUG(27252): 👤 Identifying App User ID: 10211***********
D/ Purchases] - DEBUG(27252): ℹ️ Deleting old synced subscriber attributes that don't belong to 10211***********
D/gPurchases] - DEBUG(27252): ℹ️ App foregrounded
D/:Purchases] - DEBUG(27252): ℹ️ CustomerInfo cache is stale, updating from network in foreground.
D/gPurchases] - DEBUG(27252): Retrieving customer info with policy: FETCH_CURRENT
D/fPurchases] - DEBUG(27252): ℹ️ Updating pending purchase queue
D/�Purchases] - DEBUG(27252): ℹ️ Offerings cache is stale, updating from network in foreground
D/,Purchases] - DEBUG(27252): 😻 Start Offerings update from network.
D/�Purchases] - DEBUG(27252): Request already scheduled with jitter delay, adding existing callbacks to unjittered request with key: BackgroundAwareCallbackCacheKey(cacheKey=[/subscribers/10211***********/offerings], appInBackground=false)
D/*Purchases] - DEBUG(27252): ℹ️ Updating pending purchase queue
D/2Purchases] - DEBUG(27252): ℹ️ No subscriber attributes to synchronize.
D/ Purchases] - DEBUG(27252): ℹ️ Listener set
D/ Purchases] - DEBUG(27252): ℹ️ Sending latest CustomerInfo to listener.
I/System.out(27252): (HTTPLog)-Static: isSBSettingEnabled false
I/System.out(27252): (HTTPLog)-Static: isSBSettingEnabled false
D/mPurchases] - DEBUG(27252): ℹ️ Starting connection for com.android.billingclient.api.BillingClientImpl@5057383
D/ Purchases] - DEBUG(27252): ℹ️ Ending connection for com.android.billingclient.api.BillingClientImpl@5c89da
D/cPurchases] - DEBUG(27252): Retrieving customer info with policy: CACHED_OR_FETCHED
D/(Purchases] - DEBUG(27252): ℹ️ Vending CustomerInfo from cache.
D//Purchases] - DEBUG(27252): ℹ️ Checking if cache is stale AppInBackground false

W/UPurchases] - WARN(27252): ⚠️ Unable to start a network connection due to a network configuration issue: thread interrupted


D/nPurchases] - DEBUG(27252): API request started: GET /subscribers/10211651731635640/offerings

and then Revenuecat returns cached CustomerInfo (old) where the entitlement is marked as “Active” but the expirationDate is in the past (ofc bcz it is not updated after the auto-renewal), and thats exactly what breaks my app code as the comparing: DateTime.now().isBefore(expdate) returns false…..so it keep checking with Revenuecat until a runtime error?! 

E/nPurchases] - ERROR(27252): 😿‼️ PurchasesError(code=NetworkError, underlyingErrorMessage=thread interrupted, message='Error performing request.')
E/ePurchases] - ERROR(27252): 🤖‼️ Error fetching offerings - PurchasesError(code=NetworkError, underlyingErrorMessage=thread interrupted, message='Error performing request.')
I/rPurchases] - INFO(27252): Purchases instance already set. Did you mean to configure two Purchases objects?
D/hPurchases] - DEBUG(27252): ℹ️ Debug logging enabled
D/uPurchases] - DEBUG(27252): ℹ️ SDK Version - 7.2.4
D/ePurchases] - DEBUG(27252): ℹ️ Package name - ****************
D/DPurchases] - DEBUG(27252): 👤 Initial App User ID - 1021**********
D/:Purchases] - DEBUG(27252): ℹ️ Purchases configured with response verification: DISABLED

etc.....................

Also note that, I only get this error when I launch the code at the start of the app, Only when I close the app from the background and launch it again and Programmatically trigger it. 

And I noted that if I triggered Purchases.syncPurchases() + Future.delayed(Duration(seconds: 10))

, it works normally but I can’t wait few seconds at every start of the app.

Is there anything i can do to fix it? 

Hi @ahmad-4cd8c2, I saw this log a couple of times:

I//Purchases] - INFO(27252): Purchases instance already set. Did you mean to configure two Purchases objects?

This means you’re calling `Purchases.configure` multiple times, which can have unexpected consequences. `Purchases.configure` should only be called once during the app’s lifetime. Can you try to update to remove that and see if it still happens?