The regulatory authority requires that apps not call related sensitive APIs until users click the Agree button in the privacy agreement pop-up box. For this reason, this requirement is supported by all versions of mPaaS Android 10.1.68 baseline, 10.1.60.5 or later versions of 10.1.60 baseline, and 10.1.32.16 or later versions of 10.1.32 baseline. Please update the project as the case may be by referring to this document.
You need to enable the Privacy & Security Controls window in the app, and call the API of the framework to send the Agree broadcast after the user clicks the Agree button. After receiving the broadcast, the framework is initialized and also records the agree behavior of the user in the
sharedpreference. You will be notified of the completion of the initialization through callback. You will be unable to use the capabilities of mPaaS components properly until you receive a callback.
meta-data, set the switch for the pop-up dialog box for Privacy & Security Controls. By default, the switch is off.
Use the following API to send the Agree broadcast.
Note: The broadcast can be sent only when the user clicks the Agree button.
Whether the user has agreed the privacy agreement.
Update the flag indicating the user’s consent to the privacy agreement, allowing you to pop up this window again in a particular scenario.
QuinoxlessPrivacyUtil.setUserAgreedState(Context context, **boolean **agreed);
Callback after the framework is initialized:
QuinoxApplicationis used: The capabilities of mPaaS must be used after
Note: You must use ‘QuinoxApplication’ if you need to use the hot fix function.
QuinoxApplicationis not used: The capabilities of mPassS must be used after
QuinoxlessFramework.setup(this, new IInitCallback()
public void onPostInit()