Can't send notification through service account calendar [140746812]

Assigned

Bug

Status Update

No update yet.

Description

as...@gmail.com

created issue #1

Sep 10, 2019 06:39AM

I'm using google calendar API using google service account from my server. I was able to send notifications for any event that was added or updated on the calendar.

Also, I shared the calendar with "normal" google account, so I can also add events to that calendar manually.

Recently i Noticed notifications are no longer sent from that calendar (which belongs to the google service account). Tried both by calling the API and manually using google calendar UI.

What i'm missing? Any recent changes to the calendar API can cause this?

Comments

ar...@gmail.com <ar...@gmail.com> #2Sep 10, 2019 07:29AM

Will be this fix also part of 4.2 please?

[Deleted User] <[Deleted User]> #3Sep 10, 2019 10:12AM

for the "out" bundle issue, this seems indeed an issue. for the second one reported adding "debugUpdateAPKArtifact" to the path, this WAI as there can more more than one transformer and we need to automatically separate them so they do not use the same output folder. for #3, I will look at it but it might be difficult to change it at this time.

li...@gmail.com <li...@gmail.com> #4Sep 10, 2019 10:16AM

I understand that if there is more transformer is necessary to make every folder different, but there is the main problem, that the final one (last transform) is inside of the intermediate folder. The last transformation should end in the standard location, right? Maybe also with the default name not?

[Deleted User] <[Deleted User]> #5Sep 10, 2019 10:17AM

Hello, this is a P1 S1 issue for a while now, and it's blocking us from upgrading to AGP 4.2 and further. What's the current status? And do you have plans to backport it to 4.2.x?

xu...@gmail.com <xu...@gmail.com> #6Sep 10, 2019 10:19AM

no we don't have a plan to backport this. why is this blocking you from upgrading ?

jo...@gmail.com <jo...@gmail.com> #7Sep 10, 2019 10:23AM

We sign apk's and bundles via internal service, and i don't know another way to interact with artifacts; Yesterday i ended up with some ugly workaround: https://github.com/avito-tech/avito-android/pull/1085/files#diff-b898cc20fedebe394439bb37ffb91d3366a1f9a6d359dbdebca79af8a079f911 I'd be glad if you'll point me out how can it be done better.

st...@whitecobalt.com <st...@whitecobalt.com> #8Sep 10, 2019 04:08PM

I commented on the merge request but to summarize :

you can set your signing tasks output folder to wherever you need to be :

artifacts.use(target.tasks.signedApkTaskProvider(this)).configure { signedDirProperty.set(File("/path/to/where/you/want/your/signed/files")) }

if you don't set it, then we will set a directory automatically.

gm...@gmail.com <gm...@gmail.com> #9Sep 10, 2019 07:20PM

Thanks, Jerome!

ma...@allos.it <ma...@allos.it> #10Sep 11, 2019 07:21AM

I checked that we do have correct behavior for FILE based artifacts like bundle :

> Task :app:debugUpdateArtifact
originalArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/intermediates/bundle/debug/signDebugBundle/app-debug.aab
updatedArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/bundle/debug/app-debug.aab

however, we still seem to not be consistent for the DIRECTORY based artifacts like APK:

> Task :app:debugUpdateAPKArtifact
Input folder: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/apk/debug
Output folder: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/intermediates/apk/debug
Input file: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/apk/debug/app-debug.apk

Alex, can you have a look ?

as...@gmail.com <as...@gmail.com> #11Sep 12, 2019 06:30AM

correction, I was not correct about FILE being correct.

Instead of :

updatedArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/bundle/debug/app-debug.aab

it should be

updatedArtifact: /usr/local/google/home/jedo/src/studio-main/out/apiTests/Kotlin/bugTest/app/build/outputs/app-debug.aab
``

nv...@gmail.com <nv...@gmail.com> #12Sep 12, 2019 01:51PM

Two requests are created as they are API changes b/241581686 (set artifact name for transformation) and b/241582907 (change string to OutputFile)

Message last modified on Sep 12, 2019 01:53PM

pi...@gmail.com <pi...@gmail.com> #13Sep 12, 2019 02:01PM

Fix will be available in Android Studio F/AGP 8.0 Canary 2 Release

dd...@frata.io <dd...@frata.io> #14Sep 12, 2019 02:03PM

I tried to use it and at first look, it looks like everything works as expected. Thanks!

sa...@gmail.com <sa...@gmail.com> #15Sep 12, 2019 02:06PM

The big issue is, that the current AGP 7.4.0 is broken. I tried to use this API and it is still broken in 7.4.0, it is probably really in AGP 8 :-(

ma...@allos.it <ma...@allos.it> #16Sep 13, 2019 12:53PM

I need this fix.

ar...@gmail.com <ar...@gmail.com> #17Sep 13, 2019 03:25PM

Google please fix it!!!

as...@gmail.com <as...@gmail.com> #18Sep 15, 2019 01:43AM

This is affecting calendar events created from my service accounts too. The events exist correctly in my service account, but they are not being sent out to the attendees on the invites.

si...@dudgeon.fi <si...@dudgeon.fi> #19Sep 15, 2019 07:48PM

Same for me

fa...@gmail.com <fa...@gmail.com> #20Sep 16, 2019 12:57PM

Same

Message last modified on Sep 16, 2019 12:57PM

fa...@gmail.com <fa...@gmail.com> #21Sep 16, 2019 12:58PM

Fix it

Message last modified on Sep 16, 2019 12:58PM

fa...@gmail.com <fa...@gmail.com> #22Sep 16, 2019 12:59PM

Same for me.
I think this bug is related to the fact that Google is fighting against people who are trying to spam the calendars, I hope they will solve the issue soon..

sa...@gmail.com <sa...@gmail.com> #23Sep 17, 2019 12:14PM

This is getting rather urgent now, can someone from Google please take a look?

ma...@allos.it <ma...@allos.it> #24Sep 19, 2019 08:01AM

Are there news? Someone from Google?

Message last modified on Sep 19, 2019 08:01AM

ar...@gmail.com <ar...@gmail.com> #25Sep 24, 2019 03:08PM

any news?

dr...@googlemail.com <dr...@googlemail.com> #26Sep 26, 2019 07:10PM

This is affecting a scheduling app: a service account can create events without any errors but they are instantly and automatically moved to the bin/trash. Is there any way to prevent this?

si...@dudgeon.fi <si...@dudgeon.fi> #27Sep 28, 2019 02:00PM

Any update?

as...@gmail.com <as...@gmail.com> #28Sep 28, 2019 05:55PM

One workaround you can do is use a user account to send calendar invites instead of a system account. I changed my app to use a user account and it's been working fine since then.

mi...@xpsnote.com <mi...@xpsnote.com> #29Oct 5, 2019 02:53PM

Is there any update from Google on how to get a service calendar to show entries and not have them deposited in trash? This bug is crippling functionality in our app.

I'm not sure all that is involved in recoding to switch to a user account, but it seems like the service calendar issue should be fixed regardless.

Has anyone been able to get their service calendars to work again?

ja...@google.com <ja...@google.com> Oct 8, 2019 09:12AM

Assigned to ja...@google.com.

ja...@google.com <ja...@google.com> #30Oct 8, 2019 10:32AM

Accepted by ja...@google.com.

Hello,

Thanks for your report! We are aware there is an issue with Calendar and Service Accounts and we are working on it to fix it as soon as possible. You can click on the star ☆ next to the issue number to receive updates and give more priority to this post.
Cheers!

ar...@gmail.com <ar...@gmail.com> #31Oct 10, 2019 10:29AM

Any ETA when this issue will be solved?

fe...@bellizia.com <fe...@bellizia.com> #32Oct 10, 2019 12:48PM

Hi, do you have news?

si...@dealdash.com <si...@dealdash.com> #33Oct 26, 2019 12:16PM

Started working again for me. Some proper update/confirmation would be nice

ug...@gmail.com <ug...@gmail.com> #34Oct 26, 2019 03:28PM

It also started working for me again, too, which I'm grateful for. Thanks Google! Here's hoping it doesn't break on us again.

jb...@gmail.com <jb...@gmail.com> #35Oct 26, 2019 03:46PM

Awesome I will go give it a try

It does not work for me

Message last modified on Nov 1, 2019 06:19PM

ar...@gmail.com <ar...@gmail.com> #36Oct 28, 2019 02:03PM

I tried it and it's not working for me, anyone else tries it and it's working?

ma...@allos.it <ma...@allos.it> #37Oct 28, 2019 02:29PM

Now it works for me.

ar...@gmail.com <ar...@gmail.com> #38Oct 28, 2019 02:35PM

If I create an event with the service_account and tried to invite 1 person I get reach limit exceeded

[Deleted User] <[Deleted User]> #39Mar 13, 2020 06:24PM

Is there any update on this? I'm still receiving the same error

Uncaught exception: quotaExceeded: Calendar usage limits exceeded.

[Deleted User] <[Deleted User]> #40Apr 22, 2020 07:09AM

Using service account, the API works for roughly 100 requests then starts throwing 403 quotaExceeded error and continues to not work for about 24hours, after which it starts working again for the same 100ish requests.

The requests without attendees in them are working, but any requests with attendees in them keep returning this error even with exponential backoff.

code: 403,
errors: [ { domain: 'usageLimits',
reason: 'quotaExceeded',
message: 'Calendar usage limits exceeded.' } ] }

using official nodeJS googleAPIs node module, also sending quotaUser with each request as well!

Is this behavior intended? Is there some sort of limit that isn't documented well?

is...@google.com <is...@google.com> May 17, 2023 07:15AM

Status: New

jp...@google.com <jp...@google.com> Jul 13, 2023 02:39AM

Assigned to wo...@google.com.