forked from LaconicNetwork/icns-frontend
Merge branch 'main' of https://github.com/interchain-name/icns-frontend into main
This commit is contained in:
commit
bbefba49c9
@ -31,3 +31,6 @@ export const TOO_MANY_CHAINS_IN_LEDGER_MESSAGE =
|
|||||||
export const EVM_CHAIN_IN_LEDGER_ERROR = "Ledger is unsupported for this chain";
|
export const EVM_CHAIN_IN_LEDGER_ERROR = "Ledger is unsupported for this chain";
|
||||||
export const EVM_CHAIN_IN_LEDGER_MESSAGE =
|
export const EVM_CHAIN_IN_LEDGER_MESSAGE =
|
||||||
"ICNS for Cosmos chains using Ethereum/EVM keys are not supported. Remove EVM-based Cosmos SDK chains and try again.";
|
"ICNS for Cosmos chains using Ethereum/EVM keys are not supported. Remove EVM-based Cosmos SDK chains and try again.";
|
||||||
|
|
||||||
|
export const LEDGER_MAX_REGISTER_ERROR =
|
||||||
|
"Data is invalid : JSON. Too many tokens";
|
||||||
|
@ -61,6 +61,7 @@ import {
|
|||||||
INVALID_REFERRAL_ERROR,
|
INVALID_REFERRAL_ERROR,
|
||||||
INVALID_REFERRAL_MESSAGE,
|
INVALID_REFERRAL_MESSAGE,
|
||||||
KEPLR_NOT_FOUND_ERROR,
|
KEPLR_NOT_FOUND_ERROR,
|
||||||
|
LEDGER_MAX_REGISTER_ERROR,
|
||||||
TOO_MANY_CHAINS_IN_LEDGER_ERROR,
|
TOO_MANY_CHAINS_IN_LEDGER_ERROR,
|
||||||
TOO_MANY_CHAINS_IN_LEDGER_MESSAGE,
|
TOO_MANY_CHAINS_IN_LEDGER_MESSAGE,
|
||||||
TWITTER_LOGIN_ERROR,
|
TWITTER_LOGIN_ERROR,
|
||||||
@ -510,7 +511,10 @@ export default function VerificationPage() {
|
|||||||
console.log(errorMessage);
|
console.log(errorMessage);
|
||||||
captureException(errorMessage);
|
captureException(errorMessage);
|
||||||
|
|
||||||
if (error.message.includes(TOO_MANY_CHAINS_IN_LEDGER_ERROR)) {
|
if (
|
||||||
|
error.message.includes(TOO_MANY_CHAINS_IN_LEDGER_ERROR) ||
|
||||||
|
error.message.includes(LEDGER_MAX_REGISTER_ERROR)
|
||||||
|
) {
|
||||||
setErrorMessage({ message: TOO_MANY_CHAINS_IN_LEDGER_MESSAGE });
|
setErrorMessage({ message: TOO_MANY_CHAINS_IN_LEDGER_MESSAGE });
|
||||||
setErrorModalOpen(true);
|
setErrorModalOpen(true);
|
||||||
return;
|
return;
|
||||||
|
Loading…
Reference in New Issue
Block a user