Updates and upgrading
From 26.9.5 to 26.10.2
- Enable optional Fragment in Smart Routing or ordinary Custom Routing. Advanced templates can supply their own fragmentation parameters.
- Use optional LAN proxy sharing for HTTP and SOCKS5 clients on a trusted network. It has no authentication and applies on the next VPN start from the app; complete Raw JSON owns its own listeners. Review the documented Apple platform limitation.
- Let Tasker or Automate start and stop VPN with Android automation. Authorization uses a device token; background starts reuse the last configuration generated by an in-app connection.
- Windows MSIX uses Vole for system-VPN integration, with improved connection cleanup and packaging. Start-menu and pinned icons retain their intended padding. EXE/ZIP continue to use Xray native TUN.
- Updated Xray configuration compatibility and improved import/save validation, startup failure handling and runtime cleanup.
Normal updates retain configurations and preferences. Fragment, LAN sharing and Android automation are off by default. Sharing settings are device-local and are not transferred in connection backups. After changing them, use the app to start VPN so background starts can reuse the updated configuration.
From 26.9.4 to 26.9.5
- View subscription plan information, including usage, quota, remaining traffic, and expiry when supplied by your provider. Figures refresh with the subscription; they are not live traffic counters.
- Edit JSON with field, value, tag, and GeoData suggestions, clearer syntax-error locations, and improved copy/paste menus. Saving no longer overwrites edits made while an earlier save is in progress.
- Use the optional desktop local HTTP API to validate configuration text or generate runtime previews from trusted local tools. It is off by default, requires a Token, and cannot save configurations or start VPN.
- Import and export Hysteria2 share links. Legacy VMess QR JSON and Clash/Mihomo configuration imports remain unsupported.
- Improve configuration import and dependency handling, Windows/Linux outbound-interface policy for UDP hopping, and Windows packaging compatibility.
- Keep a stable macOS menu-bar icon: speed text is no longer shown there. Current-connection speeds and traffic remain on Connect; Android also displays them in its widget and VPN notification.
Existing configurations and preferences are preserved by the database upgrade. A normal update from 26.9.4 does not require a reset or reinstall. Review local API requests before sending them: validation is not a sandbox or a connectivity guarantee.
From 26.9.3 to 26.9.4
- Android adds a compact 4×2 home-screen widget, current-connection statistics in the VPN notification, and background start/stop controls. Missing configuration or authorization still opens the app.
- macOS uses an integrated title bar and translucent sidebar with improved desktop layouts. Menu-bar speed display introduced in 26.9.4 is removed in 26.9.5.
- iOS offers an optional VPN-icon hiding workaround with documented routing and system limitations.
From 26.9.2 to 26.9.3
- Back up connection configurations to one replaceable file: iCloud on Apple, a system-selected file on Android, or a OneDrive-synced folder on Windows EXE/ZIP/MSIX. Automatic backup has its own 1/3/7-day interval, defaulting to 3 days, and requires destination confirmation before the first write.
- Restore a readable backup without waiting for GeoData downloads. Missing custom data remains pending; only configurations that depend on it require those files. Update restored subscriptions separately to fetch their nodes. Connect and Servers empty views provide a restore shortcut.
- Use advanced Custom Routing JSON for supported DNS, routing, sniffing, FakeDNS pools, and additional inbounds while retaining app-managed nodes.
- Enable optional FakeDNS in Smart Routing or ordinary Custom Routing. Ordinary rules also support protocol and local operating-system conditions.
- Existing complete Raw JSON
tunInentries retain their non-managed settings; OneXray applies the required platform-owned settings instead of replacing the entire inbound. - AI configuration guides provide prompts and import examples. Detail pages remain inside the current tab, with Back returning to the originating page.
The in-place database upgrade preserves existing configurations and preferences. Existing custom routes remain ordinary routes; FakeDNS is off until enabled. Ordinary and advanced custom routes share the three-configuration limit. Raw JSON keeps its three-item creation limit, without hiding legacy entries above it. A normal update from 26.9.2 requires neither a reset nor a reinstall.
Backups are unencrypted and can contain credentials, Age private keys, and HWID. They exclude files, subscription node caches, device settings, and the app’s final-exit selection. Restore is an explicit replacement operation, not an automatic part of updating. A provider write is not proof of completed cloud synchronization.
From 26.9.1 to 26.9.2
26.9.2 builds on the redesigned interface introduced in 26.9.1:
- Configure a local DNS address for direct traffic in Smart or Custom Routing, and edit the three tunnel DNS settings.
- Optionally send a stable, randomly generated subscription HWID. It is off by default and does not identify your hardware.
- Use four mobile app-icon shortcuts and expanded desktop tray menus.
- Add Apple route exclusions when Capture all traffic is off.
- Follow a shorter first-run flow, with platform authorization handled when entering the main interface. Connection failures now show more specific causes.
- Geodata automatic updates run only while connected. Failed updates retain the previous files and do not restart or disconnect the VPN.
- Windows packages include the matching Microsoft Visual C++ runtime. Desktop Core lifecycle, VPN status, window behavior, sharing, and traffic refresh are improved.
The in-place database upgrade preserves nodes, subscriptions, Raw JSON, custom routes, preferences, and measured latency. New HWID switches remain off. Existing routes keep the default local DNS address unless you change it. A normal update from 26.9.1 does not require reinstalling the app or repeating Setup.
From v26.8.4 and earlier
The following changes apply to the older product model, not to normal updates from 26.9.1 or 26.9.2. Version 26.9.1 introduced four main tabs and separate server and routing choices.
Before updating
Keep independent copies of configurations you may need to recreate. The new app does not import old backup ZIP archives. Check which installation channel you are using, especially on Windows.
Retained data
The database upgrade retains local nodes, subscriptions, and Raw JSON configurations. Existing Raw entries above the three-item creation limit remain visible and usable; adding more is disabled.
Old Profile and Full Config records are not part of the new UI or connection workflow. They are not automatically converted into custom routes. Recreate the needed rules in Custom Routing, or prepare a compatible complete configuration for Raw JSON.
Running preferences are reset when upgrading from the old product model. Review the selected server source, routing, permissions, and platform VPN settings before connecting. Node latency information is measured again.
Where features moved
| Previous workflow | Current workflow |
|---|---|
| Home node list and separate subscriptions | Servers, grouped by subscription or location |
| Simple Profile and separate Xray Profiles | Smart Routing and shared Advanced settings |
| Structured Full Config | Custom Routing for supported rules; Raw JSON for complete configurations |
| Rule / Global / Direct modes | Smart Routing / All via VPN / Custom Routing |
| Profile-level log and tunnel settings | Advanced > VPN Tunnel / Xray |
| Backup and restore | Single-file JSON connection backup; old ZIP backups are not supported |
| Historical/device traffic totals | Removed; current-connection counters and speeds only |
The old standalone Direct mode is not a current traffic-method choice. Direct remains an action inside Smart and Custom Routing.
Windows channels
EXE/ZIP use native TUN with UAC; MSIX uses Windows system VPN. They have separate data locations, startup integration, and quit behavior. Do not assume installing one channel imports the other’s data.