Repeatedly it is asked for permission to access Google acount in aCalendar

DeletedUser370

ACalendar does not make such an authorization request.

So I just tested this on stock PixelOS. Installing the aCalendar app instantly makes the system show me exactly the same notification and exactly the same pop-up when I tap on that notification, as when I tested on GrapheneOS with Sandboxed Google Play. Spoiler alert: you don't have to actually open the app on PixelOS to get the annoying notification.

It is probably a bug in microG or a similar framework.

"A similar framework" – such as Google Play Services running on stock PixelOS, it seems.

Dan-cer

Yes, I didn't find a MicroG in the system files, so it's probably a similar framework.

Dan-cer

Is it possible to fix it? Otherwise I could delete google account...

alienheartbeat

Same problem on Pixel 9.

ACalendar+ is asking for access to calendars of two google accounts which have no calendars.
(I have 3 google accounts on the phone, for different countries, but none have calendars.
Actual calendars are elsewhere and all reached by DavX5.

I tried to stop notifications from ACalendar+ but of course this doesnt help
as the notifications are coming from the system and cant be stopped.

There is no option in ACalendar+ to specify which accounts it should attempt to access.
Contacting the developer I have found in the past to not be helpful.

So,

I allowed ACalendar+ access to the accounts, as there are no calendars there.
Like allowing a kid to look in an empty tin.
The annoying requests for permission ceased.
Then, in Settings/ Pwds, Passkys and Accounts /
I turned off sync on both those accounts.
Though the option I turned of was actually named:
"ACalendar+ Tasks"
so whether it is still trying to access calendars and contacts, I don't know.

So my choice seems to be small bandwidth wastage Vs daily annoyance.
As I am allergic to being annoyed, I chose the small bandwidth uncertainty.

Dan-cer

alienheartbeat I have to say that the issue disappeared here a few months ago. However, I don't know - or remember - why or what I did to stop it.

alienheartbeat

ha, always happens. You might have accidentally allowed it. Anyway if you think of it, would be worth knowing.

Dan-cer

alienheartbeat Yes, btw I'm going to move to a newer Pixel. With the installation of aCalendar I will probably see if the issue reappears or not.

Dan-cer

alienheartbeat I suddenly got that annoying message again. It happened right after I added my Gmail account. I needed to do that temporarily to be able to use Telegram.
And I remember the solution to the problem: remove the Google account.
I hardly need it in GrapheneOS bc I install and update apps with Aurora, anonymous login, for example.

alienheartbeat

Interesting. For myself, I find G accounts useful to retain
(eg 1 app I use, Caltopo, requires G for single signon).
I no longer use G for email, calendar or contacts,
(not for privacy reasons, but because they are unreliable)
but I dont have a problem with directly using the G Play Store
even though it is more annoying than 27 cats on hallucinogens.

The real problem here I think is that while ACalendar does give you a choice
over which accounts/calendars to use, it doesn't give you a choice over which it accesses.

Dan-cer

alienheartbeat In any case, I believe that it is not the aCalendar app that is causing the annoying notifications, but rather the Google account. While this account was active here, it generated other notifications with calls to action too.

schweizer

I think it's the fault of acalendar+ to allow communication with play services when the user explicitely does not want this.

Dan-cer

schweizer Don't underestimate Google's capabilities.

schweizer

Dan-cer I doubt that Play Services is able to circumvent the sandbox. According to the FAQ apps within the same profile can communicate with each other with mutual consent. Google will have set their permission to communicate with every app. So acalendar+ must have set their permissions to communicate with Play Services as well.

Dan-cer

schweizer We should perhaps pass this question on to the developers at GOS. It may be possible that the Gmail account is so aggressive beyond the sandbox lock. I think that's more likely. Especially since similar requests to those made to aCalendar were also made to two other apps while I had my Gmail account active.