This section covers common FAQ’s and how to solve them.
Ensure you have enabled the chains in the dashboard. It can sometimes happen that you missed enabling a chain in the dashboard, or did it for a different environment than the one you are testing in. Check the chains and networks tab to be sure.
Ensure you have enabled the wallet connectors for the chains you want to show. Double check that you have added the right wallet connectors in your Dynamic Context Provider.
Ensure you are not encountering a CSP issue.
Check for any errors like “Refused to connect because it violates the document’s Content Security Policy.” in your console/networks tab, it means you need to add dynamic-static-assets.com
to your server CSP.
Set a custom RPC URL in code, or in the Dynamic Dashboard (when you enable a network, there is a dropdown to set your own RPC URL).
You can control how users connect on mobile devices using the mobileExperience
prop. You can set it globally or per wallet:
You can control how the SDK enforces wallet networks using the networkValidationMode
prop. Available options are:
'always'
- requires the wallet to be on an enabled network while connecting and during the session'sign-in'
- only enforces the network on connect'never'
- turns off network validationThe easiest way to hide something is to use custom CSS directly.
This commonly happens when you have not set enableVisitTrackingOnConnectOnly to true.
You can change the order of your social login options by using the socialProvidersFilter
prop. This is a function that takes an array of social providers and returns a new array with the providers in the order you want.
The social
prop on the DynamicContextProvider
take a strategy
field whose value can be set to 'redirect'
or 'popup'
.
Use the tokenFilter prop on the DynamicContextProvider
Stay on sandbox while in testing, when you are ready to launch to your first users, move to Production. Remember that Production comes with a blank slate of settings, and a new environmentId, so don’t forget to update them.
This section covers common FAQ’s and how to solve them.
Ensure you have enabled the chains in the dashboard. It can sometimes happen that you missed enabling a chain in the dashboard, or did it for a different environment than the one you are testing in. Check the chains and networks tab to be sure.
Ensure you have enabled the wallet connectors for the chains you want to show. Double check that you have added the right wallet connectors in your Dynamic Context Provider.
Ensure you are not encountering a CSP issue.
Check for any errors like “Refused to connect because it violates the document’s Content Security Policy.” in your console/networks tab, it means you need to add dynamic-static-assets.com
to your server CSP.
Set a custom RPC URL in code, or in the Dynamic Dashboard (when you enable a network, there is a dropdown to set your own RPC URL).
You can control how users connect on mobile devices using the mobileExperience
prop. You can set it globally or per wallet:
You can control how the SDK enforces wallet networks using the networkValidationMode
prop. Available options are:
'always'
- requires the wallet to be on an enabled network while connecting and during the session'sign-in'
- only enforces the network on connect'never'
- turns off network validationThe easiest way to hide something is to use custom CSS directly.
This commonly happens when you have not set enableVisitTrackingOnConnectOnly to true.
You can change the order of your social login options by using the socialProvidersFilter
prop. This is a function that takes an array of social providers and returns a new array with the providers in the order you want.
The social
prop on the DynamicContextProvider
take a strategy
field whose value can be set to 'redirect'
or 'popup'
.
Use the tokenFilter prop on the DynamicContextProvider
Stay on sandbox while in testing, when you are ready to launch to your first users, move to Production. Remember that Production comes with a blank slate of settings, and a new environmentId, so don’t forget to update them.