MarketingCloudSDK iOS (v8.1.2)

• Home
• Documentation
• AppleDoc
• MobilePush
• Get Started
• Overview
• 1. Provision for Push
• 2. Setup MobilePush Apps
• 3. Add the SDK
• 4. Configure the SDK
• 5. Enable Push
• 6. Migrating to 8.x
• Testing the SDK
• Development / Xcode
• Production / Distribution
• SDK Implementation
• Data Protection and Privacy
• Device and Contact Registration
• Handle URLs
• Runtime Toggles
• Push Notifications
• Customize Push Notifications
• Custom Sound
• Interactive Notifications
• Rich Notifications
• OpenDirect
• Custom Keys
• Application Badging
• Application Badge Override
• Event Tracking
• Mobile App Event Tracking
• In-App Messaging
• In-App Messaging
• Inbox Messaging
• Inbox Messaging
• Location Messaging
• Geofence and Beacon Messaging
• Background Location Updates
• Location Message Segmentation
• Analytics
• Analytics
• Einstein Recommendations and Collect API Integration
• Use Cases
• MobilePush SDK Privacy Manifest
• MobilePush SDK Use Cases
• Troubleshooting
• App Submission
• Push Setup
• Multiple Push SDKs
• iOS Data Protection
• Data Merge
• Keychain Crash
• MarketingCloudSDK.bundle inclusion Crash

Version 5.0.0 of the MarketingCloudSDK (formerly JB4ASDK) introduces new methods for data storage encryption that are incompatible with the methods used in JB4ASDK.

For applications upgrading from a version of JB4ASDK to version 5.x.x, the framework provides for migrating prior customer data, including contact key, tags and attributes, from the JB4ASDK database into the new framework’s storage, re-encrypting the data, and cleaning up of old data files.

Meet these conditions for successful migration of the data.

• Use the same values for Application Id and Access Token between app versions.
• Migration requires an app store update. The user cannot delete and reinstall the app.
• The app must maintain the same bundle id.
• The app cannot delete JB4ASDK data on its own.