Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: createweb3dapp.alchemy.com client-side exception #105

Open
calebcgates opened this issue Nov 6, 2023 · 0 comments
Open

Error: createweb3dapp.alchemy.com client-side exception #105

calebcgates opened this issue Nov 6, 2023 · 0 comments

Comments

@calebcgates
Copy link

Describe the bug
The website https://createweb3dapp.alchemy.com loads for a split second then errors out.

To Reproduce
Steps to reproduce the behavior:

  1. Go to (https://createweb3dapp.alchemy.com)
  2. Wait 1 second
  3. Observe the error message Application error: a client-side exception has occurred (see the browser console for more information).

Has been recreated on both chrome and brave public and private browsers

Expected behavior
Ideally the website should stay visible so that users can explore the different components made available through the create-web3-dapp package

Screenshots
Screenshot 2023-11-06 at 12 38 12 PM

Desktop (please complete the following information):

  • OS: M1 Mac

  • Browser chrome

  • Version 118.0.5993.117 (Official Build) (arm64)

  • Browser brave

  • Version 1.46.138 Chromium: 108.0.5359.94 (Official Build) (arm64)

Smartphone (please complete the following information):

  • Device: Iphone15 pro
  • OS: iOS17.1
  • Browser Chrome
  • Version 119.0.6045.109 (Official Build) stable (64-bit)

Additional context
Some quick research says its probably a malformed loaded script. The time delay between the page loading and the error occurring leads me to believe that is correct. The script that takes longest to load in the network tab is "getComponentByName" which returns a client version rather than any sort of "NFT Gallery Component". Given that the error is triggered afterwards I'm curious if that is the source of error.

Screenshot 2023-11-06 at 12 26 52 PM
Screenshot 2023-11-06 at 12 29 52 PM

@Eversmile12

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant