Skip to main content
Solved

Integrating with OneSignal


Forum|alt.badge.img+3

When following the ( excellent! ) documentation for the OneSignal integration, it references the old methods of getting the device ID, which don’t exist since the OneSignal migration to their new `User Centric` model.
 

OneSignal.add(self as OSSubscriptionObserver) // No longer exists

// If you've already set up OneSignal, then users should already have
// a OneSignal Id. We can check if it's available and send it to RevenueCat
if let onesignalId = OneSignal.getUserDevice()?.getUserId() { // No longer exists
    Purchases.shared.attribution.setOnesignalID(onesignalId)
}



I’d love to know what I should be setting as the attribution ID using the new methods ( they’re not covered in the migration guide ), as trying the various IDs I can find results in the web hooks failing due to missing aliases, or invalid IDs, and the device ID is no longer accessible as far as I can tell

Thanks!

Best answer by Ryan Glanz

Hi,

We recently updated this doc to reflect that we are currently only supporting OneSignal SDKs v9 (device-centric) and below.

We are actively working on supporting v11+ (user-centric) and hope to have that out soon.

View original
Did this post help you find an answer to your question?

3 replies

Ryan Glanz
RevenueCat Staff
Forum|alt.badge.img+8
  • RevenueCat Staff
  • 364 replies
  • Answer
  • December 12, 2023

Hi,

We recently updated this doc to reflect that we are currently only supporting OneSignal SDKs v9 (device-centric) and below.

We are actively working on supporting v11+ (user-centric) and hope to have that out soon.


Forum|alt.badge.img+6
  • Helper
  • 15 replies
  • January 14, 2024

Hi all, any luck we will get v11 support anytime soon? been chasing bugs for hours only to realise this was the issue 😆


Forum|alt.badge.img+3
  • New Member
  • 1 reply
  • March 11, 2024

@Ryan Glanz Any idea when this support will go into effect? Thank you!


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings