release.ps1: - The release is created as a draft, both APKs are uploaded, then it is published, so /releases/latest (and the QR code) never points at a release without its APK; a draft left by an interrupted run is cleaned up or resumed. - Before publishing, the APK's signing certificate is compared with the release keystore's, so an APK signed with another key is never published. - With -SkipBuild, an APK not built from the commit being tagged is refused. flexera/AndroidManifest.xml: the home screen's database provider is no longer exported. Lawnchair's manifest removes the definitions of its READ_SETTINGS and WRITE_SETTINGS permissions, so any app could have defined them and read or erased the home screen; the launcher itself never goes through the provider. build.gradle: github, the channel that is released, is the default flavour, and Flexera's folders are wired into the nightly and play variants too, so assembleDebug, lint and Android Studio's default variant build; the lines Flexera changed carry markers. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
85 lines
3.9 KiB
XML
85 lines
3.9 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!--
|
|
Flexera Launcher manifest overrides. Attached to the debug and release build types in build.gradle,
|
|
which outrank Lawnchair's flavor manifests and every library manifest during the merge.
|
|
|
|
Network access: the INTERNET permission comes from Lawnchair's manifest and is kept for one purpose,
|
|
the app's own update check (app.flexera.update.FlexeraUpdater). Lawnchair's online features stay
|
|
switched off in code; see app.flexera.FlexeraNetwork.
|
|
-->
|
|
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
|
|
xmlns:tools="http://schemas.android.com/tools">
|
|
|
|
<!-- Lets the app hand a downloaded update to Android's installer. The owner still confirms each install. -->
|
|
<uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" />
|
|
|
|
<!--
|
|
Since Android 17 an app needs this to reach a device on the network the phone itself is on.
|
|
The update server can be such a device: at the owner's home its name leads to its address
|
|
on the home network. Asked for only when a check for updates is stopped by it (About screen).
|
|
-->
|
|
<uses-permission android:name="android.permission.ACCESS_LOCAL_NETWORK" />
|
|
|
|
<application>
|
|
|
|
<!--
|
|
The picture widget that comes with the launcher. Not exported: only this launcher can
|
|
place it, and only this launcher knows how to draw it.
|
|
-->
|
|
<receiver
|
|
android:name="app.flexera.widget.PictureWidgetProvider"
|
|
android:exported="false"
|
|
android:label="@string/flexera_picture_widget">
|
|
<intent-filter>
|
|
<action android:name="android.appwidget.action.APPWIDGET_UPDATE" />
|
|
</intent-filter>
|
|
<meta-data
|
|
android:name="android.appwidget.provider"
|
|
android:resource="@xml/flexera_picture_widget_info" />
|
|
</receiver>
|
|
|
|
<!-- The clock widget that comes with the launcher: the time and the date. -->
|
|
<receiver
|
|
android:name="app.flexera.widget.ClockWidgetProvider"
|
|
android:exported="false"
|
|
android:label="@string/flexera_clock_widget">
|
|
<intent-filter>
|
|
<action android:name="android.appwidget.action.APPWIDGET_UPDATE" />
|
|
</intent-filter>
|
|
<meta-data
|
|
android:name="android.appwidget.provider"
|
|
android:resource="@xml/flexera_clock_widget_info" />
|
|
</receiver>
|
|
|
|
<!-- The clock widget's options, a sheet over the home screen. -->
|
|
<activity
|
|
android:name="app.flexera.widget.ClockWidgetConfigActivity"
|
|
android:excludeFromRecents="true"
|
|
android:exported="false"
|
|
android:theme="@style/Theme.Transparent" />
|
|
|
|
<!-- Opens Android's photo picker for the picture widget; it has no screen of its own. -->
|
|
<activity
|
|
android:name="app.flexera.widget.PictureWidgetConfigActivity"
|
|
android:excludeFromRecents="true"
|
|
android:exported="false"
|
|
android:theme="@style/Theme.Transparent" />
|
|
|
|
<!--
|
|
The home screen's database. Not exported, so other apps cannot reach it. Launcher3 exports
|
|
it for system apps that hold its READ_SETTINGS and WRITE_SETTINGS permissions, but
|
|
Lawnchair's manifest removes the definitions of those two permissions, so nothing ties
|
|
them to this app's signing key: any app could define them for itself and then read,
|
|
change or erase the home screen. The launcher itself never goes through this provider;
|
|
it uses the database directly. Only android:exported changes here; the rest of the
|
|
declaration is in AndroidManifest-common.xml.
|
|
-->
|
|
<provider
|
|
android:name="com.android.launcher3.LauncherProvider"
|
|
android:exported="false"
|
|
tools:replace="android:exported" />
|
|
|
|
</application>
|
|
|
|
</manifest>
|