api.tools.parse_actions doesn't work with new gmail interface
See original GitHub issueI noticed that observer doesn’t work with new GMail interface. I added some console.log
and noticed that responses are in format, different from expected in api.tools.parse_actions
. Could somebody fix that? I tried to decode Gmail responses myself, but with no result, they are very ugly and unreadable
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (6 by maintainers)
Top Results From Across the Web
Learn about the new integrated Gmail layout - Google Support
Gmail has a new integrated view to organize Mail, Chat, Spaces, and Meet in one place. With the new layout, you can: View...
Read more >Gmail API Overview - Google Developers
The Gmail API is a RESTful API that can be used to access Gmail mailboxes and send mail. For most web applications the...
Read more >Gmail API not returning correct emails compared to Gmail web ...
The web ui looks correct whereas the api returns emails from the next day (20th). Possibly a timezone conversation problem?
Read more >KartikTalwar/gmail.js: Gmail JavaScript API - GitHub
Note: This is not an official Gmail API, and isn't affiliated with Google. ... Create an issue/pull request for feedback, requests and fixes....
Read more >Using the Zoom for Gmail add-on
The Gmail add-on is not currently compatible with iOS. You can also use the Zoom for Google Workspace add-on to schedule Zoom meetings...
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
New Gmail not being fully supported? It is known.
New Gmail breaks quite a lot of things. Fully supporting new Gmail is a ongoing effort.
Some code has already been committed and release in 0.7.0 to ensure a minimal amount of compatibility (like not crashing).
Right now event-observers are on top of my priority-list too, since that’s the only remaining thing broken in my extension (after the other updates I’ve applied).
Hopefully more fixes and commits will come as we reverse engineer some of the new XHR formats used.
If you find some other things you depend on not working, I advice you to try to resolve the issue yourself, and submit PRs to get your patches mainlined.
We don’t really tag releases in source-code. If you need a specific version, check for when we bump-versions (post release) in
package.json
.Currently, as of right now, 0.7.1 is git master.