send_message event stopped working
See original GitHub issueIt is still something to be confirmed, but I can see that both send_message and send_scheduled_message does not work anymore.
These hooks are now never triggered:
this.gmail.observe.before("send_message", (url: string, body: string, data: Mail) => {});
this.gmail.observe.before("send_scheduled_message", (url: string, _body: string, data: Mail) => {});
Browser differences
- Works fine in Firefox
- Does not work in Chrome (with the same Google account)
I can see there is different parameters passed in URL - Chrome v105
Firefox v104

I am trying to investigate if it is payload or something…
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:22 (10 by maintainers)
Top Results From Across the Web
Sendmessage not working properly inside of a method definition
SendMessage () worked on WM_LBUTTONUP when it was not used inside of a class method. However, once I called SendMessage() from a class...
Read more >Send Message Event not working when posted via REST API
We are posting a message event via REST API, and want any snapshot version to handle it via correlation variable, hence we omit...
Read more >Message Received Not Working · Discussion #2152 - GitHub
My MessageReceived is not working for no reason at all. Is there any way that Messagereceived does not work? I think I initialized...
Read more >SendMessage function (winuser.h) - Win32 - Microsoft Learn
The SendMessage function calls the window procedure for the specified window and does not return until the window procedure has processed ...
Read more >system.perspective.sendMessage not triggering Session ...
So i am trying to set session properties via a system.perspective.sendMessage call. ... Why does this seem to not work, but if i...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Some users reports that older algorithm is back and older version of my extension works fine…
Hello! It seems that
parse_sent_message_payloadis fixed as well now, andparse_sent_message_payload_newhas incorrectsubjectfield index (should be 7, but there is 8).I believe that
parse_sent_message_payload_newcould be removed in favor of recently updatedparse_sent_message_payload.UPD: just discovered that incorrect index was fixed in #726. 🙂 But I still think that removing duplicated code is good, as long as
parse_send_message_payloadwas fixed in 9d4ff11327df06363df3576c12368d4e762b7017.