Deferred Deep Linking

       After you enable deferred deep linking, the SE SDK will request the related parameters during initialization.

If Callback success, result can be:

• sedpLink: Jump parameter
• turlId: 7-digit short link
• sedp_urlscheme: Filled in by the user when creating a deep link

If Callback failed, errorCode can be:

• 1101: Error in SDK
• 1102: Failed to establish a connection with the server
• 1103: Timed out while trying to establish a connection with the server
• 1104: Server-side error
• 1105: The server returned data to the SDK side
• 1106: Deep link matching failed, the server callback is empty

Note: Deferred deep linking does re-direct users into your app, but there is no need to report a new _appReEngagement event.

Developers can enable deferred deep linking feature in config parameter during initialization.

Sample code:

SolarEngineConfig.Builder builder = new SolarEngineConfig.Builder();
builder.enableDeferredDeeplink(true);
SolarEngineManager.getInstance().initialize(context, "appkey",
builder.build(), new OnInitializationCallback() {
     @Override
      public void onInitializationCompleted(int code) {
             //todo
      }
});

After deferred deep linking enabled, developers can obtain its callback result or error code.

Sample code (You need to call this method before initializing the SDK):

SolarEngineManager.getInstance().setDeferredDeepLinkCallback(new DeferredDeepLinkCallback() {
            @Override
            public void onReceivedSuccess(JSONObject result) {
                //Callback success
            }

            @Override
            public void onReceivedFailed(int errorCode) {
                //Callback failed
            }
});