Setup
Requirements for iOS:
- The minimum deployment target needs to be at least 11.0
- Required react-native version 0.60.x+
Requirements for Android:
Important: When using tools like Proguard to obfuscate your code, make sure to exclude Android Link SDK package (
com.argyle._) from the process, it may cause unexpected runtime issues otherwise. You can do this by adding this line to your proguard-rules.pro:-keep class com.argyle. { _; }okhttp3 library, the Link SDK currently has a dependency of okhttp3:4.9.2. If some of your dependencies use an older version (okhttp3:3.x.x), you may need to update a version that also uses okhttp3:4.x.x. Alternatively, you may try forcing the version of the dependency as follows:
Build gradle:
- Add the SDK dependency.
$ npm install @argyleio/argyle-plugin-react-native --save or
$ yarn add @argyleio/argyle-plugin-react-native
- Update the Argyle pod with these commands, in case an older version of Argyle pod was installed:
$ cd ios
$ pod install
$ pod update
- Configure and start the flow:
SDK configuration:
The API host in this SDK configuration example is set to the Argyle Sandbox API (
https://api-sandbox.argyle.com/v1). It’s a good idea to test your implementation in Sandbox mode first, then change this to the Production API (https://api.argyle.com/v1) when you are ready to go live.Closing Link programmatically
Normally, the user closes Link but you can also close it by callingArgyleSdk.close().
We strongly recommend upgrading the SDK as soon as there is a new version available. Doing so will help you provide the best Argyle Link experience in your application.
Configuration
Argyle Link provides multiple configuration options and callbacks that customize how this UI element functions in your application. The only argument that is mandatory when invoking Argyle Link is thelinkKey, which you can find in Argyle Console.
By default, anytime Argyle Link is initialized, it will be treated as a new session for a new user. To ensure your users retain their previous state in Argyle Link when it is re-initialized for them, your application must use the userToken parameter.
For a full list of Link configuration parameters, see the Link reference.
User tokens
User tokens are temporary access keys that let you start Argyle Link for an existing user. Tokens are short-lived. Generate a new token using the API every time you initialize Argyle Link for a returning user. You can create user tokens using the/user-tokens endpoint.
Make sure that you request user tokens on your server-side and your client_id and client_secret are never exposed on the front-end.