Skip to main content
Solved

Error when marking attributes as collecting device identifiers

  • 21 July 2021
  • 1 reply
  • 254 views

Forum|alt.badge.img+1

Hey,


I’m using react-native-purchases library and found some issue in Xcode logs. Every time initialise my app is initialised I send identifiers using:

useEffect(() => {
  Purchases.collectDeviceIdentifiers()
}, [])

RevenueCat is returning error and complaining that IDFV cannot be modified. Am I doing something incorrectly? Below I’m also attaching log.

 

Thank you

 

Best answer by cody

Hey @Radek Cymborski!

This is expected behavior. Since we recognized the user's previous profile, we already had their IDFV. Your app tried to set it again, which we prevented because we try to keep advertising identifiers like IDFA and IDFV constant across installs. That way we can always pass the same identifiers to our downstream integrations whenever this specific user generates a revenue event.

If you want to clear the data for this user and try to set the IDFV for that user ID again, you can delete them from the dashboard, then re-identify with that user ID and call collectDeviceIdentifiers again. The new value will be saved, but like before, we won’t update it again if it’s already been set.

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

1 reply

cody
RevenueCat Staff
Forum|alt.badge.img+8
  • RevenueCat Staff
  • 492 replies
  • Answer
  • July 21, 2021

Hey @Radek Cymborski!

This is expected behavior. Since we recognized the user's previous profile, we already had their IDFV. Your app tried to set it again, which we prevented because we try to keep advertising identifiers like IDFA and IDFV constant across installs. That way we can always pass the same identifiers to our downstream integrations whenever this specific user generates a revenue event.

If you want to clear the data for this user and try to set the IDFV for that user ID again, you can delete them from the dashboard, then re-identify with that user ID and call collectDeviceIdentifiers again. The new value will be saved, but like before, we won’t update it again if it’s already been set.


Reply


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