Repeated syncs and calls to applicationDidBecomeActive with TV off about purchases-ios HOT 3 CLOSED

Hey there, thanks for reporting! This has also been reported in Stack Overflow, , but it's nice to track it here as well. Answer from SO:

This is caused by a bug in purchases-ios, present in versions 3.1.0 -> 3.2.2, where the log gets issued even though the method no-ops, if there aren't any subscriber attributes that need to sync (which will be your case unless they're being set to different values very often).

It will be fixed in the next release, 3.2.3, coming out this week (along with other fixes).

What's happening is that RevenueCat attempts to sync Subscriber Attributes (https://docs.revenuecat.com/docs/subscriber-attributes) whenever the app is foregrounded or backgrounded. An app is considered foregrounded/backgrounded on tvOS when UIApplicationDidBecomeActiveNotification or UIApplicationWillResignActiveNotification get fired. If there are no attributes that need syncing, the method early exits, but the current version still issues the log saying that they've synced successfully.

I'm not quite sure why tvOS is firing those two notifications while the TV is off, but I'll dig in a bit more and let you know.

To clarify again, though, the method won't do anything unless new Subscriber Attributes have been set in between foregrounding or backgrounding, or unless they've been set to different values than the current ones.

I'll update the ticket once the fix gets released.

from purchases-ios.

it looks like UIApplicationDidBecomeActiveNotification and UIApplicationWillResignActiveNotification behave a little oddly on tvOS:

https://stackoverflow.com/questions/35573349/apple-tv-application-does-not-resign-active-on-sleep-mode

So that's the reason that the method is getting called. Like I mentioned before, the method doesn't actually do anything, and the log will be fixed by the next release.

from purchases-ios.

version 3.3.0 is out, and it shouldn't have these extra logs (although UIApplicationDidBecomeActiveNotification and UIApplicationWillResignActiveNotification behavior is out of our control, so you will likely still see the didbecomeactive message).
Closing this out for now

from purchases-ios.