Initialization
API Interface / React Native
Last updated
API Interface / React Native
Last updated
The MOVE SDK must be initialized natively. For the first init, the SDK expects to be setup after user onboarding using Javascript. In this case, Javascript passes the required auth code or , and objects.
In all future inits, the SDK expects to be initialized natively at app start points (In AppDelegate for iOS, and MainApplication for Android). This is to guarantee that the MOVE SDK is set up and active before the limited time provided by the OS in background wakeups is consumed.
The native init will re-use the last authentication and configs objects passed to the SDK from the JS initialization.
To initialize the SDK natively, in your AppDelegate:
To initialize the SDK natively, in your MainApplication:
Setup will return with a promise or throw an error on failure, such as when the code is expired or there is no network available. These errors must be caught.
Will be remove in future versions, use setupWithCode(...)
instead.
To setup the SDK in React Native you have to provide and auth code (provided by the backend), and . is optional object with additional SDK configurations.
Previously setup was done using a object.
The SDK will provide all relevant information on its status and ability to recognise trips. In order to have up-to-date information about the status of the SDK you can add (e.g. to be aware of every change, to be aware of every change) or request this information directly (e.g. and ).
In addition, the SDK will report all possible and that may prevent the SDK from functioning properly. Among these errors and warnings will be those that indicate a missing permission or incomplete guarantee of certain permission. This is useful for informing the user of certain problems in granting permissions to the host app. To keep track of these errors and warnings you can use listeners ( and ) or request a list of errors or warnings directly ( and ).