Sometimes (~50% of time) after entering given realm's details for the first time since reloading the page, there are some warnings/errors in the logs:
Access to fetch at 'https://resolve.unstoppabledomains.com/domains/?owners=0x277c1d7a4c4dd06733f19904d88c7f7fe3925b86&sortBy=id&sortDirection=ASC' from origin 'https://stage-live--taho-development.netlify.app' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.
GET https://resolve.unstoppabledomains.com/domains/?owners=0x277c1d7…&sortBy=id&sortDirection=ASC net::ERR_FAILED 308 (Permanent Redirect)
GET https://resolve.unstoppabledomains.com/domains/?owners=0x200d2172fa4d6a1ae4a9e568ea4e749dd7a9ee7c&sortBy=id&sortDirection=ASC net::ERR_FAILED
react-spring_shared.modern.mjs:930 react-spring: Directly calling start instead of using the api object is deprecated in v9 (use ".start" instead), this will be removed in later 0.X.0 versions
The errors are failed names resolution (not sure if the last warning also is for the same reason).
Does not happen always for the sam realms.
Sometimes (~50% of time) after entering given realm's details for the first time since reloading the page, there are some warnings/errors in the logs:
The errors are failed names resolution (not sure if the last warning also is for the same reason).
Does not happen always for the sam realms.