Fission 0.8.0: release workflows, native video, and selector-driven testing

Fission 0.8.0 adds a shared release plan, provider-aware publishing, native video, selector-driven LiveTest actions, text-input fixes, and generated app…
2026-07-14
By Fission Team
Releases
Fission 0.8.0 adds a shared release plan, provider-aware publishing, native video, selector-driven LiveTest actions, text-input fixes, and generated app guidance.
These changes cover the path from checking the app and its release content to publishing the artifact and testing it with semantic actions instead of coordinates.

One release workflow

Publishing now starts from a shared release plan. The plan records the target, package format, provider, track, locales, release version, build number, requirements, capabilities, and steps.
That plan is consumed by:
•
fission readiness release;
•
fission publish;
•
guided publish prompts;
•
the Terminal TUI;
•
the windowed publish UI;
•
CI JSON mode.
This keeps the CLI, terminal UI, windowed UI, and CI from drifting into different release behaviour.

Release content is first-class

For store releases, the plan lists requirements for release notes, screenshots, localised metadata, privacy and review details, tester setup, provider assets, signing, and provider authentication.
Each item is marked as required by the provider, recommended by Fission, optional, or not applicable. You can explicitly skip a recommendation and see that choice in the receipt. Provider-required items still block changes to the store until you provide them.
Before upload, package readiness checks more of the release artifact itself:
•
selected app icon source and generated icon manifest;
•
target, format, version, build, source config hashes, and artifact hashes;
•
package validation receipts for install/load smoke checks;
•
stale artifact manifests before expensive rebuilds;
•
secondary artifacts such as debug symbols or crash diagnostics.

Provider-aware publishing

The provider layer now records upload plans, request and response summaries, provider status, stdout and stderr events, uploaded assets and byte totals, deployment IDs, canonical and preview URLs, manual follow-up, and skipped requirements.
Provider changes include:
•
Google Play uses correct edit validate/commit semantics, including empty-body validate requests with an explicit content length.
•
App Store Connect can upload screenshots, previews, review attachments, assign TestFlight groups, and submit App Review actions through explicit commands.
•
Microsoft Store distinguishes draft updates, private flights, public submission, and certification state.
•
GitHub Releases uses an explicit duplicate-asset policy instead of silently replacing assets.
•
S3 can inspect planned object keys from an artifact manifest and report ok, partial, or missing.
•
Docker registry status checks every configured tag or falls back to tags from docker image metadata.
Some steps remain manual by design. Microsoft Store trailer upload still creates a handoff manifest. Rollback in a provider console stays manual when the provider has no safe API. Fission does not try to recreate those provider portals.

Native video without forcing native dependencies everywhere

Fission 0.8.0 clarifies the video widget contract and native backends.
Video sources are typed, so app code can distinguish assets, files, and URLs instead of passing ambiguous strings through each shell. Native backends are configured per platform. Linux native video is behind the video feature, so projects that do not use it do not need GStreamer development packages.
Static site, SSR, and Web video do not depend on the native GStreamer-backed Linux path.

Selector-driven LiveTest actions

LiveTest can now find UI elements by selector for end-to-end tests and release screenshots. A test can target semantic identifiers, explicit widget IDs, roles, labels, accessibility or test identifiers, and scoped matches when names are duplicated.
It supports actions including tap, activate, focus, hover, right-click, scroll into view, fill, clear, toggle, and select. GetTree now reports semantic identifiers separately from values, so tests do not have to rely on text fields with multiple meanings or coordinate calculations.
The same selectors help with release screenshots. Fission can drive the app, wait for the state you want, and capture the screen without brittle sleeps.

Better semantics and text input behavior

Interactive widgets now expose clearer semantic identities. Radio buttons have their own semantics instead of being treated as generic toggles. That improves accessibility metadata and gives tests a more stable way to find them.
Text selection and controlled-value rendering now keep the visible text, selection, and editing affordances aligned. This fixes cases where the rendered text drifted from the controlled value or selection behaved inconsistently for disabled and read-only inputs.

Generated app guidance is stricter

fission init now writes more complete app guidance. Generated projects recommend:
•
responsive mobile and desktop layouts by default;
•
generated design-system tokens rather than hard-coded styling;
•
i18n setup with at least two languages;
•
one widget implementation per file where practical;
•
semantic metadata for interactive widgets and meaningful regions;
•
shared app cores with thin feature-gated shell entrypoints for multi-platform apps;
•
Fission LiveTest end-to-end checks and screenshot-based manual QA.
The aim is for a generated Fission app to start with the structure of a real product, not a throwaway demo.

Migration notes

Update the Fission dependency to 0.8.0:
fission = { version = "0.8.0", default-features = false, features = ["desktop"] }
If your app uses native video on Linux, enable the video feature and install the GStreamer development packages required by your distribution. On Debian or Ubuntu:
sudo apt install libglib2.0-dev libgstreamer1.0-dev libgstreamer-plugins-base1.0-dev
Before publishing, check that the release is ready:
fission readiness release \
  --target android --format aab \
  --provider play-store --track internal \
  --locale en-US --json
Then publish either from a freshly built artifact or an existing artifact manifest:
fission publish \
  --provider play-store \
  --artifact target/fission/release/android/aab/artifact-manifest.json \
  --track internal --locale en-US --yes --json