Airclone v0.21.0

Airclone v0.21.0 — adding a cloud is guided now

Adding storage used to mean picking from 69 alphabetically-sorted backend names starting at
alias, filling in a form of up to 78 options, and then answering every field you left blank
a second time as a question. It worked. Nobody would call it guided.

Now you press Add a cloud, pick Google Drive, press Sign in, and you are done.

What you will see

Ten clouds you recognise, first. Google Drive, OneDrive, Dropbox, iCloud Drive, Google
Photos, Amazon S3, Cloudflare R2, Backblaze B2, SFTP and WebDAV — then everything else rclone
supports behind "All storage types". Search finds things by the name you would actually use:
type "Wasabi" or "Nextcloud" and you get them, without needing to know that Wasabi is spelled
"s3" and Nextcloud is spelled "webdav".

Signing in is one button. The other ways are still there, one tap behind Other ways to
sign in, and each only appears when it can actually work for that provider on that device:
show me the link, authorize on another device with rclone's own hand-off, or fill everything
in by hand.

The fields that matter, in words. For the storage types rclone asks nothing about — S3,
B2, SFTP, WebDAV, FTP, SMB, Azure and crypt — you get one screen with the handful of fields
that are actually needed, called what they are called in your provider's console. Picking a
crypt remote's underlying storage is a list of your remotes rather than a text box you have
to type name:folder into correctly.

Questions became controls. Where rclone offers a list of choices you now get a list.
Choosing a Google Shared Drive used to mean typing a drive ID.

You are not stopped to invent a name. One is suggested and you can change it.

Google is retiring the sign-in rclone has always used

This one is worth knowing about whether or not you use Airclone.

Google is switching off the shared sign-in credential that rclone has used for Google Drive
and Google Photos. rclone's own words are that it "will stop working during 2026", and rclone
now recommends creating your own.

Airclone asks you, plainly, rather than choosing for you. You can set up your own sign-in —
there is a short walkthrough and a link to rclone's full instructions — or use the shared one
for now, knowing it has an end date, and change it later under Advanced without adding the
cloud again. Existing remotes are not touched. If one stops working, the same walkthrough
is offered from the failure.

Cancelling actually cancels

If you close a sign-in half way through, two things now happen that did not before: the
sign-in is ended properly instead of being left waiting — an abandoned one used to make your
next attempt fail — and the half-written remote is removed. rclone writes a remote's entry
as soon as it asks its first question, so an abandoned setup left behind an entry that looked
like a remote and could not connect to anything.

Airclone checks that the removal worked instead of assuming it did, and tells you if it did
not.

Nothing was taken away

The full options form is still there, exactly as it was, on every storage type — from the
tile, from the header of any guided step, and offered automatically if setup fails, carrying
what you already typed. It gained one thing: a filter box. S3 has 78 options, and finding
endpoint by scrolling was the previous reality.

Editing an existing remote is unchanged.

Also in this release

• Credentials are hidden as you type them in more places. rclone does not mark every secret as
  one — it does not flag a Google client secret or an S3 access key as a password — so
  Airclone no longer takes its word for it.
• Error messages are cleaned of anything that looks like a credential before they are shown.
  Some server errors quote the address they failed on, and those can contain a password.
• On Android, signing in opens a real browser tab rather than failing silently on newer
  versions of Android.

Which rclone is inside

rclone v1.75.1, the current release, bundled into every download — you do not need rclone
installed. This version is not optional here: the guided sign-in asks rclone for the sign-in
link through methods that 1.75 introduced. If you point Airclone at your own older rclone it
still works, by reading the link from the engine's own output instead.

v1.75.1 is also a security release, and several of its advisories land on things Airclone
ships: a path-traversal in untrusted zip archives, and a planted symlink escaping the root of
a local remote.

Honest status

This release is on GitHub only. Google Drive setup has been tested end to end on Windows.
The Android, iOS and macOS paths share the same code and are covered by automated tests, but
have not yet been through a real sign-in on a device — so this is not going to the app stores
until they have.

Everything Airclone does with rclone's configuration was verified against a real rclone
v1.75.1 before it was written, and the recorded behaviour is replayed in the test suite, so a
future rclone that changes its questions will fail a test rather than surprise you.