Status Update
Comments
ga...@google.com <ga...@google.com> #2
Hi there!
Thank you for reporting this behaviour. I have been able to reproduce this in my test environment and so have filed it internally.
Many thanks!
ja...@google.com <ja...@google.com>
ga...@google.com <ga...@google.com> #3
Hi there!
I just wanted to get back to you regarding this. I followed your reproduction steps and I actually did receive the emails as the non-Calendar user in my test environment. There was however, a delay of three hours between sending and receiving the notifications, and the messages had also been passed to the spam folder.
Can I please confirm if this was also the case for you?
Many thanks!
[Deleted User] <[Deleted User]> #4
the calendar-api also doesn't work when using the api explorer or the current node.js-lib for inserting/patching events. Non-gmail-accounts don't get the invite, even after several hours have passed. B/c no invite gets sent, the calendar event doesn't even show up at those account. This practically makes the whole calendar api useless.
Thanks for all your hard work, but this severe bug is practically blocking the release of one of the services I'm working on which heavily relies on scheduling events with various attendees.
ga...@google.com <ga...@google.com> #5
Hi there!
I am closing this issue due to inactivity, as I was not able to reproduce this, and have not received a response. If you are still encountering this behaviour, please feel free to open a new issue.
Many thanks!
fl...@gmail.com <fl...@gmail.com> #6
It is still reproducible with the Google API explorer (url-encoded is the setting I was using):
No notification gets sent to
If this isn't the right place to post the issue, please tell me where.
pu...@gmail.com <pu...@gmail.com> #8
I am able to reproduce the issue. I tried the Event Insert API from
and marking the sendNotifications as True and sendUpdates as all , the event got created in my calendar but still m not receiving any email for the event created (gmail account).
these parameters are not working for sending emails. It's a bug.
Please have a look.
Thank you
[Deleted User] <[Deleted User]> #9
please make sure the calendar entry's dates are >= the present date, else no invite gets sent out. I had the same issue but figured you have to use an "active" date. In hindsight it makes absolutely sense that no invite gets send out for past calendar entries. This is not a bug, but the documentation could be enhanced by mentioning it.
gu...@cfssinc.com <gu...@cfssinc.com> #10
It should be part of the query parameters options, instead of part of the event object.
Calendar.Events.insert(event, calendar, {'sendNotifications':true})
got it done for me.
By the way, the Google Calendar API Reference makes this clear, but I still missed it initially. Also, I realize the initial poster in this thread has it listed correctly, but thought my comment might help some other dolt like me who wasn't building the query carefully...
pu...@gmail.com <pu...@gmail.com> #11
I am trying the Google Calendar API for Event:insert and not providing the past date in calendar , sendNotifications: True, but still did'nt receive any email invitation.
fl...@gmail.com <fl...@gmail.com> #12
Have you set sendUpdates
to all
? Also, if no calendar was created by you where you know the ID, make sure to use primary
for calendarId
. I just tested an example in the API Explorer + with the Node.js-lib and it works as expected.
ga...@google.com <ga...@google.com>
pu...@gmail.com <pu...@gmail.com> #13
av...@gmail.com <av...@gmail.com> #14
Getting the same issue even if senUpdates:"all" & senNotifications:true.
[Deleted User] <[Deleted User]> #15
I'm facing the same issue. @google Please solve it.
[Deleted User] <[Deleted User]> #16
I'm facing the same issue. @google Please solve it.
[Deleted User] <[Deleted User]> #17
It works well with google-api-client:1.23.0 Try passing sendUpdates = 'all' instead of true/false.
I am able to get email notification for same day events too
ot...@gmail.com <ot...@gmail.com> #18
ch...@gmail.com <ch...@gmail.com> #19
Upon Events.insert, even with **sendUpdates** or the old **sendNotificiations** set accordingly according to the documentation here:
I still do not observe any email or notification being sent upon the creation of the Calendar event. Help?
ya...@gmail.com <ya...@gmail.com> #20
an...@gmail.com <an...@gmail.com> #21
The parameter sendUpdates must be on the url, NOT ON THE BODY.
The url I use for create events and notify attendees is:
And the body:
{
"end": {
"dateTime": "2022-08-04T17:00:00-04:30"
},
"start": {
"dateTime": "2022-08-04T16:00:00-05:30"
},
"summary": "Test event",
"description": "This is a test description of the event",
"attendees":[{"email": "fakeemail@gmail.com"}]
}
Hope this helps!
id...@deeto.ai <id...@deeto.ai> #23
ar...@cgg.be <ar...@cgg.be> #24
Ik have a project where registrations arrive via a Google form. A confirmation email will be automatically sent with confirmation of registration.
After that, an agenda appointment is made and the tenderer is added to it. --> This works!
However, an invitation from the calendar is no longer sent. This works when i made the forms. (i'm an administrator)
I am thinking of certain rights of the account with which it is now used, but everything is fine according to me. I also don't get an error. Just resetted the rights for the user, but still not works
const verstuurUitnodiging = (calendarId, eventId, email) => {
try {
let event = Calendar.Events.get(calendarId, eventId);
if (event.attendees) {
event.attendees.push({
email: email
});
} else {
event.attendees = new Array({ email: email });
}
event = Calendar.Events.patch(event, calendarId, eventId, {
sendUpdates: "all"
});
}
catch (error) {
console.log('Foutmelding versturen uitnodiging agenda: ' + error.message);
}
}
zr...@gmail.com <zr...@gmail.com> #25
ma...@recruitcrm.io <ma...@recruitcrm.io> #26
di...@discuss.io <di...@discuss.io> #27
We're using the google/apiclient v2.12.6 for PHP and are appending the sendUpdates option on the insert command like so:
$createdEvent = $this->_cal->events->insert($this->_cal_id, $event, [
'sendUpdates' => 'all'
]);
Any information on how to remedy this would be amazing as our API metrics report no errors, rate-limiting, or issues with our quotas and our logs/calendars only show successful creation events.
m....@gmail.com <m....@gmail.com> #28
al...@byldd.com <al...@byldd.com> #29
You are passing the sendUpdates all in body but you should pass in the query parameter. Refer to this url.
ba...@gmail.com <ba...@gmail.com> #30
Yes, the sendUpdates is send as a query parameter in the url: ?sendUpdates=all
But only the external addresses are receiving notification emails
su...@skwish.app <su...@skwish.app> #31
It fails to send notifications, which means that the other attendees don't see the updates, which is horrible if the time of the event changes (for example, when an attendee has Modify Event permissions). This is a terrible bug.
Description
Creating events with the advanced calendar, invitation emails are not sent to guests regardless of values for 'sendNotifications' or 'sendUpdates'.
A small code sample that reliably reproduces the issue. The sample should run as-is or with minimal setup, without external dependencies.
```
function testMail() {
var calendarId = 'someId';
var eventId = 'anotherId';
var event = Calendar.Events.get(calendarId, eventId);
event.attendees.push({
email: 'test@example.com'
});
event = Calendar.Events.patch(event, calendarId, eventId, {
sendNotifications: true,
sendUpdates: 'all'
});
}
```
What steps will reproduce the problem?
1. Create or patch a calendar event with an external email address as an attendee. Include 'sendUpdates: "all"' in the options object.
2. Check your external mail.
What is the expected output? What do you see instead? If you see error messages, please provide them.
Expected: The external mail account should receive an invite email for the new/updated event.
Instead: The event is created, attendees are registered on the event, but external email addresses do not receive invitations.
Please provide any additional information below.
It's possible this is a permission scopes problem, which needs to be either auto-detected or added to the documentation. I've tried with the following scopes applied:
"oauthScopes": ["