[bug] Error in invocation of runtime.sendMessage

[0xbuidler]

Is there an existing issue for this?

• I have searched the existing issues

RainbowKit Version

2.2.5

wagmi Version

2.15.4

Current Behavior

Go to https://app.aave.com/, inspect the console. See the error:

Uncaught (in promise) TypeError: Error in invocation of runtime.sendMessage(optional string extensionId, any message, optional object options, optional function callback): chrome.runtime.sendMessage() called from a webpage must specify an Extension ID (string) for its first argument.

Same error happens in local.

Expected Behavior

I'm expecting to not have this error.

Steps To Reproduce

Go to https://app.aave.com/ and inspect the console.

Needs to have the Rainbow chrome extension ofc.

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)

No response

Anything else?

Chrome version: Version 137.0.7151.69 (Build officiel) (arm64)

[linear]

RK-162 [bug] <title> Error in invocation of runtime.sendMessage

[DanielSinclair]

This actually seems to be an issue on the wallet side. Does this occur for you on every dApp? Are you eventually able to successfully connect and sign transactions?

[josephbouassaf]

Hello, I am also getting the same issue (locally and in production). Every users that connects to my dApp with Rainbow wallet sees the above error in their console.

RainbowKit Version

2.2.4

wagmi Version

2.14.15

[zakariamouhid]

same error

here is the source of the error:

browser-extension/src/core/messengers/internal/tab.ts

Lines 23 to 32 in 16a6ea8

	function sendMessage<TPayload>(
	message: SendMessage<TPayload>,
	{ tabId }: { tabId?: number } = {},
	) {
	if (!tabId) {
	chrome?.runtime?.sendMessage?.(message);
	} else {
	chrome.tabs?.sendMessage(tabId, message);
	}
	}

[0xbuidler]

This actually seems to be an issue on the wallet side. Does this occur for you on every dApp? Are you eventually able to successfully connect and sign transactions?

@DanielSinclair Yes, it would seem that I can do everything. But when working in a dev env I get this error everytime I refresh and it's a nighmare.

Have you been able to figure out the issue ?

[0xbuidler]

@DanielSinclair Hello, this error kinda ruin the development experience on Next.js. I'd be very happy to help fix this if redirected into the right direction. Thank you 🙏

[0xbuidler]

Looks like it was first spotted in November 2023: #1117

[aspiers]

I get this too:

It's really bad for an extension to be spamming the console in this way:

1. It's very inconvenient as it makes it harder to spot genuine issues.
2. It gives the impression of a low quality product.

[0xbuidler]

Could you have a look at this when you have time pls @DanielSinclair ?