Starting the Launcher Skip Navigation

Starting the
Launcher

After the
GDiOS
delegate (usually also the
UIApplicationDelegate
) receives the
onAuthorized:
callback, the
BlackBerry Dynamics Launcher Library
needs to start up various services that call into the
BlackBerry Dynamics
API. Starting the
Launcher
requires that startup options be provided. Internally, the library uses the
GDUtility
and
GDPushConnection
classes. These classes are singleton classes with a single delegate. If the host app is using these classes, the
Launcher Library
needs to either retrieve the required information through a delegate callback or through method calls into the
Launcher
.
Startup options
Description
GTLInternalGDAuthTokenAndPushConnectionManagement
This is the default option. Use this option if the host app does not use
BlackBerry Dynamics
auth tokens (
GDUtility
class) or
BlackBerry Dynamics
push connection. The specified classes are used internally in the
Launcher
.
GTLHostGDAuthTokenManagement
Use this option if the host app uses the
GDUtility
class internally. The
Launcher
makes a delegate callback into the app whenever it requires an auth token (see below).
GTLHostGDAuthTokenManagement
Use this option if the host app uses
GDPushConnection
and specifies a delegate. Whenever the host app receives the
onStatus:
call, the value provided should be passed to the
Launcher
.