need chrome manifest v3 expert. Problem to migrate v2 to v3 function "chrome.tabs.sendMessage."
Budget: $250 – $750 USD
I have a issue to migrate the function "chrome.tabs.sendMessage."
Below is my code.
chrome.tabs.sendMessage(tab.id, {
action: "MonitorInforChanged",
}, function (response) {
console.log(tab.id, chrome.runtime.lastError)
});
This function works in V2, but in V3 occurs below issue.
959
"Could not establish connection. Receiving end does not exist."
959 is tabs id.
This means the tab.id is valid.
If you know how to solve this, I will need you to communicate with my developer and work out a solution.
To show that you actually read this posting. Put the name of your favorite chrome extension as the first words in your bid. I need to see that you follow instructions. Do not put "my favorite is....", just put the name of the extension as the first words in your bid. This is critical and we will pay to solve this problem, even if it takes you 10 minutes, we just need it solved.
in addition, The chrome function chrome.runtime.connectNative worked in manifest v2, but it is not working in V3, we will need a solution for that as well. We will provide code to the selected bidder.
Below is my code.
chrome.tabs.sendMessage(tab.id, {
action: "MonitorInforChanged",
}, function (response) {
console.log(tab.id, chrome.runtime.lastError)
});
This function works in V2, but in V3 occurs below issue.
959
"Could not establish connection. Receiving end does not exist."
959 is tabs id.
This means the tab.id is valid.
If you know how to solve this, I will need you to communicate with my developer and work out a solution.
To show that you actually read this posting. Put the name of your favorite chrome extension as the first words in your bid. I need to see that you follow instructions. Do not put "my favorite is....", just put the name of the extension as the first words in your bid. This is critical and we will pay to solve this problem, even if it takes you 10 minutes, we just need it solved.
in addition, The chrome function chrome.runtime.connectNative worked in manifest v2, but it is not working in V3, we will need a solution for that as well. We will provide code to the selected bidder.