Setup
-
Navigate to the Resources folder imported via the
Setup
sample and locate theSequenceConfig
ScriptableObjecta) If you imported the SDK manually, you will need to create a Resources folder and SequenceConfig
b) Create a
Resources
folder located atAssets/Resources
. The SDK uses Resources.Load to load the configScriptableObject
we'll create in the next step.c) On the top bar, click
Assets > Create > Sequence > SequenceConfig
and place the newly createdScriptableObject
at the root of yourResources
folder. -
Fill in
SequenceConfig
with the appropriate values for your project.a)
Url Scheme
- You must replace this with a string that is unique to your application. This is very important. Failure to do so will cause unexpected behaviour when signing in with social sign in and it will not work.b)
Builder API Keys
- These are found in the Sequence Builder underSettings > API Keys
c)
WaaS Config Key
- You can get this key in Sequence Builder underOnboard > Embedded Wallet
d)
StoreSessionPrivateKeyInSecureStorage
- Available on select platforms: we have integrated with the platform's native secure storage system. If enabled, we will store session wallet info (including the private key) in secure storage and automatically attempt to recover the session for the user after closing the app (so they won't need to login again). With this disabled (default) or on an unsupported platform, the session wallet's private keys never leave the application's runtime memory; however, your user will need to sign in again anytime they close the app. The defaultLoginPanel
UI (see Recovering Sessions) will handle this behaviour for you automatically, navigating to the appropriate page.e)
EnableMultipleAccountsPerEmail
- By default, the SDK will only allow users to create one account per email. The account is initially associated with the login method used (email + OTP, PlayFab, Google, etc.); the user can associate additional login methods with their account (more on this in the Authentication section). IfEnableMultipleAccountsPerEmail
is enabled, users have the option to create multiple accounts per email address (associated with different login methods). While we have enabled this functionality, we, in general, feel this behaviour may be confusing to end-users and recommend integrators keep this option in the default disabled status.