Handle Deeplink AFTER loading external configuration file

App does handle handle deep link delegate on cold open.

On cold open, the app will fetch an external configuration file and load the UI when completed. The deep link delegate is being called too soon before the UI can be created. When does the DeeplinkDelegate get called and when would be the optimal time to listen for the call?

Didn't find what you were looking for?

New post

Comments

4 comments

  • Hi David,

    If you are following our documentation on Deep Linking, then the UI should be able to be created in an appropriate timeframe. Would you be able to compare your code against our Sample App and see if there are any discrepancies? Please be sure to investigate line 193 and below of the App Delegate to see more information on the completion handler.

    Comment actions Permalink
  • ^does NOT handle deep link delegation on cold open

    Comment actions Permalink
    0
  • On cold open, the app will fetch an external configuration file and load the UI when completed. The deep link delegate is being called too soon before the UI can be created. When does the DeeplinkDelegate get called and when would be the optimal time to listen for the call? promotional umbrellas

     
    Comment actions Permalink
    0
  • Handling a deeplink after loading an external configuration file involves a sequence where the application first retrieves and processes the configuration file, often from a remote server, to set up necessary parameters. Once the configuration is fully loaded, the app then processes the deeplink to navigate to the appropriate screen or perform specific actions. This ensures that the app has all the required settings and resources before responding to the deeplink, allowing for a smooth user experience of glitzyinfo and avoiding potential errors caused by missing configurations.

     
     
    Comment actions Permalink
    0

Please sign in to leave a comment.