@selligent-marketing-cloud/selligent-react-native 3.1.0 → 3.2.6

package/ios/include/SMManager+RemoteNotification.h

@@ -1,171 +0,0 @@
-//
-//  SMManager+RemoteNotification.h
-//  MobileSDK
-//
-//  Created by Samy Ziat on 25/09/15.
-//  Copyright (c) 2015 Selligent. All rights reserved.
-//
-
-#import "SMManager.h"
-
-@class SMNotificationMessage;
-
-/**
- *  This category contains the basic step-by-step implementation to get you started.
- *  Make sure to read the category SMManager(SilentPush) to learn more about background-remote-notification.
- *
- *  ##Handling Remote Notifications
- *  In order to receive remote-notification from the back-end,  all the following methods must be included in you application's delegate:
- *
- *  - didRegisterForRemoteNotificationsWithDeviceToken:
- *  - didRegisterUserNotificationSettings:
- *  - didFailToRegisterForRemoteNotificationsWithError:
- *  - didReceiveRemoteNotification:
- *
- *  Finally, make sure to call registerForRemoteNotification according to your application's need.
- *
- *  ##Receiving Remote Notifications
- *  When a remote-notification is received, the library will automatically display a custom UIViewController.
- *  Should you want to prevent this behaviour, feel free to configure the SMManagerSetting accordingly before starting the SMManager.
- *
- *  Before displaying the remote-notification's UIVIewController, the library will broadcast an NSNotification offering the application a chance to pause any ongoing heavy task.
- *  The same principle is applied before dismissing the UIVIewController providing the application the opportunity to start again the paused heavy-task.
- *
- *  Finally, should you want to know when the user interact with UIViewController's control, an NSNotification is also posted providing information about the selected element.
- *  For additionnal information about NSNotification processing and handling, please check SMNSNotification
- *
- *  ##Displaying notification
- *  The application can display any notification based on its ID using the API displayNotificationID:
- *  These IDs can be retrieved from broadcasted NSNotification.
- *  (Please read SMNSNotification for additional information).
- *
- *  A convenient method is provided to display the last received remote-notification using displayLastReceivedRemotePushNotification
- *
- */
-@interface SMManager (RemoteNotification)
-
-/*!
- *  Mandatory method which allows notification registration
- *
- *  @discussion This API will display a dialog asking user's permission for remote-notifications (when app is launched the very 1st time).
- *  Often, this call is added right after startWithLaunchOptions:Setting:
- *  However, you may call this API later in your code according to your application need. Just remember that this call is mandatory to receive remote-notifications
- *  @warning If your device has already been registered to remote-notifications by your application or a third-party framework, then this call is not mandatory.
- */
-- (void) registerForRemoteNotification;
-
-/*!
- *  Optional method which allows getting a provisional push token [more info](https://developer.apple.com/documentation/usernotifications/asking_permission_to_use_notifications)
- *
- *  @discussion This API will automatically obtain a push token without asking the user, triggering registerForRemoteNotification afterwards will still present the prompt to the user.
- *  @warning iOS 12+ method, do only implement this method when you have a clear strategy about how to engage with these type of users.
- */
-- (void) registerForProvisionalRemoteNotification API_AVAILABLE(macos(10.14), ios(12.0), watchos(5.0), tvos(12.0));
-
-/**
- *  Use this API to unregister the current device. In other words, the device will not receive any remote-notification from our backend server anymore.
- *  @warning Deprecated method. This does NOT call unregisterForRemoteNotifications on the sharedApplication instance.
- *  Therefore, the application can still receive third-party remote-notifications.
- */
-- (void) unregisterForRemoteNotification __deprecated __deprecated_msg("Use disableRemoteNotification instead.");
-
-/**
- *  Use this API to enable the selligent notification on current device. In other words, the device will receive any remote-notification from selligent backend server.
- *  @warning This is independent from registerForRemoteNotification and from notification settings for the app on device level.
- */
-- (void) enableRemoteNotification;
-
-/**
- *  Use this API to disable the selligent notification on current device. In other words, the device will not receive any remote-notification from selligent backend server anymore.
- *  @warning This does NOT call unregisterForRemoteNotifications on the sharedApplication instance.
- *  Therefore, the application can still receive third-party remote-notifications.
- */
-- (void) disableRemoteNotification;
-
-/*!
- *  Mandatory API to be included in application:didRegisterForRemoteNotificationsWithDeviceToken:
- *
- *  @param deviceToken A string that identifies the device to APNs.
- *  @discussion This method is mandatory to handle properly all notifications
- */
-- (void) didRegisterForRemoteNotificationsWithDeviceToken:(NSData*_Nonnull) deviceToken;
-
-/*!
- *  Mandatory API to be included in application:didRegisterUserNotificationSettings
- *
- *  @param notificationSettings The user notification settings that are available to your app.
- *  @discussion This method confirms the type of notification the user would like to receive.
- *  @warning Deprecated method - replaced by  didRegisterUserNotificationSettings;
- */
-- (void) didRegisterUserNotificationSettings:(UIUserNotificationSettings*_Nonnull)notificationSettings __deprecated;
-
-/*!
- *  Mandatory API to be included in application:didRegisterUserNotificationSettings
- *
- *  @discussion This method confirms the type of notification the user would like to receive.
- */
-- (void) didRegisterUserNotificationSettings;
-
-/*!
- *  Mandatory API to be included in application:didFailToRegisterForRemoteNotificationsWithError
- *
- *  @param error An NSError object that encapsulates information why registration did not succeed. Provided by the delegate call
- *  @discussion Called when the user has deactivated remote-notification or if any other error happen.
- */
-- (void) didFailToRegisterForRemoteNotificationsWithError:(NSError *_Nonnull)error;
-
-/*!
- *  Mandatory API to be included in application:didReceiveRemoteNotification
- *  Handle and display remote notification when application is in foreground
- *
- *  @param userInfo An NSDictionary that contains information related to the remote notification. Provided by the delegate call
- *  @discussion This method is not mandatory anymore if you implement didReceiveRemoteNotification:fetchCompletionHandler:
- *  For additional information about background-remote-notifications, please check SMManager(SilentPush) for further details.
- */
-- (void) didReceiveRemoteNotification:(NSDictionary *_Nonnull)userInfo;
-
-/**
- *  Display a notification based on its ID
- *
- *  @param idNotification NSString instance referencing the unique notification's ID
- *  @discussion Basically, the application may store notification's IDs and then display them according to its need.
- *  In this context, the word "notification" stands for either a remote-notification or an InAppMessage.
- *  This feature has initially been added to allow applications to display remote-notifications at any time (not directly when the push is received).
- *  Then, it has been extended to display In-App-Messages. For additional information about IAM, please read SMManager(InAppMessage).
- */
-- (void) displayNotificationID:(NSString*_Nullable)idNotification;
-
-/**
- *  Retrieve and display the last known notification.
- *
- *  @discussion Basically, This API is a helpher which combine both retrieveLastRemotePushNotification and displayNotificationID:
- *  It only focuses on remote-notification. Not on IAM.
- *  At this stage, only the very last remote-notification can be recovered, previous ones are automaticly overriden.
- *  To learn more about this API, please read documentation in [SMManagerSetting](SMManagerSetting), more particularly [SMManagerSetting shouldDisplayRemoteNotification]
- */
-- (void) displayLastReceivedRemotePushNotification;
-
-/**
- *  Retrieve information about the last received remote-notification
- *
- *  @return NSDictionary instance containing basic information about the last push, nil if no push was received so far.
- *  @discussion This is a convinient method to quickly retrieve the last remote-notificaiton known by the device.
- *  At this stage, only the very last remote-notification can be recovered, previous ones are automaticly overriden.
- *  To learn more about this API, please read documentation in [SMManagerSetting](SMManagerSetting), more particularly [SMManagerSetting shouldDisplayRemoteNotification]
- */
-- (NSDictionary*_Nullable) retrieveLastRemotePushNotification;
-
-/**
- *  Tells to the SDK that a certain SMNotificationMessage object has been seen.
- *  The SDK will send an opened event to the Selligent platform.
- *
- *  @param notificationMessage  SMNotificationMessage that needs to be marked as seen.
- *  @discussion This is a convinient method when the behaviour when receiving a remote-notification is handled at App side
- *  and the standard events need to be sent back to the Selligent platform.
- *  @warning The App will be fully responsible of possible event duplication in the Selligent platform when implementing this method,
- *  as each execution will trigger a new event, so make sure to just trigger it once if you don't want this to happen.
- *  @see SMNotificationMessage
- */
-- (void) setNotificationMessageAsSeen:(SMNotificationMessage*_Nullable)notificationMessage;
-
-@end

package/ios/include/SMManager+SMEvent.h

@@ -1,67 +0,0 @@
-//
-//  SMManager+SMEvent.h
-//  MobileSDK
-//
-//  Created by Samy Ziat on 25/09/15.
-//  Copyright (c) 2015 Selligent. All rights reserved.
-//
-
-#import "SMManager.h"
-
-@class SMEvent;
-
-/**
- *  Sending any set of data to the back-end can be done with the API sendSMEvent:
- *
- *  ##Event type
- *  Few default events are already available for you to be used. 
- *  They all inhirit from SMEvent and are configurable through their constructors.
- *  At the time of this writing, they default provided events are :
- *
- *  * SMEventUserLogin
- *  * SMEventUserLogout
- *  * SMEventUserRegistration
- *  * SMEventUserUnregistration
- *
- *  ##Custom events
- *  Simplest case is to create an instance of SMEvent.
- *  Then, inject your data in it (Code example bellow).
- *
- *  Also, you can subclass from default provided event-type or even create your own sub-classes of events.
- *
- *  The library will keep sending events to the backend as far as they inhirit from SMEvent.
- *
- *  ##Injecting custom data in events
- *  Any information can be appended to an event and sent to your back-end.
- *  This is basically done by creating a dictionary containing your data and injecting it as in the example bellow.
- *
- *
- *  @code
- *  //  Dictionary with your custom data
- *
- *  NSDictionary *dictMyCustomData = @{@"MyKey": @"MyValue"};
- *
- *  //  Create the event
- *
- *  SMEvent *event = [SMEvent eventWithDictionary:dictMyCustomData];
- *
- *  //  Sent the event to the back-end
- *  
- *  [[SMManager sharedInstance] sendSMEvent:event];
- *  @endcode
- *
- *  The exemple above is considered as a custom event.
- *  The same principle can be applied to any event-type subclasses stated above or to your own subclasses of SMEvent.
- */
-@interface SMManager (SMEvent)
-
-/*!
- *  Send an event to the Selligent platform
- *
- *  @param event An SMEvent object containing your event
- *  @discussion Should you want to track the event's response, please check SMEvent
- *  @see SMEvent
- */
-- (void) sendSMEvent:(SMEvent*_Nullable)event;
-
-@end

package/ios/include/SMManager+SMLink.h

@@ -1,44 +0,0 @@
-//
-//  SMManager+SMLink.h
-//  MobileSDK
-//
-//  Created by Marc Biosca on 7/12/21.
-//  Copyright © 2021 Selligent. All rights reserved.
-//
-
-#import "SMManagerUniversalLinksDelegate.h"
-
-@class SMNotificationMessage;
-@class SMLink;
-
-/**
- *  This category will help you to manage specific behaviour related to SMLink.
- */
-@interface SMManager (SMLink)
-
-/**
- *  Used to let the app manage the behaviour of "deeplink" button types containing universal links.
- *
- *  @param delegate  An object implementing SMManagerUniversalLinksDelegate methods
- *  @discussion This setting will allow you to manage the behaviour of the click in a "deeplink" button type that contains an universal link.
- *  In order to do it, the delegate object should implement [SMManagerUniversalLinksDelegate executeLinkAction:] method, it will provide the app with the defined NSURL.
- *  @see SMManagerUniversalLinksDelegate
- */
-- (void) universalLinksDelegate:(id <SMManagerUniversalLinksDelegate>_Nullable) delegate;
-
-/**
- *  Tells to the SDK that a certain SMLink object has been clicked.
- *  The SDK will send a clicked event to the Selligent platform.
- *
- *  @param link  SMLink that needs to be marked as clicked.
- *  @param notificationMessage The SMNotificationMessage from where the link was extracted.
- *  @discussion This is a convinient method when the behaviour when receiving a remote-notification is handled at App side
- *  and the standard events need to be sent back to the Selligent platform.
- *  @warning The App will be fully responsible of possible event duplication in the Selligent platform when implementing this method,
- *  as each execution will trigger a new event, so make sure to just trigger it once if you don't want this to happen.
- *  @see SMLink
- *  @see SMNotificationMessage
- */
-- (void) setLinkAsClicked:(SMLink*_Nullable)link fromMessage:(SMNotificationMessage*_Nullable)notificationMessage;
-
-@end

package/ios/include/SMManager+SilentPush.h

@@ -1,53 +0,0 @@
-//
-//  SMManager+SilentPush.h
-//  MobileSDK
-//
-//  Created by Samy Ziat on 25/09/15.
-//  Copyright (c) 2015 Selligent. All rights reserved.
-//
-
-#import "SMManager+RemoteNotification.h"
-
-/**
- *  Optionally, you can support silent-remote-notificaiton which will not render anything on the device.
- *  To know more about this topic, please visit [the Apple documentation.](https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/ApplePushService.html#//apple_ref/doc/uid/TP40008194-CH100-SW1)
- *
- *  Even if you're not planning to use silent-pushes, we recommand enabling this service in your application anyway.
- *  As using this service will also improve rendering time for the usual (non-silent) remote-notifications.
- *
- *  ##Implementation
- *  In a nutshell, you should do the following :
- *
- *  *   In the application's target, enable the following: Capabilities > Background Modes > Remote Notifications
- *  *   Removing previous call to didReceiveRemoteNotification: (see last point of "Start library")
- *  *   Implement didReceiveRemoteNotification:fetchCompletionHandler: in UIApplication's delegate.
- */
-@interface SMManager (SilentPush)
-
-/**
- *  Mandatory API to be included in application:didReceiveRemoteNotification:fetchCompletionHandler
- *  Handle and display the received notification according to different application state.
- *
- *  @param userInfo An NSDictionary that contains information related to the remote notification. Provided by the delegate call
- *  @param completionHandler The block-completion to be processed after the download. Provided by the delegate call
- *  @discussion It is recommended to use this API over didReceiveRemoteNotification: as it handles silent-remote-notificaitons.
- *  @warning You must enable "Remote notifications" in your application's Capabilities in order to use this API. 
- *  If this capability is not useful to your application, you must use  [SMManager(RemoteNotification) didReceiveRemoteNotification:] instead.
- */
-- (void) didReceiveRemoteNotification:(NSDictionary *_Nullable)userInfo fetchCompletionHandler:(void (^_Nullable)(UIBackgroundFetchResult))completionHandler;
-
-/**
- *  See didReceiveRemoteNotification:fetchCompletionHandler:
- *
- *  @param userInfo An NSDictionary that contains information related to the remote notification. Provided by the delegate call
- *  @param completionHandler The block-completion to be processed after the download. Provided by the delegate call
- *  @param resultFetch The enumeration that might be overiden by application if needed
- *  @discussion This API is provided in order to force the fetch result to a specific value. 
- *  Use it only if your application need to overide the service. 
- *  Otherwise, please use didReceiveRemoteNotification:fetchCompletionHandler:
- *  @warning You must enable "Remote notifications" in your application's Capabilities in order to use this API.
- *  If this capability is not useful to your application, you must use [SMManager(RemoteNotification) didReceiveRemoteNotification:] instead.
- */
-- (void) didReceiveRemoteNotification:(NSDictionary *_Nullable)userInfo fetchCompletionHandler:(void (^_Nullable)(UIBackgroundFetchResult))completionHandler ForceResultFetch:(UIBackgroundFetchResult)resultFetch;
-
-@end

package/ios/include/SMManager+StyleOptions.h

@@ -1,36 +0,0 @@
-//
-//  SMManager+StyleOptions.h
-//  MobileSDK
-//
-//  Created by Gilbert Schakal on 30/04/16.
-//  Copyright © 2016 Selligent. All rights reserved.
-//
-
-#import "SMManager.h"
-
-@class SMInAppContentStyleOptions;
-
-/*!
- *  Allows you to customise the appearance of all the In App Content containers
- *
- *  ##Implementation
- *      * First create a SMInAppContentStyleOptions object instance
- *      * load it with loadStyleOptions:
- */
-
-@interface SMManager (StyleOptions)
-
-/*!
- * This will allow you to load your custom SMInAppContentStyleOptions object
- *
- * @param options a SMInAppContentStyleOptions object
- * @see SMInAppContentStyleOptions
- */
-- (void) loadStyleOptions:(SMInAppContentStyleOptions*_Nullable)options;
-
-/*!
- * Reset style options to default one
- */
-- (void) resetStyleOptions;
-
-@end

package/ios/include/SMManager+UserNotification.h

@@ -1,180 +0,0 @@
-//
-//  SMManager+UserNotification.h
-//  MobileSDK
-//
-//  Created by Gilbert Schakal on 25/01/2017.
-//  Copyright © 2017 Selligent. All rights reserved.
-//
-
-#import "SMManager+RemoteNotification.h"
-#import <UserNotifications/UserNotifications.h>
-#import <UserNotificationsUI/UserNotificationsUI.h>
-
-@class SMNotificationMessage;
-
-/**
- *  In addition to the implementation of category SMManager(RemoteNotification), this category will supply a support of iOS 10 and usage of UserNotifications framework
- *
- *  Make sure to read the category SMManager(RemoteNotification) to learn more about remote-notification for support of iOS version 8 and 9 and to correctly register for remote notification.
- *
- *  If you build against iOS 10+ and you use UserNotifications framework we then recommend you to implement those 2 methods of UNUserNotificationCenterDelegate in your appdelegate:
- *
- *      - didReceiveNotificationResponse:
- *      - didReceiveNotificationResponse:withCompletionHandler:
- *      - willPresentNotification:
- *      - willPresentNotification:withCompletionHandler:
- *
- *  Register your appdelegate to the UNUserNotificationCenter by adding the following two lines in the didFinishLaunchingWithOptions delegate.
- *
- *   `UNUserNotificationCenter *center = [UNUserNotificationCenter currentNotificationCenter];`
- *
- *   `center.delegate = self;`
- *
- *
- * __Notification extensions__
- *
- * In this category you will also find the support for notification extensions target (content and service)
- *
- *      Init extensions (to be used for each extensions that will be added to your project):
- *
- *          - startExtensionWithSetting:
- *
- *      Notification content extension :
- *
- *          - didReceiveNotification:
- *
- *      Notification service extension :
- *
- *          - didReceiveNotificationRequest:
- *          - didReceiveNotificationRequest:withContentHandler:
- *          - serviceExtensionTimeWillExpire
- *
- */
-@interface SMManager (UserNotification)
-
-/*!
- *  Mandatory API when used inside App in AppDelegate (but is optional for Notification Content Extension), when building against iOS 10+ and using UserNotifications framework, to be included in userNotificationCenter:didReceiveNotificationResponse:withCompletionHandler.
- *  Handle and display remote notification.
- *
- *  @param response An UNNotificationResponse that contains information about the notification and the interaction the user has done with it. Provided by the delegate call
- *  @discussion This method is mandatory when used in AppDelegate but is optional when implementing Notification content extension. When used in Notification Content Extension it  provides to the sdk the ability to process the action that should be triggered without opening the app (in this case don't forget to call the completionhandler with the desired UNNotificationContentExtensionResponseOption
- */
-- (void) didReceiveNotificationResponse:(UNNotificationResponse*_Nonnull)response;
-
-/*!
- *  Mandatory API, when building against iOS 10+ and using UserNotifications framework, to be included in userNotificationCenter:didReceiveNotificationResponse:withCompletionHandler
- *  Handle and display remote notification.
- *
- *  @param response An UNNotificationResponse that contains information about the notification and the interaction the user has done with it. Provided by the delegate call
- *  @param completionHandler A completion that will be called with the option UNNotificationContentExtensionResponseOptionDismiss
- */
-- (void) didReceiveNotificationResponse:(UNNotificationResponse *_Nonnull)response withCompletionHandler:(void (^_Nullable)(UNNotificationContentExtensionResponseOption option))completionHandler;
-
-/*!
- *  Mandatory API, when building against iOS 10+ and using UserNotifications framework, to be included in userNotificationCenter:willPresentNotification:withCompletionHandler
- *  Handle the remote notification when app is in foreground.
- *
- *  This allows the SDK to inform the services that the Selligent push has been received.
- *
- *  Calling this method does not call any CompletionHandler. You will have to call the completion handler with your preferred option.
- *
- *  For example you can call inside this delegate :
- *      completionHandler(UNNotificationPresentationOptionAlert);
- *
- *  @param notification A UNNotification that contains information about the notification.
- */
-- (void) willPresentNotification:(UNNotification*_Nonnull)notification;
-
-/*!
- *  Mandatory API, when building against iOS 10+ and using UserNotifications framework, to be included in userNotificationCenter:willPresentNotification:withCompletionHandler
- *  Handle the remote notification when app is in foreground and call the completionHandler(UNNotificationPresentationOptionAlert) by default (or UNNotificationPresentationOptionBanner | UNNotificationPresentationOptionList for iOS 14+).
- *
- *  This allows the SDK to inform the services that the Selligent push has been received.
- *
- *  You don't need to call the completion handler in the delegate anymore.
- *
- *  @param notification An UNNotification that contains information about the notification.
- *  @param completionHandler A Completion handler that will be called with a specific UNNotificationPresentationOption depending on the SMForegroundDisplayType value specified when starting the SDK.
- *  @see SMManagerSetting
- */
-- (void) willPresentNotification:(UNNotification*_Nonnull)notification withCompletionHandler:(void (^_Nullable)(UNNotificationPresentationOptions options))completionHandler;
-
-/*!
- *  Mandatory method which allows sdk initialisation when building against iOS 10+ and using Notification Extensions .
- *  To be included in didReceiveNotification: when implementing Notification content extension and/or in didReceiveNotificationRequest:withContentHandler: when implementing Notification service extension
- *
- *  @param setting  mandatory SMManagerSetting instance to start-up the library - this setting mus tbe initialized with only url, clienID and privateKet provided by selligent
- *  @see SMManagerSetting
- *  @discussion This method is mandatory in order to start / initialize the library and should be called in in didReceiveNotification: when implementing Notification content extension and/or in didReceiveNotificationRequest:withContentHandler: when implementing Notification service extension
- *  @see SMManagerSetting
- */
-- (void) startExtensionWithSetting:(SMManagerSetting*_Nonnull)setting;
-
-/*!
- *  Optional API, when building against iOS 10+ and using a Notification Content Extension target, to be included in NotificationViewController didReceiveNotification:
- *  Handle the push action buttons that may be present in the selligent notification payload
- *
- *  This allows the SDK to display the action buttons in the push notification outside of the app.
- *
- *  The category that must be added to Info.plist of the Notification Content Extension target is mandatory and must be SELLIGENT_BUTTON.
- *
- *  @param notification A UNNotification that contains information about the notification.
- */
-- (void) didReceiveNotification:(UNNotification*_Nonnull)notification __deprecated_msg("Method deprecated. Use `didReceiveNotification:withContext:`");
-
-/*!
- *  Optional API, when building against iOS 10+ and using a Notification Content Extension target, to be included in NotificationViewController didReceiveNotification:
- *  Handle the push action buttons that may be present in the selligent notification payload
- *
- *  This allows the SDK to display the action buttons in the push notification outside of the app.
- *
- *  The category that must be added to Info.plist of the Notification Content Extension target is mandatory and must be SELLIGENT_BUTTON.
- *
- *  @param notification A UNNotification that contains information about the notification.
- *  @param context A NSExtensionContext that contains the context information of the extension.
- */
-- (void) didReceiveNotification:(UNNotification*_Nonnull)notification withContext:(NSExtensionContext*_Nullable)context;
-
-/*!
- *  Optional API, when building against iOS 10+ and using a Notification Service Extension target, to be included in NotificationService didReceiveNotificationRequest:withContentHandler:
- *  Handle the selligent payload before displaying it to the user
- *
- *  This allows the SDK to decrypt the payload before displaying it to the user if you have activated the encryption of push.
- *
- *  @param request An UNNotificationRequest that contains the original notification request.
- *  @return UNMutableNotificationContent the updated content of the payload.
- *  @discussion you can use this method if you have decided to trigger the block to execute with the modified content by yourself otherwise if you want the sdk to manage all steps please use SMManager didReceiveNotificationRequest:withContentHandler:
- */
-- (UNMutableNotificationContent*_Nullable) didReceiveNotificationRequest:(UNNotificationRequest*_Nonnull)request;
-
-/*!
- *  Optional API, when building against iOS 10+ and using a Notification Service Extension target, to be included in NotificationService didReceiveNotificationRequest:withContentHandler:
- *  Handle the selligent payload before displaying it to the user
- *
- *  This allows the SDK to decrypt the payload before displaying it to the user if you have activated the encryption of push.
- *
- *  @param request An UNNotificationRequest that contains the original notification request.
- *  @param contentHandler The block to execute with the modified content
- *  @discussion you can use this method if you want the sdk to manage the display of the notification after the decryption has been processed
- */
-- (void) didReceiveNotificationRequest:(UNNotificationRequest*_Nonnull)request withContentHandler:(void (^_Nullable)(UNNotificationContent*_Nonnull))contentHandler;
-
-/*!
- *  Optional API, when building against iOS 10+ and using a Notification Service Extension target, to be included in NotificationService serviceExtensionTimeWillExpire
- *  Tells the sdk that the extension is about to be terminated.
- *  @discussion this method is to be implemented only if you have implemented SMManager didReceiveNotificationRequest:withContentHandler:
- */
-- (void) serviceExtensionTimeWillExpire;
-
-/**
- *  Optional API, retrieves the SMNotificationMessage object from a given userInfo
- *
- *  @param userInfo An NSDictionary
- *  @return SMNotificationMessage instance containing the information extracted from the given userInfo.
- *  @discussion This is a convinient method to get the SMNotificationMessage from an incoming remote-notification.
- *  It can be used for custom purposes when receiving a remote-notification in foreground for iOS 10+.
- *  @see SMNotificationMessage
- */
-- (SMNotificationMessage*_Nullable) retrieveNotificationMessage:(NSDictionary*_Nullable)userInfo;
-
-@end

package/ios/include/SMManager+ViewController.h

@@ -1,45 +0,0 @@
-//
-//  SMManager+ViewController.h
-//  MobileSDK
-//
-//  Created by Gauthier Dumont on 07/07/15.
-//  Copyright (c) 2015 Selligent. All rights reserved.
-//
-
-/**
- *  This category will help our SDK making the WKWebView navigation buttons enabled/disabled when needed, if inAppMessageWKNavigationDelegate is set.
- */
-@interface SMManager (ViewController)
-
-/*!
- *  Use this API inside the corresponding method in your WKNavigationDelegate when inAppMessageWKNavigationDelegate is set.
- *  It will enable the SDK to have the navigation arrows working properly and log the error when the delegate is implemented in your APP.
- *
- *  @param webView The WKWebView from the WKNavigationDelegate.
- *  @param navigation The WKNavigation from the WKNavigationDelegate.
- *  @param error The NSError from the WKNavigationDelegate.
- */
-- (void) webView:(WKWebView *_Nonnull)webView didFailNavigation:(WKNavigation *_Nonnull)navigation withError:(NSError *_Nonnull)error;
-
-/*!
- *  Use this API inside the corresponding method in your WKNavigationDelegate when inAppMessageWKNavigationDelegate is set.
- *  It will enable the SDK to have the navigation arrows working properly when the delegate is implemented in your APP.
- *
- *  @param webView The WKWebView from the WKNavigationDelegate.
- *  @param navigation The WKNavigation from the WKNavigationDelegate
- */
-- (void) webView:(WKWebView *_Nonnull)webView didFinishNavigation:(WKNavigation *_Nonnull)navigation;
-
-/*!
- *  Use this API inside the corresponding method in your WKNavigationDelegate when inAppMessageWKNavigationDelegate is set.
- *  It will enable the SDK to have the navigation arrows working properly when the delegate is implemented in your APP.
- *
- *  @param webView The WKWebView from the WKNavigationDelegate.
- *  @param navigation The WKNavigation from the WKNavigationDelegate.
- */
-- (void) webView:(WKWebView *_Nonnull)webView didCommitNavigation:(WKNavigation *_Nonnull)navigation;
-
-@end
-
-
-

package/ios/include/SMManager.h

@@ -1,69 +0,0 @@
-//
-//  SellMobileSDK.h
-//  MobileSDK
-//
-//  Created by Gilbert Schakal on 17/04/15.
-//  Copyright (c) 2015 Selligent. All rights reserved.
-//
-
-#import <UIKit/UIKit.h>
-
-#import "SMManagerHelper.h"
-
-@class SMManagerSetting;
-
-/*!
- *  ##Start Library
- *  In order to start the library, please follow the steps bellow (will mainly happen in your UIApplication's delegate):
- *
- *  -   Use startWithLaunchOptions:Setting: in your application:didFinishLaunchingWithOptions:
- *  -   Implement methods described in SMManager(RemoteNotification) in your UIApplication's delegate
- *  -   When building against iOS10 : Implement methods described in SMManager(UserNotification) in your UIApplication's delegate
- *
- *  Starting the library will not register for remote notification.
- *  Don't forget to call registerForRemoteNotification according to your application's need.
- *
- *  From there, your application is ready to handle all incoming remote-notifications.
- */
-@interface SMManager : NSObject
-
-/**
- *  The current version of the library
- */
-@property (readonly, nonatomic) NSString *_Nonnull versionLib;
-
-/*!
- * Singleton for SellMobileSDK Class which allow to access public SellMobileSDK methods and properties
- *
- * @return SMManager: singleton instance of SMManager class
- */
-+ (instancetype _Nonnull) sharedInstance;
-
-/*!
- *  Mandatory method which allows sdk initialisation. To be included in application:didFinishLaunchingWithOptions: 
- *  Make sure to provide the launchOptions dictionary
- *
- *  @param launchOptions NSDictionary instance indicating the reason the app was launched (if any). This dictionary is provided by application:didFinishLaunchingWithOptions
- *  @param setting  mandatory SMManagerSetting instance to start-up the library
- *  @see SMManagerSetting
- *  @discussion This method is mandatory in order to start / initialize the library and should be called in application:didFinishLaunchingWithOptions:
- */
-- (void) startWithLaunchOptions:(NSDictionary* _Nullable)launchOptions Setting:(SMManagerSetting* _Null_unspecified)setting;
-
-/*!
- *  Optional + used for testing only. This method will re-configure the SMManager with the newly provided information
- *
- *  @discussion This is a handy API in case you would like to switch between two backend environements without rebuilding your target.
- *  @param setting  mandatory SMManagerSetting instance to start-up the library
- *  @warning This API is provided for testing purposes only. Never use it in production.
- *  Make sure to re-enable any service after calling this API.
- *  @see SMManagerSetting
- */
-- (void) reloadSetting:(SMManagerSetting* _Null_unspecified)setting;
-
-/*!
- *  Device id  used by the sdk
- */
-- (NSString*_Nullable) deviceID;
-
- @end