Auth SDK v0.2.x -> v0.3.0 Migration
This guide is meant for developers who have already integrated apps with an older version of the Arcana Auth SDK and run them using Arcana Network Testnet. If you are new to Arcana Network, please visit Quick Start Guide to get started.
When you migrate from an older version of the Arcana Auth SDK to v0.3.0, there are some breaking changes. These changes are mostly related to deploying an app on the Arcana Testnet and the use of Arcana Storage SDK (no longer supported). There are no breaking changes in the Auth SDK usage related to user onboarding or blockchain transaction signing functions. Also, the Arcana wallet has a revamped, better look in this release.
What has Changed?
-
This release does not contain Arcana Storage SDK.
-
Arcana Blockchain is no longer listed in the list of available blockchain networks in the Arcana wallet dropdown.
-
Now you can use the Auth SDK and Arcana wallet on any supported EVM-compatible chain for user onboarding and signing of blockchain transactions.
-
The blockchain transaction activity is no longer available in the form of a tab in the main Arcana wallet screen. You can see the activity listed in the newly added combined notification screen in the Arcana wallet.
Developer Dashboard
- There were some breaking changes in the registered application database schema. If you were already using an older version of the Auth SDK, you need to re-register and configure your application again using the latest Arcana Developer Dashboard. The Client ID assigned to you earlier will not work. You need to re-register and obtain a new one. Make sure you use the new Client ID while integrating with the Auth SDK.
Auth SDK
- There is no usage change in the Auth SDK in this release.
- After re-registering your app, the dashboard will assign a new Client ID. You need to use the new Client ID during integration with the Auth SDK.
How to Migrate to v0.3.0
-
You need to re-register your app using the Arcana Developer Dashboard. This is required to obtain a fresh Client ID and use that for integrating with the Auth SDK. The older Client ID will NOT WORK with the latest v0.3.0 release. Follow the instructions in the How to Configure App Guide to re-register and configure your app.
-
If you were using the Arcana Storage SDK, it is no longer supported. You need to stop using Storage SDK in your app for the time being until we begin supporting Storage SDK in a future release.
-
You need to re-integrate your app with the Auth SDK by providing the new Client ID after re-registering and configuring your application using the developer dashboard.
-
If you had enabled the Arcana Testnet blockchain network in Web3 wallet operations, you will need to remove this network altogether as it no longer exists. The Arcana Network Testnet Blockchain Explorer too is no longer available. Arcana Network smart contracts are deployed on Polygon now. In this release, Arcana wallet supports all EVM-compatible chains besides the default ones that show in the drop-down. Use the Wallet User Guide and the Wallet Developer Guide to add and switch networks using the wallet UI or programmatically.
-
The wallet activity tab on the wallet token asset tab is gone. A new 'notification' tab is added to the wallet screen. You can see the list of all activities in the notification tab. It lists send tokens, contract deployment, and contract interaction transactions performed by the wallet user.
What's New?
The new improved Auth SDK now supports NFT preview, NFT transactions, and management of NFT collections. A new combined notification screen displays blockchain transactions related to smart contracts, tokens as well as NFTs. For details, see Auth SDK release notes.