How to handle UNKNOWN_BACKEND_ERROR - attribute_errors ?

Hey @Tim Papler! 

First, I’m a huge fan of Lake so hello 😊 

Second, I’m not exactly sure why this is being sent as a `UNKNOWN_BACKEND_ERROR` 🤔 Both IDFV and AppsflyerID aren’t allowed to be modified after set on a purchaser/customer.

Do you know how this started happening and is this happening to a handful of your users? Or is this something that was discovered through local testing? 

If it was local testing you could uninstall and reinstall the app and those subscriber attributes should no longer try to sync.

If this is happening to a bunch of users in a non-local testing environment then we’d probably need to figure out a different kind of solution 😇 

Hopefully this helps and we can get this figured out for you!

Hey @joshdholtz,

Love to hear you’re a fan 😀

We are seeing this in production. I am not sure when this started happening. But we had quite a lot of users needing to restore purchases often, at the moment my suspicion is this happens because they upgraded from version of the app without RevenueCat SDK to version with it and we try to do purchases sync and we get this error. 

Honestly at the moment I am not 100% sure this error happens only when I try to sync purchases or also when I try to get subscriber info.

We try to sync purchases when getting subscriber info for the first time (only users who upgraded app from app version without RevenueCat to version with it) and if we succeed we then get subscriber info without syncing. But if it fails well we keep trying. So I was wondering if we can safely ignore the error if `rc_successfullySynced = 1`  and try to get subscriber info?

Hey @Tim Papler!

The `$idfv` error is expected and can be ignored 😊 `$idfv` will change when a user is using multiple devices so it’s really only used for attribution integrations. This is something that RC picks up automatically but I’m not sure why the `UNKNOWN_BACKEND_ERROR` error is getting reported but I’m going to look into that.

The next thing is the `$appsflyerId` part of the error. This also shouldn’t be an error that is stopping you from continuing on but this one I think is manually set by your app. Is this also getting set by the IDFC with `UIDevice.current.identifierForVendor`? If so, that would explain this same error behavior.

Thanks!

Hello,

Yes you are correct we are setting $appsflyerId manually in the app, but we set it to the value we get from AppsFlyer SDK, but in case user has multiple devices different #appsflyerId is set for each device since it is generated by AppsFlyer SDK I can’t really tell how they generate it but I would assume they can’t match multiple devices to the same user.

Thanks for your help :)

Ok great, will ignore the errors.

Yes, please let me know when this is addressed.

Thank you very much for your support!

@Tim Papler It’s been my pleasure 😊 We’ll be in touch again when this is fixed!

Hello @joshdholtz,

I have found potential reason for this issue. Our server didn’t send the attributes to RevenueCat server so idfv and appsflyerId were not set. We are using our server to forward receipts to RevenueCat for app versions that don’t use RevenueCat SDK. I suppose when users upgraded the app to version with RevenueCat SDK included, these attributes got set and rejected by RevenueCat backend?

In my case.

This error occurred because i was not configuring App Store Server Notifications of revenuecat for both production and sandbox URL of AppStore. 

When its purchased Appstore fail to notify revenuecat i guess.

After fixing it, this error is solved.

Thanks.

When trying to fetch the offering from revenue cat [Error: There was an unknown backend error.]. I am getting this error suddenly. I even purchased some products. Suddenly I got this error. Any idea what to do?