Urban Airship SDK keeps sending response of resetting device ID to the app

[JennyLi-VF]

cause of data privacy reasons, the Urban Airship SDK is only allowed to proceed, storage user data and sending network calls to the app, if users agreed to give consents.

We´ve found out the actual behavior as follow:

1. When the user revoked the consent and logged out, then relogin to the app, UA SDK will be deactivated.
2. If user revoked the consents and put the app in the background, every time when user opens the app from the background, UA SDK keeps sending the reset of device ID response.

The expected behavior is:

If user revoked the consents and put the app in the background, every time when user opens the app from the background, nothing should be sent to the SDK until the consents are given again.

Additionally, here is the pentest findings:

pls kindly resolve the defect and if there is any questions, let reach me out. Thanks!

[rlepinski]

Could you provide more info?

• What version of the plugin are you using?
• How are you telling Airship you are revoking consent? Integration code might be helpful here

If the SDK is disabled using privacy manager it should no-op. Once you enable a feature we do some set of operations based on that feature. If you go from some features enabled to no features enabled, you should see few requests for us to opt the user out but then the SDK should go back to the no-op state.

[alynaguibv]

Hi @rlepinski,

Please find below my answers:

• What version of the plugin are you using?

  • 15.2.6

• How are you telling Airship you are revoking consent? Integration code might be helpful here

  • await Airship.privacyManager.disableFeatures(FEATURES_ALL)

• If the SDK is disabled using privacy manager it should no-op. Once you enable a feature we do some set of operations based on that feature. If you go from some features enabled to no features enabled, you should see few requests for us to opt the user out but then the SDK should go back to the no-op state.

  • Sure and this is an expected behaviour but the thing is that the set of calls for opt the user out are triggered before the sdk get initialized (I mean before takeOff is called).

  • We still in an investigation round but any insights could be very helpful from your side.

Thanks in advance for your support

[rlepinski]

Could you gather verbose logs or provide an example that I can use to reproduce your issue?

[DaliaElhefny]

Hello @rlepinski
These are the airship logs from our app

• When airship is enabled, then we disable it: OnClosingAirshipLogs.txt
• When we open the app and airship is already disabled: OnInitializingAppWithDisabledAirship.txt