Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

On SDK 4 we have exposed new APIs with backward compatibility with SDK 3 APIs with the below changes:
  • Inbox messages  - (Not relevant for DMC customers)
    • support of Appoxee default UI for Inbox
    has been removed and we instead a reference
    • was removed
    • As an alternative a reference UI implementation is provided in our example application (code API gitHub).
    • In addition, Instead of using AppoxeeMessage object, developer will need to use APXRichMessage object.
  • More Apps, User Feedback removed – SDK  (Not relevant for DMC customers)– SDK 4 implemented an empty implementation of these features 
  • Custom Field – fetching a custom field will be from the device cache only (values will not be fetched from server. So when migrating, on getting a custom field which wasn’t set, a nil value will be returned).
  • Deep-Linking - SDK 4 uses iOS URL schemes for deep-linking. As such please make sure you perform the following:
    • You must implement the URL schemes and register them (see apple documentation)
    • Test all Deep linking by entering the deep link in the browser on the device and make sure that the expected screen is showing in the app.

...

4. SDK 4 uses iOS URL schemes for deep-linking.If you have not registered the deep-link URLs, you will need to register them in order for deep-linking to work (see apple documentation).

5. Follow Add the Mobile Push SDK for Appoxee Standalone

Optional Steps:

  1. Remove all frameworks which were required in SDK3 and are not required by SDK 4 :AudioToolbox.framework, QuartzCore.framework, CoreGraphics.framework, libxml2.dylib, AWSSQS.framework, AWSRuntime.framework
  2. Upgrade and use SDK 4 APIs. While SDK has backward compatibility with SDK 3 APIs, the APIs exposed on SDK 4 have additional capabilities including more sophisticated error handling.

...