You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 3, 2024. It is now read-only.
When using a custom network the snap returns an error: Invalid configuration schema - Network name should be provided even though a network name was specified.
Please check version of the installed metamask snap, that si bug from older version of snap.
My guess, its installed from metamask snap store which now still installs older version.
Hey @irubido, hope you are doing well! Just following up on that, it's been almost a month since the Github 0.9.0 release but the snap store is still at 0.8.2, is the audit expected to take that long?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When using a custom network the snap returns an error:
Invalid configuration schema - Network name should be provided
even though a network name was specified.When connecting from a DApp the snap appears to still work anyway but the error still appears in the console.
E.g: https://pioneer-2-git-feature-metamask-snap-joystream.vercel.app
However when I run the snap locally or publish it myself this does not happen.
Is this the expected behavior for the published version of the snap ? If so could the error be more explicit ?
The text was updated successfully, but these errors were encountered: