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
The bundled apps now update themselves. A scheduled workflow checks the microG repo and IzzyOnDroid every week for GmsCore, Companion, GsfProxy, Aurora Store and Aurora Services, and if any of them has moved it rebuilds the module, bumps the version and publishes the release on its own. Before this only a GmsCore change could trigger a refresh, so an Aurora update could sit unnoticed indefinitely.
Aurora Store and Aurora Services are now verified against pinned signing keys before they are staged, the same way the microG core already was. They were being downloaded from IzzyOnDroid and installed as system apps, one of them privileged, with nothing checking who signed them.
The privileged permission generator can now create an entry for a bundled app that does not have one yet. It could only add permissions to an app already listed, so a new privileged permission on GsfProxy would have been silently skipped, which is the same shape as the Aurora Services gap in 3.1.4.
Removed INSTALL_PACKAGES and DELETE_PACKAGES from the Aurora Services allowlist entry. Those were added in 3.1.4, but Aurora Services 0.3.0 only ever requests INSTALL_PACKAGE_UPDATES, and Android cannot grant an app a permission it does not ask for, so the two entries did nothing. If a future Aurora Services requests them the generator adds them back automatically.