v2.0.0-beta.34

Motrix 2.0.0-beta.34

English | 简体中文

Motrix 2.0.0-beta.34 makes BitTorrent and magnet downloads more resilient when
Web Seeds fail, peer discovery is slow, or a WebUI misses the file-selection
event. It also adds an optional timeout that can start all files when a magnet
selection remains unconfirmed. It is intended for public distribution only
after every protected release gate passes.

Highlights

• A failed HTTP Web Seed no longer stops an entire BitTorrent task through
  aria2's file-not-found limit. The BT-specific policy covers torrent and
  magnet submission, metadata retry and recovery, and torrent re-add paths,
  while ordinary HTTP downloads keep their configured policy
  (#2088).
• Magnet metadata discovery now waits 600 seconds by default, with a configurable
  maximum of 900 seconds. Existing settings using the former 120-second default
  are migrated once; other saved values and later user edits are preserved
  (#2088).
• Pending magnet file selections recover after refresh or reconnect, multiple
  pending tasks queue behind the active form, and the task inspector provides a
  manual selection action with pending and failure feedback. Direct WebUI
  responses and dialog revisions prevent stale forms from replacing or closing
  newer selections (#2089).
• Settings → BitTorrent has an opt-in automatic selection timeout. When
  enabled, a magnet task that remains unconfirmed after metadata is ready starts
  all files after 60 seconds by default, configurable from 10 to 3,600 seconds.
  The host-owned timer survives renderer closure and preserves elapsed selection
  time across restarts (#2089).
• Builtin plugin downloads retry transient failures with bounded exponential
  backoff while retaining digest and signature verification. License checks are
  isolated from application setup so they no longer fetch builtin plugins
  (#2089).

Before testing

This is prerelease software. Back up existing Motrix application data and
downloads before installing it. Migration from Motrix v1 data has not yet been
validated, so do not use your only copy of v1 data with this beta.

When practical, test v2 in parallel using a separate OS account, machine, or
Docker data directory. Test torrents containing unavailable Web Seeds, slow
magnet metadata discovery, selection recovery after refreshing or reconnecting
the WebUI, manual selection from the task inspector, and the optional automatic
selection timeout across an application restart.

After the protected release completes, Snap testers can install the strictly
confined build with sudo snap install motrix --edge. Existing installations
tracking latest/edge should upgrade to the same beta.34 revision set.

Planned downloads after release gates pass

Distribution	Architectures	Planned output
macOS 13 or later	arm64 (Apple Silicon), x64 (Intel)	DMG and ZIP
Windows	x64	Unsigned NSIS installer (.exe) and ZIP
Linux	x64, arm64	AppImage, DEB, and RPM
Flatpak Native Host companion	linux/x64, linux/arm64	Motrix-Native-Host-2.0.0-beta.34-linux-<arch>.tar.gz
Docker Hub / GHCR	linux/amd64, linux/arm64	Immutable 2.0.0-beta.34 tag in both registries
Snap Store	amd64, arm64	Verified build set on latest/edge

After every container gate passes, the versioned image references will be
docker.io/motrixapp/motrix-server:2.0.0-beta.34 and
ghcr.io/agalwood/motrix-server:2.0.0-beta.34. See the
Docker Server deployment guide
for storage, networking, remote Extension pairing, and upgrade guidance.

Distribution notes

• AppImage desktop integration is opt-in and confined to the current user's
  XDG data directory. Browser-extension hand-off is not yet available from the
  AppImage package because its Native Messaging host does not have a stable
  path outside the mounted image.
• Flatpak is validated separately and is not published by the release tag; the
  GitHub prerelease includes its Native Host companion archives.
• Windows arm64 and all 32-bit packages are not available.
• Windows packages are unsigned and may trigger a Windows SmartScreen warning.
  Download them only from the official GitHub prerelease after it is published.
• Beta container tags are immutable and do not update latest, stable, or
  other stable floating tags.
• The Snap package is strictly confined. Its approved personal-files
  interface is limited to registering Native Messaging host manifests for
  supported browsers. Beta publication updates latest/edge only; it does not
  promote the build to candidate or stable.

Feedback

Please report reproducible problems through
GitHub Issues. Include your
operating system, architecture, package type, and the steps needed to reproduce
the issue.

What's Changed

• fix(bt): isolate web seed failures and extend magnet timeout by @agalwood in #2088
• fix(bt): recover magnet file selection and add timeout fallback by @agalwood in #2089
• chore(release): prepare 2.0.0-beta.34 by @agalwood in #2092

Full Changelog: v2.0.0-beta.33...v2.0.0-beta.34