Skip to content

Native iCloud apps for Windows and Linux, built in Rust. Notes, Reminders, Calendar, Contacts, Drive and Photos, offline and in sync with your iPhone.

6.3 KB
Raw Blame

Flatpak (Flathub) packaging

File What it is
io.github.yashwanthkamireddi.Skykeep.yml The manifest. Builds offline from the vendored sources below.
cargo-sources.json Every crate in Cargo.lock, generated by flatpak-cargo-generator.py.
node-sources.json Every npm package in package-lock.json, generated by flatpak-node-generator.
io.github.yashwanthkamireddi.Skykeep.desktop The main launcher entry.
io.github.yashwanthkamireddi.Skykeep.metainfo.xml The AppStream metadata a software centre shows.

Status: never built. The development machine has no flatpak or flatpak-builder. Checked so far: the manifest parses as YAML, both source files parse as JSON, appstreamcli validate --pedantic passes on the metainfo, and desktop-file-validate passes on the desktop file.

The identifier

The Tauri identifier in src-tauri/tauri.conf.json is this app ID, so the window's Wayland app ID, the six per-app windows (<id>.Notes, … in src-tauri/src/apps.rs) and the single-instance D-Bus name (<id>.SingleInstance, which a sandbox may own without --own-name) all match the exported desktop files. Installs from before the switch (dev.quince.client) are moved over at first launch by src-tauri/src/migrate.rs; inside the sandbox there is nothing to move (its data lives under ~/.var/app/<id>/), so a Flatpak starts with an empty library and fills it from iCloud.

Runtime and modules

  • org.gnome.Platform / org.gnome.Sdk 51, which ships webkit2gtk-4.1, gtk3, libsecret, GStreamer and libheif (from freedesktop-sdk 26.08).
  • SDK extensions rust-stable and node24.
  • libheif: in the runtime, so not bundled. It is built without an HEVC decoder; the libde265 plugin comes from org.freedesktop.Platform.codecs-extra, which the runtime downloads by itself. HEIC decoding inside the sandbox is unverified.
  • fuse3: not bundled. fuser is built with default-features = false, which links no libfuse.
  • Tray: no library. The app speaks StatusNotifierItem over D-Bus itself (ksni), without a well-known bus name inside the sandbox.

Permissions

Granted Why
--share=network iCloud.
--socket=wayland, --socket=fallback-x11, --share=ipc The window; X11 only without Wayland.
--device=dri GPU rendering for WebKitGTK.
--talk-name=org.freedesktop.secrets The Apple Account session lives in the Secret Service keyring.
--talk-name=org.freedesktop.Notifications Reminder alerts.
--talk-name=org.kde.StatusNotifierWatcher The tray icon.
--filesystem=xdg-download Drive and Photos save straight to ~/Downloads, not through the portal.

Left out on purpose:

  • The FUSE device. Drive and Photos as folders need /dev/fuse (only reachable with --device=all) and a fusermount3 that can't be setuid in the sandbox, so in practice a host escape (--talk-name=org.freedesktop.Flatpak). Flathub reviewers will push back on that, so the folders are unavailable in the Flatpak. If they're ever wanted, add --device=all and document why in the manifest.
  • --system-talk-name=org.freedesktop.login1 (wake on resume). Without it, alerts fall back to their ten-minute check.

Regenerating the sources

Regenerate whenever Cargo.lock or package-lock.json changes. Run from the repository root. The build uses --locked, so generate from the committed lockfiles.

cargo-sources.json was regenerated from Cargo.lock at 054560f on 2026-10-22 (1,267 entries; it now has aes-gcm, aes-kw, ctr, ghash, polyval and rustls 0.23.46).

node-sources.json was checked against package-lock.json on 2026-10-22 by running the current generator: every one of its 310 entries is identical. The generator's only additions were ten Playwright browser archives (chromium, webkit, ffmpeg), which the build never uses because the interface suites don't run inside it. They were left out, so the file is unchanged.

# Cargo: the generator is a single script with inline uv metadata.
curl -LO https://raw.githubusercontent.com/flatpak/flatpak-builder-tools/master/cargo/flatpak-cargo-generator.py
uv run --script flatpak-cargo-generator.py Cargo.lock -o packaging/flatpak/cargo-sources.json

# npm: flatpak-node-generator is a Python package in the same repository. Current versions
# add esbuild's binary by themselves (there is no --esbuild flag any more). Drop the
# ms-playwright entries it adds; the build doesn't need them.
uvx --from 'git+https://github.com/flatpak/flatpak-builder-tools.git#subdirectory=node' \
    flatpak-node-generator npm package-lock.json -o packaging/flatpak/node-sources.json

The esbuild entries place the binary that ESBUILD_BINARY_PATH in the manifest points at. Without them, Vite can't run offline.

Building locally

The manifest's main source is type: git, path: ../.., so it builds the repository's committed HEAD. Commit first. The desktop file and metainfo are separate file sources, so they're picked up even before they're committed.

flatpak remote-add --user --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
flatpak install --user flathub org.gnome.Platform//51 org.gnome.Sdk//51 \
    org.freedesktop.Sdk.Extension.rust-stable//26.08 org.freedesktop.Sdk.Extension.node24//26.08
# Match the extension branch to the freedesktop-sdk the GNOME runtime is built on
# (`flatpak info org.gnome.Sdk//51` shows it).

cd packaging/flatpak
flatpak-builder --user --install --force-clean build-dir io.github.yashwanthkamireddi.Skykeep.yml
flatpak run io.github.yashwanthkamireddi.Skykeep

build-dir/ and .flatpak-builder/ are build output. Don't commit them.

Lint before submitting:

flatpak run --command=flatpak-builder-lint org.flatpak.Builder manifest io.github.yashwanthkamireddi.Skykeep.yml
flatpak run --command=flatpak-builder-lint org.flatpak.Builder repo repo

Before Flathub

  • Point the git source at the public repository at a release tag and commit.
  • Set the v0.1.0 <release date> in both metainfo files (it's a 2099-01-01 placeholder).
  • <screenshots> point at the docs/media/screenshots/*-light.png on raw.githubusercontent.com/…/main. They resolve once the repository is public. Flathub's linter also asks for <branding> colours, which haven't been added yet.
  • Confirm HEIC decodes and the keyring session survives a restart inside the sandbox.