Skip to content

Automatic updates only in Settings on Android

The owner asked (2026-10-20) to remove the Automatic updates switch from Android’s airspace settings page: Settings › Map already has the same switch, so the page shows it twice. iOS has it only in Settings › Map (vulture-ios/Modules/App/Sources/Features/Settings/Settings/Infrastructure/AppMainSettings.swift).

The page got the switch in phase 6 (P6-D9), before Android had a Settings screen; P9-D3 kept it there next to the new Settings row.

  • The airspace settings page (Library › Airspaces › ⋮ and Settings › Map › Airspace) keeps Custom airspace and Show hidden sectors, and loses the Automatic updates section (switch and footer).
  • Settings › Map › Automatic updates is unchanged: the same synced setting (isAutomaticUpdateEnabled, VultureAutomaticUpdateEnabled, default off), the same check at app start.

None.

None.

None new. settings_label_autoupdates and settings_label_autoupdates_title stay, used by Settings › Map.

#QuestionDecisionDate
1Where does Automatic updates live on Android?Only in Settings › Map, as iOS (owner).2026-10-20

None.

No changes.

Code (vulture-android)Change
feature/airspacefiles/.../AirspaceSettingsScreen.ktDrop the Automatic updates section and the onAutomaticUpdates parameter
feature/airspacefiles/.../AirspaceSettingsViewModel.ktDrop isAutomaticUpdateEnabled and setAutomaticUpdateEnabled from the page’s state and actions
feature/airspacefiles/.../AirspacePreferences.ktKeep isAutomaticUpdateEnabled only if the update check at app start (AirspaceUpdatesHost) still reads it from here

Tests and the airspace settings screenshots; changelog (“Automatic updates is only in Settings”).

No changes.

  • vulture-android: remove the switch from the airspace settings page; tests; screenshots; changelog (2026-10-20). AirspacePreferences dropped it too: the start-up check reads the setting in :data:airspace.
  • vulture-docs: when built, update P6-D9 and P9-D3 in Port decisions and set status: shipped.