Jean-Luc Makiola
ab631365b2
Round out the calendar-intent surface toward AOSP/Etar parity — the app already handled VIEW (date + event), INSERT, and .ics open/share, but was missing the edit action and the alternate .ics MIME labels. - ACTION_EDIT on content://com.android.calendar/events/<id> now opens the event in the edit form (previously only VIEW → read-only detail existed). An assistant, task app, or widget can hand an event to Calendula to edit. A bare EDIT URI with no occurrence extras falls back to the event row's own DTSTART/DTEND, mirroring the #48 view-event fallback. - ACTION_EDIT with no event id (AOSP's "edit a new event") maps to the same prefilled create form as ACTION_INSERT. - The .ics VIEW/SEND filters now also accept text/x-vcalendar (vCalendar 1.0 / .vcs) and application/ics — the alternate labels the same calendar data arrives under from some file/mail apps (matches Etar's ImportActivity). Deliberately excluded: webcal:// / http(s) remote-calendar subscription (needs INTERNET, which the app doesn't have) and the Google-web-link handler (Google-specific + network). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
289 lines
14 KiB
XML
289 lines
14 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
||
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
|
||
xmlns:tools="http://schemas.android.com/tools">
|
||
|
||
<uses-permission android:name="android.permission.READ_CALENDAR" />
|
||
<uses-permission android:name="android.permission.WRITE_CALENDAR" />
|
||
<uses-permission android:name="android.permission.POST_NOTIFICATIONS" />
|
||
<!--
|
||
Optional and feature-gated: only the "Contact special dates" feature reads
|
||
contacts, and only after the user enables it and grants this at runtime
|
||
(never requested at startup). Everything stays offline — birthdays and
|
||
other contact dates are mirrored one-way into local calendars; contacts
|
||
are never written and nothing leaves the device (the app has no INTERNET
|
||
permission). See docs/design/contact-special-dates.md.
|
||
-->
|
||
<uses-permission android:name="android.permission.READ_CONTACTS" />
|
||
<!--
|
||
Lets the "Reliable delivery" setting open the direct system dialog to
|
||
exempt Calendula from battery optimisation (so reminder broadcasts aren't
|
||
delayed by Doze). Used only to launch that dialog; falls back to the
|
||
battery-optimisation list if the OS declines the direct intent.
|
||
-->
|
||
<uses-permission android:name="android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS" />
|
||
|
||
<!--
|
||
Re-fire a snoozed reminder at an exact time (the calendar provider won't —
|
||
its alert is already fired). USE_EXACT_ALARM is auto-granted to calendar
|
||
apps on API 33+; SCHEDULE_EXACT_ALARM covers API 31–32 (user-revocable,
|
||
with an inexact fallback if withheld). F-Droid-clean: no Play allowlisting.
|
||
-->
|
||
<uses-permission
|
||
android:name="android.permission.SCHEDULE_EXACT_ALARM"
|
||
android:maxSdkVersion="32" />
|
||
<uses-permission android:name="android.permission.USE_EXACT_ALARM" />
|
||
|
||
<!-- Package visibility (Android 11+): without this, getLaunchIntentForPackage
|
||
returns null and the calendar manager's per-account "manage" button can't
|
||
open the source sync app (DAVx5, ICSx5, Google Calendar, …). The LAUNCHER
|
||
intent makes launchable apps visible so we can launch whichever app owns a
|
||
calendar account's authenticator. -->
|
||
<queries>
|
||
<intent>
|
||
<action android:name="android.intent.action.MAIN" />
|
||
<category android:name="android.intent.category.LAUNCHER" />
|
||
</intent>
|
||
</queries>
|
||
|
||
<application
|
||
android:name=".CalendulaApp"
|
||
android:allowBackup="true"
|
||
android:enableOnBackInvokedCallback="true"
|
||
android:dataExtractionRules="@xml/data_extraction_rules"
|
||
android:fullBackupContent="@xml/backup_rules"
|
||
android:icon="@mipmap/ic_launcher"
|
||
android:label="@string/app_name"
|
||
android:localeConfig="@xml/locales_config"
|
||
android:roundIcon="@mipmap/ic_launcher_round"
|
||
android:supportsRtl="true"
|
||
android:theme="@style/Theme.Calendula"
|
||
tools:targetApi="35">
|
||
<activity
|
||
android:name=".MainActivity"
|
||
android:exported="true"
|
||
android:launchMode="singleTop"
|
||
android:windowSoftInputMode="adjustResize">
|
||
<intent-filter>
|
||
<action android:name="android.intent.action.MAIN" />
|
||
<category android:name="android.intent.category.LAUNCHER" />
|
||
</intent-filter>
|
||
|
||
<!-- Be selectable as the system calendar app. Android has no API for
|
||
an app to make itself the default, so registering the filters
|
||
launchers and the OS use is what lets the user pick Calendula
|
||
from the system chooser when a date action fires (issue #9).
|
||
APP_CALENDAR is the "open the calendar app" action; the VIEW
|
||
filters below catch a tapped date. -->
|
||
<intent-filter>
|
||
<action android:name="android.intent.action.MAIN" />
|
||
<category android:name="android.intent.category.DEFAULT" />
|
||
<category android:name="android.intent.category.APP_CALENDAR" />
|
||
</intent-filter>
|
||
<!-- A launcher/clock date tap fires ACTION_VIEW on the provider's
|
||
time Uri (content://com.android.calendar/time/<epochMillis>);
|
||
some surfaces use the time/epoch mime type. We open the day view
|
||
on that date (MainActivity.calendarTimeDateOrNull). -->
|
||
<intent-filter>
|
||
<action android:name="android.intent.action.VIEW" />
|
||
<category android:name="android.intent.category.DEFAULT" />
|
||
<data
|
||
android:scheme="content"
|
||
android:host="com.android.calendar"
|
||
android:pathPrefix="/time" />
|
||
</intent-filter>
|
||
<intent-filter>
|
||
<action android:name="android.intent.action.VIEW" />
|
||
<category android:name="android.intent.category.DEFAULT" />
|
||
<data android:mimeType="time/epoch" />
|
||
</intent-filter>
|
||
|
||
<!-- Open a .ics/.vcs file (file manager / email attachment / browser).
|
||
The three MIME types cover the common labels the same calendar
|
||
data arrives under: iCalendar 2.0 (text/calendar), the older
|
||
vCalendar 1.0 / .vcs (text/x-vcalendar), and application/ics some
|
||
mail apps emit — Android cross-products the scheme and mimeType
|
||
tags, so each MIME is accepted on both schemes (matches Etar). -->
|
||
<intent-filter>
|
||
<action android:name="android.intent.action.VIEW" />
|
||
<category android:name="android.intent.category.DEFAULT" />
|
||
<category android:name="android.intent.category.BROWSABLE" />
|
||
<data android:scheme="content" />
|
||
<data android:scheme="file" />
|
||
<data android:mimeType="text/calendar" />
|
||
<data android:mimeType="text/x-vcalendar" />
|
||
<data android:mimeType="application/ics" />
|
||
</intent-filter>
|
||
<!-- Receive a .ics/.vcs shared from another app (same MIME set). -->
|
||
<intent-filter>
|
||
<action android:name="android.intent.action.SEND" />
|
||
<category android:name="android.intent.category.DEFAULT" />
|
||
<data android:mimeType="text/calendar" />
|
||
<data android:mimeType="text/x-vcalendar" />
|
||
<data android:mimeType="application/ics" />
|
||
</intent-filter>
|
||
|
||
<!-- Let another app or widget (e.g. the Todo Agenda widget) launch us
|
||
to create a new event, the way the AOSP calendar accepts it:
|
||
ACTION_INSERT on the events dir mime type, carrying the new
|
||
event's fields as CalendarContract extras
|
||
(MainActivity.insertFormOrNull, issue #30). ACTION_EDIT on the
|
||
dir mime is AOSP's "edit a new event" — i.e. create — so it maps
|
||
to the same prefilled create form. -->
|
||
<intent-filter>
|
||
<action android:name="android.intent.action.INSERT" />
|
||
<action android:name="android.intent.action.EDIT" />
|
||
<category android:name="android.intent.category.DEFAULT" />
|
||
<data android:mimeType="vnd.android.cursor.dir/event" />
|
||
</intent-filter>
|
||
|
||
<!-- Edit an existing event another app/assistant/widget points at:
|
||
ACTION_EDIT on content://com.android.calendar/events/<id>, the way
|
||
AOSP fires it. Opens the occurrence in the edit form (not the
|
||
read-only detail — that's the VIEW filter above). Matched by the
|
||
provider's item MIME type, like the VIEW filter. The occurrence's
|
||
times ride as EXTRA_EVENT_BEGIN_TIME / EXTRA_EVENT_END_TIME when
|
||
supplied (MainActivity.editEventKeyOrNull). -->
|
||
<intent-filter>
|
||
<action android:name="android.intent.action.EDIT" />
|
||
<category android:name="android.intent.category.DEFAULT" />
|
||
<data android:mimeType="vnd.android.cursor.item/event" />
|
||
</intent-filter>
|
||
|
||
<!-- Open an existing event another app/widget points at (e.g. tapping
|
||
an event in the Todo Agenda widget): ACTION_VIEW on
|
||
content://com.android.calendar/events/<id>, the way AOSP fires it.
|
||
Matched by the provider's item MIME type, not the path — a
|
||
content: VIEW intent carries the resolved type
|
||
(vnd.android.cursor.item/event) and a path-only filter wouldn't
|
||
match it. The occurrence's times ride as EXTRA_EVENT_BEGIN_TIME /
|
||
EXTRA_EVENT_END_TIME when the launcher supplies them
|
||
(MainActivity.viewEventKeyOrNull, issue #48). -->
|
||
<intent-filter>
|
||
<action android:name="android.intent.action.VIEW" />
|
||
<category android:name="android.intent.category.DEFAULT" />
|
||
<category android:name="android.intent.category.BROWSABLE" />
|
||
<data android:mimeType="vnd.android.cursor.item/event" />
|
||
</intent-filter>
|
||
|
||
<!-- Launcher long-press shortcuts (e.g. "New event"). -->
|
||
<meta-data
|
||
android:name="android.app.shortcuts"
|
||
android:resource="@xml/shortcuts" />
|
||
</activity>
|
||
|
||
<!-- Standalone surface for a captured crash report. MainActivity routes
|
||
here on a startup crash-loop, so it stays clear of the app's Hilt
|
||
graph and Compose content. Not exported: launched only by us. -->
|
||
<activity
|
||
android:name=".ui.crash.CrashReportActivity"
|
||
android:exported="false"
|
||
android:excludeFromRecents="true"
|
||
android:launchMode="singleTask" />
|
||
|
||
<!-- Quick Settings tile: a one-tap "New event" shortcut in the QS panel.
|
||
Exported with BIND_QUICK_SETTINGS_TILE so only the system QS host can
|
||
bind it; the action mirrors the launcher "New event" shortcut. -->
|
||
<service
|
||
android:name=".qs.NewEventTileService"
|
||
android:exported="true"
|
||
android:icon="@drawable/ic_qs_new_event"
|
||
android:label="@string/qs_tile_new_event_label"
|
||
android:permission="android.permission.BIND_QUICK_SETTINGS_TILE">
|
||
<intent-filter>
|
||
<action android:name="android.service.quicksettings.action.QS_TILE" />
|
||
</intent-filter>
|
||
</service>
|
||
|
||
<!-- The provider broadcasts EVENT_REMINDER at reminder time but posts
|
||
no notification itself — a calendar app must (v1.4, Etar model).
|
||
Exported: the broadcast arrives from the provider's process. -->
|
||
<receiver
|
||
android:name=".data.reminders.EventReminderReceiver"
|
||
android:exported="true">
|
||
<intent-filter>
|
||
<action android:name="android.intent.action.EVENT_REMINDER" />
|
||
<data
|
||
android:host="com.android.calendar"
|
||
android:scheme="content" />
|
||
</intent-filter>
|
||
</receiver>
|
||
|
||
<!-- Snooze / dismiss actions on a reminder notification, plus the snooze
|
||
re-show alarm. Not exported: only our own notification buttons and
|
||
AlarmManager PendingIntents target it. -->
|
||
<receiver
|
||
android:name=".data.reminders.ReminderActionReceiver"
|
||
android:exported="false" />
|
||
|
||
<!-- Home-screen widgets (Glance). Exported: the launcher/host binds them. -->
|
||
<receiver
|
||
android:name=".widget.agenda.AgendaWidgetReceiver"
|
||
android:label="@string/widget_agenda_label"
|
||
android:exported="true">
|
||
<intent-filter>
|
||
<action android:name="android.appwidget.action.APPWIDGET_UPDATE" />
|
||
</intent-filter>
|
||
<meta-data
|
||
android:name="android.appwidget.provider"
|
||
android:resource="@xml/appwidget_info_agenda" />
|
||
</receiver>
|
||
|
||
<receiver
|
||
android:name=".widget.month.MonthWidgetReceiver"
|
||
android:label="@string/widget_month_label"
|
||
android:exported="true">
|
||
<intent-filter>
|
||
<action android:name="android.appwidget.action.APPWIDGET_UPDATE" />
|
||
</intent-filter>
|
||
<meta-data
|
||
android:name="android.appwidget.provider"
|
||
android:resource="@xml/appwidget_info_month" />
|
||
</receiver>
|
||
|
||
<!-- Keeps both widgets fresh: the calendar provider broadcasts
|
||
PROVIDER_CHANGED on any data change (our writes and external sync),
|
||
and the system broadcasts the date/time ones at midnight / clock
|
||
changes so "today" highlighting rolls over. -->
|
||
<receiver
|
||
android:name=".widget.WidgetUpdateReceiver"
|
||
android:exported="true">
|
||
<intent-filter>
|
||
<action android:name="android.intent.action.PROVIDER_CHANGED" />
|
||
<data
|
||
android:host="com.android.calendar"
|
||
android:scheme="content" />
|
||
</intent-filter>
|
||
<intent-filter>
|
||
<action android:name="android.intent.action.DATE_CHANGED" />
|
||
<action android:name="android.intent.action.TIME_SET" />
|
||
<action android:name="android.intent.action.TIMEZONE_CHANGED" />
|
||
</intent-filter>
|
||
</receiver>
|
||
|
||
<!-- Hands .ics files we stage in the cache to other apps via a content
|
||
Uri (single-event share). Authority tracks applicationId so the
|
||
debug suffix doesn't break getUriForFile. -->
|
||
<provider
|
||
android:name="androidx.core.content.FileProvider"
|
||
android:authorities="${applicationId}.fileprovider"
|
||
android:exported="false"
|
||
android:grantUriPermissions="true">
|
||
<meta-data
|
||
android:name="android.support.FILE_PROVIDER_PATHS"
|
||
android:resource="@xml/file_paths" />
|
||
</provider>
|
||
|
||
<!-- Persists the per-app language (M4) on API < 33, where the platform
|
||
per-app-languages API is unavailable. On 33+ this is a no-op. -->
|
||
<service
|
||
android:name="androidx.appcompat.app.AppLocalesMetadataHolderService"
|
||
android:enabled="false"
|
||
android:exported="false">
|
||
<meta-data
|
||
android:name="autoStoreLocales"
|
||
android:value="true" />
|
||
</service>
|
||
</application>
|
||
|
||
</manifest>
|