Skip to main content

Hi, recently in one of our apps the integration between  RevenueCat and OneSignal is failing, im aware of the changes in the API as stated here 

https://www.revenuecat.com/docs/integrations/third-party-integrations/onesignal#11-user-centric-api-versions-of-onesignal-110-and-above

we have two types of problems first of all some of the request send empty bodies and some others return 

{"errors":s{"title":"No subscription with alias 

We have this integration working in two apps with exactly the same implementation, one is working fine and the other is always failing.

as of today which type should we use with flutter and why one is failing?

Here is a little snippet of the integration:

      final oneSignalUserId = OneSignal.User.pushSubscription.id;

OneSignal.login(revenueCatUserId);
OneSignal.User.addAliases(<String, dynamic>{
'revenuecat_id': revenueCatUserId,
});

await _corePurchases.setOneSignalId(oneSignalUserId!)

Thanks.

Hi @apernas, thanks for posting this. Would you mind opening a support ticket, so we can review our logs for your app? Also, in the support ticket, could you please send the following:

 

  • A larger snippet of your implementation for the app that isn’t working
  • A snippet of your implementation for the app that is working
  • Versions of the Flutter SDK, RevenueCat Flutter SDK, and OneSignal Flutter SDKs you’re using in both apps

We’ll be happy to dig deeper into this. Thanks!


Hi @jeffrey_bunn thank you for your time, it seems for the moment that this is caused by a OneSignal database cleaning, revenue cat does not know and it sends events to users that do not exist anymore.

i don`t know if this is a use case that you know of or if there is any way to control this or to make RC webhook know this.

Thank you for looking into this.

Regards,


Reply