Motrix 2.0.0-beta.44
English | 简体中文
Motrix 2.0.0-beta.44 packages the Safari desktop bootstrap in signed macOS
builds, improves registration when upgrading or switching installed copies, and
makes unavailable download metrics easier to distinguish. The Safari extension
remains independently distributed.
Highlights
- Download rows distinguish a real zero transfer speed, an unknown value, and a
metric that does not apply. Paused, completed, queued, and other inactive tasks
leave speed and ETA cells blank; seeding keeps upload speed, and media merging
clears transfer metrics. Zero speeds now participate in numeric sorting
(#2275). - macOS signing now signs Safari helpers before the main executable seals the
app, fixing the unsigned x64 registrar failure. The complete signature,
entitlement, and notarization checks remain required
(#2273). - macOS arm64 and x64 packages now include the Safari bootstrap service,
registrar, and LaunchAgent. The helpers receive their required signatures and
App Group entitlement before the app passes the existing notarization and
package-verification gates (#2271). - Opening the installed Motrix app verifies that the registered service belongs
to that app. Stale or mismatched registrations are rebound with bounded
retries, while a matching service stays running. If macOS requires background
item approval, Motrix preserves that state instead of overriding your choice
(#2271). - Safari bootstrap stops after one nonce request when a running bridge refuses
it, avoiding unnecessary launch attempts and retries. A stopped bridge can
still trigger the cold-launch path. The extension-facing protocol remains
compatible, with regression coverage using the production Swift/Rust adapter
(#2271).
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.
For Safari integration, install or update the signed macOS app, then open the
intended Motrix.app once to register its bootstrap service. Approve the
background item if macOS requests it. Downloading the app alone does not change
registration; opening another signed copy can change the registered owner.
Use a compatible, separately distributed Safari extension and test cold launch
and paired reconnection after the upgrade. Do not delete your database or
pairing credentials to resolve an old launch target.
Automated package and Swift/Rust integration checks do not replace clean-Mac
upgrade and cold-launch acceptance testing.
After the protected Snap workflow completes, testers can install the strictly
confined build with sudo snap install motrix --edge. Existing installations
tracking latest/edge should upgrade to the same beta.44 revision set.
Planned downloads after release gates pass
| Distribution | Architectures | Planned output |
|---|---|---|
| macOS 13 or later | arm64 (Apple Silicon), x64 (Intel)
| Signed and notarized DMG and ZIP |
| Windows | x64
| Unsigned NSIS installer (.exe) and ZIP
|
| Linux | x64, arm64
| AppImage, DEB, RPM, and pacman |
| Flatpak application | x86_64, aarch64
| Motrix-2.0.0-beta.44-<arch>.flatpak
|
| Flatpak Native Host companion | linux/x64, linux/arm64
| Motrix-Native-Host-2.0.0-beta.44-linux-<arch>.tar.gz
|
| Docker Hub / GHCR | linux/amd64, linux/arm64
| Immutable 2.0.0-beta.44 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.44 and
ghcr.io/agalwood/motrix-server:2.0.0-beta.44. See the
Docker Server guide
for storage, networking, and upgrades.
Distribution notes
- Flatpak bundles use application ID
app.motrix.nativeand thebetabranch.
Download each new bundle and install it withflatpak install --user --or-update; no Motrix update remote is configured by these single-file
bundles. Update the Native Host companion separately when using browser
integration. See the
Flatpak guide. - AppImage desktop integration remains opt-in. Browser cold launch requires
the separately enabled Native Messaging host and a registered AppImage path;
reconnecting with a saved pairing also requires a compatible Extension. - Windows
arm64and all 32-bit packages are unavailable. Windows packages are
unsigned and may trigger Windows SmartScreen warnings; download them only
from the official published GitHub prerelease. - Beta container tags are immutable and do not update
latest,stable, or
other stable-channel aliases. - Snap packages use strict confinement. The approved
personal-files
interface is limited to Native Messaging host registration for supported
browsers. Beta publication updateslatest/edgeonly.
Feedback
Report reproducible problems through
GitHub Issues, including your OS,
architecture, package type, and reproduction steps.
What's Changed
- feat(safari): ship signed desktop bootstrap and upgrade registration by @agalwood in #2271
- chore(release): prepare 2.0.0-beta.43 by @agalwood in #2272
- fix(downloads): distinguish unavailable task metrics by @agalwood in #2275
- fix(macos): sign safari helpers before the main executable by @agalwood in #2273
- chore(release): prepare 2.0.0-beta.44 by @agalwood in #2277
Full Changelog: v2.0.0-beta.42...v2.0.0-beta.44