1

All "recipients" properties of the "draftMetadata" object passed into "onGmailCompose" stopped coming through (are now missing) on iOS (iPad and iPhone).

My Apps Script code was working perfectly for about a year, since Sep 30 2022. It has not been changed since that date. The last successful operation I can find in my logs took place on 2023-11-16 23:44.48 UTC The first evidence in my logs showing all calls beginning to fail is 2023-11-22 15:49.52 UTC so whatever was changed in between those above dates appears to have introduced this bug.
My logs show that there has not been any successful iOS operation since the last one on 2023-11-16 23:44.48 UTC

This issue occurs consistently on all iOS devices: Myself and 24 other (paying=P1) customers have tested this on at least 24 unique iPhones and iPads.

There has been no change to any of my apps script code, dependencies, or infrastructure since Sep 30 2022, and, it continues to work flawlessly on all other platforms besides iOS.

I am at wits end here: I've reported this bug more than a dozen times over the last 3 months, and every time I simply get 1 of two outcomes: no response whatsoever, or, google employees telling me I've reported it to the wrong department - followed by no further response.

I'm a paying workspace user, supposedly on a 4-hour response time, so I'm really not sure what to do now: what's the point of offering us support timeframes in hours, when nothing gets even looked-at for months (so far) ?

How to reproduce the problem:-

  1. Implement the below code in a gmail add-on Apps Script project.
  2. Compose a gmail and add a recipient using a web browser or android
  3. Click your add-on's button - observe that the code works OK, then
  4. repeat steps 2 and 3 on an iPhone or iPad - observe the newly-broken behavior as described above ( draftMetadata properties are missing on iOS only )
    function onGmailCompose(e,f) {
        if( e.draftMetadata && (!e.draftMetadata.toRecipients.length) && (!e.draftMetadata.ccRecipients.length) && (!e.draftMetadata.bccRecipients.length) ) { 
          // no recipients
          // [ snip ...]
        }

The above used to work perfectly (from 2022 up until 2023-11-16) on all platforms - including all web browsers (chrome/firefox/safari on windows/linux/mac) and (via the "gmail app" from its respective stores) all Androids (phones and tablets) and it used to also work on iPhones and iPads.

However now, on iPad and iPhone (latest versions) that line is always happening, even when recipients are specified. All other platforms still work fine.

A bug has been introduced into the Apple iOS "Gmail App" which incorrectly fails to populate the "draftMetadata" key passed into the onGmailCompose action.

The App I'm using has not been changed since publication (2022-09-30).

4
  • 1
    I can see that this issue has been raised through proper channels already at issuetracker.google.com. Commented Mar 22, 2024 at 0:52
  • 1
    Depends what you mean by "proper channels" - if you mean filing a bug, and watching for 3+ months as nobody whatsoever even looks at the problem, then yeah... This is posted here in the hope that an actual engineer from google might happen to be reading. As far as I can tell, the "triage" people are claiming "resolutions" on issues by marking them as "solution provided" when they add any kinds of comments, even though nobody is actually fixing the bug. The one thing I'm certain about: no actual google developers are reading submitted issues this year, probably because of that triage exploit. Commented Mar 23, 2024 at 1:08
  • Edit to link the tracker here as well. Commented Mar 23, 2024 at 3:18
  • 1
    @cnd The correct place would be Google workspace > Google Workspace addons, Currently component: 642720+ . See search component here. You can also add an answer with the tracker link for greater visibility on the issue. See sample answers stackoverflow.com/a/73854991 and stackoverflow.com/… Commented Mar 25, 2024 at 2:06

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.