You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I try to add a public calendar via an URL with the calendar app. Error message asks if I'm sure the calendar is public. It is. When I download the ics-file and import it into a calendar it works, but that's not the solution since the calendar behind the URL is updated regularly. E.g. URL: http://i.cal.to/ical/4437/fiba/team-deutschland-basketball/424997c0.f42b7eb1-1af6cb2e.ics
Expected behavior
A new calendar is created and the events are imported and updated regularly.
Device: Pixel 6a
OS: GrapheneOS
Version: 14
The text was updated successfully, but these errors were encountered:
0utl4w
added
the
bug
broken functionality, usability problems, unexpected errors
label
Oct 8, 2024
Hi, thanks for the report.
It's probably something with GrapheneOS, but we will investigate further.
Does it happen to any URSs or just from the provider you mentioned?
Hi, it happens with any URL I am trying. But with the app ISCx5 it is no problem to sync these adresses.
Am 9. Oktober 2024 08:14:52 UTC schrieb "André Dias" ***@***.***>:
Hi, thanks for the report.
It's probably something with GrapheneOS, but we will investigate further.
Does it happen to any URSs or just from the provider you mentioned?
--
Reply to this email directly or view it on GitHub:
#7695 (comment)
You are receiving this because you authored the thread.
Message ID: ***@***.***>
I try to add a public calendar via an URL with the calendar app. Error message asks if I'm sure the calendar is public. It is. When I download the ics-file and import it into a calendar it works, but that's not the solution since the calendar behind the URL is updated regularly. E.g. URL: http://i.cal.to/ical/4437/fiba/team-deutschland-basketball/424997c0.f42b7eb1-1af6cb2e.ics
Expected behavior
A new calendar is created and the events are imported and updated regularly.
The text was updated successfully, but these errors were encountered: