Aviate 1.0.0 Prelease 7

✈️ Aviate 1.0.0 Pre-Release 7

This pre-release is less about adding another thing to your boarding pass and more about giving you a clear choice before Aviate turns something on or shares anything outside the app.

It also adds the reporting and blocking tools that should have been there as soon as public profiles and groups were introduced. They are there now.

Reporting and blocking

Before taking part in public profiles or groups, Aviate now asks you to agree to a short set of community rules. They cover harassment, hate speech, threats, spam, impersonation, private information, and the other things nobody should have to work around in a travel app.

You can report a public profile, an account, a member, or an entire group. A report includes a reason and optional details. When you report a person, you can also ask Aviate to block that account after the report is sent. Reports are reviewed by Aviate administrators, and Aviate does not show the reported account who sent the report.

Blocking now carries through the signed-in Aviate experience. Blocked accounts disappear from each other's profile and community views, direct flight shares between them are removed, and new group invitations, community notifications, and direct shares are stopped. You can review and unblock accounts later from Public Profile settings.

You decide what gets turned on

There is a new Data & Notification Controls section in Preferences. It separates four choices that used to be too easy to bundle together:

• Account-linked push notifications
• Optional crash reports
• Precise location inside airport maps
• The Wear OS companion

Each one explains what it uses before you enable it, and each one can be turned off again. Crash reports and push notifications stay off until you make that choice. Indoor maps still work without your location, and turning off the Wear OS companion stops future transfers and clears Aviate's cached watch data.

Flight tracking stays in your control

On Android, ongoing live tracking now asks separately for each flight. The prompt explains that Aviate will check that flight about every five minutes and keep an ongoing notification until it ends. You can enable it or choose Not for this flight.

Once tracking is running, the notification has a visible Stop tracking action. Stopping it prevents that flight from silently starting again. After a phone restart or app update, Aviate sends a normal reminder to reopen the app instead of restarting live tracking by itself.

The countdown inside the notification now uses Android's own chronometer too, so it can keep moving without waking Aviate every minute just to redraw a number.

Push alerts and Wear OS need to be re-enabled

Pre-Release 7 resets the old automatic connections so the new choices are real. Account-linked push alerts and Wear OS syncing both start turned off after updating.

If you use either one, open Preferences → Data & Notification Controls and enable it again. The Wear OS connection has been rebuilt as an explicit opt-in, and the update clears the watch data left by the older automatic connection.

The watch can receive upcoming flights, boarding-pass barcodes, live progress, gate changes, and your Pro status. It no longer receives your Aviate username, email, access token, or refresh token. Turning the companion off or logging out clears the cached Aviate data on paired watches.

Clearer before you continue

Aviate now explains a few one-time transfers at the moment they matter:

• Parking waits for you to tap Capture before requesting your current location. It no longer grabs it when the screen opens.
• Airport maps ask before showing your position or sending coordinates to the walking-route service.
• Ride links ask before adding your current pickup coordinates to a third-party app.
• Airline Connect explains that your password stays on the airline's website and what loyalty or trip data Aviate stores after you sign in.
• Bug reports explain optional diagnostic attachments, keep them off by default, and redact authentication secrets.

Form responses are also shown to reviewers without automatically including your Aviate username or email. There was an unexpected bug that could theoretically allow administrators to see usernames for each form, but thankfully, that has not been abused. Your account is still used internally to enforce one response and to remove the response if you delete your account.

Disconnect should mean disconnect

Disconnecting an airline now removes its saved connection and loyalty or trip data from Aviate's servers before the local copy is cleared. If the server cannot confirm that removal, the connection stays visible instead of pretending the job is done.

Deleting your Aviate account now reaches more of the data attached to it, including community records and report attachments. If attachment storage is temporarily unavailable, that cleanup is retried without bringing the deleted account back.

Android sign-in tokens are also migrated out of normal app storage and encrypted with a non-exportable key in Android Keystore. Old copies are removed after the migration, and widgets and live tracking use the same protected store.

Smaller changes

• The Jet Lag Advisor uses less medical-sounding language, removes the melatonin suggestion, stops presenting an adjustment estimate as a promise, and links to CDC Travelers' Health.
• Screen scanning now explains its one-frame capture before Android's system prompt, removes its temporary image afterward, and tells you when a protected screen or timeout prevented the scan.
• Saving Aviate images and videos now requests the correct permission on Android 8 and 9. Android 10 and newer continue to use scoped gallery storage without asking for broad storage access.

This release is mostly about saying what Aviate is doing before it does it, then respecting the answer. That should be the standard, and Pre-Release 7 gets us much closer to it.