[Bug]: Premature close

[Aliceonly]

Describe the bug

When modify the network config and then metamask can't connect the network through the rpc url,
it leads metamask can't open and always get the Premature close
Cannot destructure property 'chainId' of '(0 , t.useSelector)(...)' as it is undefined.

Expected behavior

No response

Screenshots/Recordings

No response

Steps to reproduce

1. Swith to a network metamask can't connect
2. switch network
3. can't open metamask anymore

Error messages or log output

Error#17: Premature close scripts/sentry-install.js:1

TypeError: Cannot destructure property 'chainId' of '(0 , t.useSelector)(...)' as it is undefined.
  at z (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-2.js:1:857888)
  at ga (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-6.js:1:61316)
  at Cs (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-6.js:1:106147)
  at Au (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-6.js:1:92055)
  at Ou (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-6.js:1:91980)
  at Tu (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-6.js:1:89328)
  at vu (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-6.js:1:86072)
  at al (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-6.js:1:113703)
  at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-6.js:1:114902
  at xu (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-6.js:1:89679)
  at dl (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-6.js:1:114887)
  at render (chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/common-6.js:1:116810)
  at chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/ui-6.js:1:54554

Detection stage

In production (default)

Version

latest

Build type

None

Browser

Chrome

Operating system

MacOS

Hardware wallet

No response

Additional context

No response

Severity

fatal

[Aliceonly]

I try update serveral version but still have this bug

[Aliceonly]

console log: MetaMask - RPC Error: Cannot destructure property 'chainId' of 'this.networkController.getNetworkConfigurationByNetworkClientId(...)' as it is undefined.

[Aliceonly]

try call js api wallet_switchEthereumChain & wallet_addEthereumChain also get {
"code": -32603,
"message": "Cannot destructure property 'chainId' of 'this.networkController.getNetworkConfigurationByNetworkClientId(...)' as it is undefined.",
"data": {
"originalError": {}
}
}

[anaamolnar]

Hello, @Aliceonly, The team is working on identifying the root cause of this. In the meantime, could you trigger a network switch from chainlist.wtf to see if you can unblock the extension? Thank you!

[Sentini14]

Yes please can you give me a link for chain list ***@***.***

…

On Mon, Aug 5, 2024 at 8:16 AM Ana M. ***@***.***> wrote: Hello, @Aliceonly <https://github.com/Aliceonly>, The team is working on identifying the root cause of this. In the meantime, could you trigger a network switch from chainlist.wtf to see if you can unblock the extension? Thank you! — Reply to this email directly, view it on GitHub <#26326 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATS7JMQLVXAEB2V5IV5ACHTZP4RDPAVCNFSM6AAAAABL42K5NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGM2DEOBWGY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Aliceonly]

Hello, @Aliceonly, The team is working on identifying the root cause of this. In the meantime, could you trigger a network switch from chainlist.wtf to see if you can unblock the extension? Thank you!

not work. the extension totally blocked by the error. I even tried call the js api in console, not work

[Sentini14]

Ok, I will try.

…

On Mon, Aug 5, 2024 at 10:20 AM Abel ***@***.***> wrote: Hello, @Aliceonly <https://github.com/Aliceonly>, The team is working on identifying the root cause of this. In the meantime, could you trigger a network switch from chainlist.wtf to see if you can unblock the extension? Thank you! not work. the extension totally blocked by the error. I even tried call the js api in console, not work — Reply to this email directly, view it on GitHub <#26326 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATS7JMQZRTJQG2XJET2Q44LZP47VNAVCNFSM6AAAAABL42K5NKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRYGU4DKMRQGI> . You are receiving this because you commented.Message ID: ***@***.***>

[Sentini14]

How can I see my real public phrase key secret place

[Gudahtt]

I suspect that this crash will no longer happen in v12.0.1, but the circumstances leading up to that crash probably are still possible, and would still be considered a bug.

@Aliceonly could you clarify how you were able to reproduce this problem? I am having trouble with these steps. I have tried switching to an unavailable network, but I don't see any crash and MetaMask doesn't get stuck. I just see that the balance loads infinitely, or a loading overlay appears that eventually lets me switch back.

Also, let us know if this is still a problem on v12.0.1. Thanks!

[Aliceonly]

I suspect that this crash will no longer happen in v12.0.1, but the circumstances leading up to that crash probably are still possible, and would still be considered a bug.

@Aliceonly could you clarify how you were able to reproduce this problem? I am having trouble with these steps. I have tried switching to an unavailable network, but I don't see any crash and MetaMask doesn't get stuck. I just see that the balance loads infinitely, or a loading overlay appears that eventually lets me switch back.

Also, let us know if this is still a problem on v12.0.1. Thanks!

thx for ur reply and supporting
I tried v12.0.1, the indefinite crush seems to be fixed

It seems metamask handles the error properly now, the error not lead to premature close now

the reproduction steps in v12.0.0:
I'm not sure this situation happens all the time, but it happened several times on me

1. add a network with public rpc, and switch to it (it's Arbitrum Sepolia for me)
2. now metamask maybe the balance loads slowly, or not connected yet
3. go to settings and modify the network u r on to private rpc url (for me it's Alchemy RPC of arb sep)
4. back to the account page, metamask no longer connects arb sep and crush infinitely

[Gudahtt]

Thanks! Hmm, this sounds similar to #26072 but the repeated errors make me unsure. And with #26072 we never saw a crash, even before v12.0.1. We will investigate further.

[Gudahtt]

OK, so I believe I know what's happening now. The crash was caused by #26320, that has been resolved.

The errors that caused the crash, and are still causing these console errors, are tracked already in these issues:

• [Bug]: Adding custom RPC URL results in 'Error: No custom network client was found with the ID' #26072 (for the network form error; I know your case was an edit rather than an add, but we're covering both issues here)
• [Sentry] Error: networkConfigurationId [UUID] does not match a configured networkConfiguration or built-in network type #26309 (for the state corruption resulting from that form)

I will close this issue for now, as it should be resolved in the next release as we fix those remaining two issues. Thanks very much for the report though, and let us know if you still see this in v12.0.5 or later versions!

[Aliceonly]

OK, so I believe I know what's happening now. The crash was caused by #26320, that has been resolved.

The errors that caused the crash, and are still causing these console errors, are tracked already in these issues:

• [Bug]: Adding custom RPC URL results in 'Error: No custom network client was found with the ID' #26072 (for the network form error; I know your case was an edit rather than an add, but we're covering both issues here)
• [Sentry] Error: networkConfigurationId [UUID] does not match a configured networkConfiguration or built-in network type #26309 (for the state corruption resulting from that form)

I will close this issue for now, as it should be resolved in the next release as we fix those remaining two issues. Thanks very much for the report though, and let us know if you still see this in v12.0.5 or later versions!

thx u guys too, hope it's getting better & better