v3.3.0
🚀 Flutter V2Ray Client v3.3.0
We’re pleased to release Flutter V2Ray Client v3.3.0, a focused update that moves the embedded Xray core to v26.6.1. If you’re already on 3.2.0, this is the next step: same plugin API and the same Android VPN/TUN stack, with an updated libv2ray and V2rayCoreManager aligned to the latest core line.
🔄 Xray Core v26.6.1
- Upgraded from v26.4.17 to v26.6.1 (embedded core)
- Android ships an updated
libv2ray(AAR) and refreshedV2rayCoreManagerintegration - Picks up upstream fixes and refinements on the 26.x line since 26.4.17
🛠️ What’s in this release
- Core maintenance: latest Xray 26.6.1 for improved stability and compatibility on the current feature set (TUN, transports, obfuscation, pinning, REALITY, XDNS — introduced in 3.2.0)
- Native stack: rebuilt Android artifacts so Gradle and the app bundle use the new core
- No Dart API changes intended for typical integrations — bump the dependency and rebuild
🔄 Compatibility Notes
- Requirements (unchanged): Android API 21+, Flutter 3.16+; still compatible with using OpenVPN in the same project when configured as in 3.1.0
- Migration from 3.2.0
- Update to
flutter_v2ray_client: ^3.3.0 - Run
flutter clean, refresh dependencies, and do a full Android rebuild so the new AAR is picked up - Re-test VPN and proxy-only flows, reconnect, and WiFi ↔ cellular handoff if those matter for your app
- Update to
📝 Testing Recommendations
- Confirm connect / disconnect and status events after upgrade
- Exercise VPN (TUN) and proxy-only modes on your target devices
- Run a long session and a quick background → foreground check
- If you use Hysteria2, UDPhop, or obfuscation configs from 3.2.0, smoke-test with your production server profiles
📦 Install
dependencies:
flutter_v2ray_client: ^3.3.0🙏 Acknowledgments
Thank you to everyone who uses and reports on Flutter V2Ray Client — your feedback drives these core updates.