Script suddenly stopped notifying

[Niehztog]

I noticed that I no longer receive notifications about my contacts birthdays. I used this script for years before and never had any problems. It just suddenly stopped notifying.

Once I opened script.google.com and navigated to the script I got a notification saying that the script automatically got migrated to "V8". I am running the latest version (5.1.4). I then checked the permissions as described here. I had to remove the deprecated Contacts API permission and add the People API. But the script still does not work. I've set the test date setting multiple times to different days of my contact's birthdays and executed the test() function. It always outputs "I: No events found. Exiting now.".

In calendar.google.com I noticed that the contacts birthdays no longer appear in the calendar, even though the Contact Calendar is activated and shown.

Does anyone else have the same issue? Any ideas how to debug this?

[edit]
The first link in the installation instructions leads to this google help page. I noticed on top of this page the following notice which might explain why my birthdays went missing. Can anyone confirm?

[Toasbi]

Same issue here...

I got an email from google some time ago though:

Hello Google Developer,

We are writing to inform you about upcoming changes to the Google Calendar API v3 that may impact your applications and notification handling, starting March 11, 2024.

What does this mean for your organization?
The Google Calendar API v3 will now include the eventType parameter to subscribe to specific event types when using Events.Watch. Additionally, starting March 11, 2024, the following changes will be introduced:

Default event type filters alignment for both Events.list and Events.watch.
Error handling for operations not supported for special event types, such as WorkingLocation, Out of Office, and FocusTime events.
What do you need to do?
To prevent any direct impact in your applications, we strongly encourage you to review your usage of the applications listed below and take the following actions:

Events.watch: Specify the event types you need for your application as a parameter to reduce your infrastructure costs. In case you want to request a quota increase, please make sure you have implemented event type filters appropriately. This factor will be considered when we are evaluating quota increase requests.
Events.list: Specify the event types you need for your application as a parameter. Without making this change, working location events will start to be returned.
Event type: If your code is performing operations on special events, it is important to review it to ensure that your code does not attempt to perform operations not supported for special event types.

[plainerman]

Thank you for reporting this issue!

I got this mail recently:

Hello Google Developer,

We are writing to inform you about upcoming changes to the Google Calendar API v3 that may impact your applications and notification handling, starting March 11, 2024.

What does this mean for your organization?

The Google Calendar API v3 will now include the eventType parameter to subscribe to specific event types when using Events.Watch. Additionally, starting March 11, 2024, the following changes will be introduced:

Default event type filters alignment for both Events.list and Events.watch.
Error handling for operations not supported for special event types, such as WorkingLocation, Out of Office, and FocusTime events.

What do you need to do?

To prevent any direct impact in your applications, we strongly encourage you to review your usage of the applications listed below and take the following actions:

Events.watch: Specify the event types you need for your application as a parameter to reduce your infrastructure costs. In case you want to request a quota increase, please make sure you have implemented event type filters appropriately. This factor will be considered when we are evaluating quota increase requests.
Events.list: Specify the event types you need for your application as a parameter. Without making this change, working location events will start to be returned.
Event type: If your code is performing operations on special events, it is important to review it to ensure that your code does not attempt to perform operations not supported for special event types.

Maybe this is the reason? The dates where these changes have been introduced would align with these issues.

Especially this seems suspicious:

Event type: If your code is performing operations on special events, it is important to review it to ensure that your code does not attempt to perform operations not supported for special event types.

Anybody willing to invest time to look into this? Have my hands full right now.

EDIT:
I am pretty confident that v8 has nothing to do with it, fixed that a while back.

[Niehztog]

I managed to fix this issue in a suprisingly easy way:

• Go to https://myactivity.google.com/linked-services?hl=de&utm_source=google-account&utm_medium=web&continue=https%3A%2F%2Fmyaccount.google.com%2Fdata-and-privacy

• Check "Contacts" to make sure that Google Contacts data may be shared with other google services like Calendar

Now the birthdays are appearing again in my callendar and notifications seem to work.

[Toasbi]

I managed to fix this issue in a suprisingly easy way:

• Go to https://myactivity.google.com/linked-services?hl=de&utm_source=google-account&utm_medium=web&continue=https%3A%2F%2Fmyaccount.google.com%2Fdata-and-privacy
• Check "Contacts" to make sure that Google Contacts data may be shared with other google services like Calendar

Now the birthdays are appearing again in my callendar and notifications seem to work.

Thanks @Niehztog , that fixed it for me as well!

[plainerman]

Updated the installation to include this step. Thank you for your help @Niehztog !

[Rabattkarte]

I stumbled upon this change at random, since the script did not notify me. I am wondering how many users are out there that also had the feeling of. "Hmmmm... it's weird that my emails stopped working coming in".

Maybe we can notify the users of this mandatory change somehow? I am not sure if bumping the Patch version might help here, since no emails are coming in. 🤔

[plainerman]

@Rabattkarte that's a great idea, but I don't think there is a way to notify the users.
Bumping the version number would simply append a footer that the script is outdated. Since no emails are sent, I don't see how this could help.

I can add a short statement to the readme, but otherwise I am not sure what we can do for now. Happy to hear any ideas.