-
Notifications
You must be signed in to change notification settings - Fork 19
Privacy settings
MobileMessaging SDK has several options to provide different levels of users privacy for your application. The settings are represented by PrivacySettings
class and may be accessed and modified as follows:
MobileMessaging.privacySettings.carrierInfoSendingDisabled = true
MobileMessaging.privacySettings.systemInfoSendingDisabled = true
MobileMessaging.privacySettings.applicationCodePersistingDisabled = true
MobileMessaging.privacySettings.userDataPersistingDisabled = true
-
carrierInfoSendingDisabled
: A boolean variable that indicates whether the MobileMessaging SDK will be sending the carrier information to the server. Default value isfalse
. -
systemInfoSendingDisabled
: A boolean variable that indicates whether the MobileMessaging SDK will be sending the system information such as OS version, device model, application version to the server. Default value isfalse
. -
applicationCodePersistingDisabled
: A boolean variable that indicates whether the MobileMessaging SDK will be persisting the application code locally. This feature is a convenience to maintain SDK viability in case of possible application code changes. Default value isfalse
.There might be situation when you want to switch between different Application Codes during development/testing. If you disable the Application Code persisting (value
true
), the SDK won't detect the Application Code changes, thus won't cleanup the old Application Code related data. You should manually invokeMobileMessaging.cleanUpAndStop()
prior to start otherwise the SDK would not detect the Application Code change. Another option is to useMobileMessaging.withApplicationCode(_ code: String, notificationType: MMUserNotificationType, forceCleanup: Bool)
fabric method withforceCleanup
parameter set totrue
each time you want to change your Application Code. -
userDataPersistingDisabled
: A boolean variable that indicates whether the MobileMessaging SDK will be persisting the User Data locally. Persisting user data locally gives you quick access to the data and eliminates a need to implement the persistent storage yourself. Default value isfalse
.
Feature is available since 11.0.0-rc version. Javascript is enabled for the webView for this feature to work properly, but it's possible to Disable In-app messages
If you have any questions or suggestions, feel free to send an email to [email protected] or create an issue.
- Library events
- Server errors
- Users and installations
- Messages and notifications management
- Inbox
- Geofencing service
- Privacy settings
- In-app chat
- WebRTC Calls and UI