Adjoe.init(Context, String, Adjoe.Options, AdjoeInitializationListener)
.AdjoeInitializationListener
's onInitialisationFinished
or onInitialisationError
method.Adjoe.init
will immediately invoke onInitialisationFinished
until your app is removed from the heap.onResume
method.Adjoe.init(Context, String)
or Adjoe.init(Context, String, AdjoeInitializationListener)
instead.Adjoe.init(Context, String)
or Adjoe.init(Context, String, Adjoe.Options)
instead.Adjoe.Options
object in the following way:Adjoe.getUserId(Context)
.android.process
for application tag in androidManifest file.isInitialized
methodAdjoe.isInitialized()
. This will return true
if the SDK is initialized and false
otherwise. However, you should not condition calling init
on the result of isInitialized
because the SDK will do some checks on its own. You should not do something like the following as it can lead to bad user experience:init
without checking for isInitialized
. You can however use isInitialized
e.g. for debugging or to check whether the SDK is initialized before calling other methods of the SDK like requestRewards
.