Welcome to One2all
  • 🎉First Time Setup Video Walkthrough
  • ➡️One2all v5 Guide
    • 🔧Recent Fixes/Deployments
    • ⭐Bubble Basics (for web3)
    • 🔌Setting up One2all v5 Bubble Plugins
    • ⚡How to set up your NFT Marketplace
    • 🤜For O2A Partners: How to Import the Latest Version of the app
  • 🏅v4+ Troubleshooting Common Issues, Best Practices and Walkthroughs
    • 🔧Issue with logo not appearing on index and header
    • 🎯How to fix ipfs base url issues for existing NFT's
    • 👨‍🎓Understanding the NFT /Item Page
    • 🏅One2all Customization Best Practices
    • 🌈Troubleshooting Styles and Hard-to-Find Formats
    • 🐛How to debug a blank Web3auth Modal and other Connectivity Issues
  • 📣v4+ Patch Change Tracking and Update History
    • 🩹v4.1.1 - Issue with social links not showing in /account page
    • 🔗v4.1.2 - updated default IPFS link to web3 storage public gateway
    • 🚒v4.1.3 Fixing Ramp URL and improving Ramp Button
    • 🎉v4.2 Feature Release and Video Walkthrough
    • 🛩️v4.2.1 small update with password reset workflow
  • ⭕Back to One2all.io
Powered by GitBook
On this page
  1. v4+ Troubleshooting Common Issues, Best Practices and Walkthroughs

How to debug a blank Web3auth Modal and other Connectivity Issues

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

PreviousTroubleshooting Styles and Hard-to-Find FormatsNextv4+ Patch Change Tracking and Update History

Last updated 2 years ago

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:

🏅
🐛
Web3auth for new SDK seems to be generating wallets that no longer show up in torus · Web3Auth · Discussion #1249GitHub
Logo