Torus-embed v6 and v5

[yatatay]

Hey there.
I’m using Torus-embed.
I’ve tried Torus-Embed v6.0.0 and WS-Embed v5.0.17.

but, I’ve noticed that when torus-embed fails to open window, there’s no fallback notification at v6. I believe that notification is an important feature for a better user experience.

Is there a way to display a fallback notification in v6? Or should I continue using v5 to retain this functionality?

[w3abot]

Thanks for the detailed context and screenshot!

Summary of your question:

• You’re using Torus-embed v6.0.0 and previously used v5.0.17.
• In v5, when the Torus window fails to open, a fallback notification is shown to the user.
• In v6, this fallback notification is missing, and you want to know if there’s a way to restore this in v6, or if you should stick with v5 for this feature.

SDK Details:

• SDK: Torus-embed (Plug n Play)
• Versions: v5.0.17 (works as expected), v6.0.0 (missing fallback notification)
• Platform: Not explicitly mentioned, but likely web (browser) based on SDK choice and screenshot.

Issue:

• In Torus-embed v6, there is no fallback notification when the popup window fails to open (e.g., due to popup blockers), which degrades user experience compared to v5.

---

Guidance & Next Steps

1. Behavior Change in v6

It appears that the fallback notification feature was either removed or not implemented in v6. This is a regression in user experience, as you noted.

2. Workaround/Proposed Solution

• Manual Handling:
  In v6, you may need to manually detect if the popup failed to open and show your own notification. Typically, Torus-embed exposes events or error callbacks you can use for this. Check if the login() or related methods return an error or reject a promise when the popup fails, and display a custom notification in that case.
• Check Documentation:
  The Torus-embed v6 migration guide and the API reference may have details on error handling or events you can hook into.
• Fallback Example:

  try {
    await torus.login();
  } catch (error) {
    // Check for popup blocked error
    if (error.message.includes('popup')) {
      // Show your own notification to the user
      alert('Popup was blocked. Please enable popups and try again.');
    }
  }
  

• Feature Request:
  If you prefer the built-in fallback notification, you can request this feature to be reintroduced in v6 by opening a GitHub issue or posting on the Web3Auth Community Forum.

3. Should You Downgrade?

• If the fallback notification is critical and you don’t want to implement your own, you may want to stay on v5 until v6 adds this feature or provides an equivalent hook.

---

Action Items for Support Team

• Confirm if fallback notification was intentionally removed in v6.
• Suggest if there’s an official workaround or upcoming fix.
• Consider this as a feature request if not already tracked.

---

References:

• Torus-embed v6 Migration Guide
• Torus-embed API Usage

If you need help with a code snippet for manual fallback, let me know your integration details and I can provide an example!

Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.

Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours