Plus the differences between latest Web3auth SDK (v2.0.1 for Plugin) and prior SDK behaviors (v1.8.0 for Plugin) and "user with email already exists" issue
Last updated
In this video, we will:
walk through how to identify and fix the blank web3auth modal issue
discuss v2.0.1 of the Web3auth plugin and specifically how it impacts wallets generated and Torus access in near term (testnet wallets are not accessible via http://app.tor.us anymore whereas previously they were)
We will discuss why you get a "user with this email already exists" and the current way to resolve (delete that user and reconnect)
Which key to use for additional dev branches (Professional or Production bubble plans) Bubble will assume any non-dev branch is on mainnet so plan to use the mainnet key for non-Development dev branches (a bit confusing i know)
A second video walk-through for more rare connectivity issues, if you see no log-in even after Web3auth successfully connects:
Using the bubble debugger to identify misfiring conditionals
Using Data transfer from Live to Dev to populate Settings-Technical
Setting up the Admin wallet so you can access Admin Settings
Pointing to a new chain with Admin user
The official github Web3auth discussion around this can be found here:
