Repository navigation
Releases
v1.1.0
Full Changelog: v1.0.1...v1.1.0
iOxide Desktop 1.0.0-beta.3
desktop-v1.0.0-beta.3 iOxide Desktop 1.0.0-beta.3 (rebuilt with the fix for #8)
v1.0.1
iOxide Desktop 1.0.0-beta.2
Second test build of the iOxide desktop app. It replaces beta 1, which could not get past Proton's human-verification step.
Fixed since beta 1
- Sign-in stuck at "Waiting for verification…". After you solved the challenge, nothing happened. iOxide now opens Proton's own verification page (
verify.proton.me). When you have completed the challenge there, return to iOxide and choose I have completed verification.
This is a beta. The fix is covered by an automated test against a stand-in for Proton's service and follows the method Proton Mail Bridge uses, but it has not yet been confirmed against a real Proton account. If sign-in still fails after verification, please report what the app shows. The stable download is still the command-line release, v1.0.0.
Install
Quit beta 1 from the tray menu first; only one copy of iOxide can run at a time. The builds are not code-signed, so each system asks for confirmation once.
| System | Download | First start |
|---|---|---|
| Windows | …-windows-amd64.zip (or arm64) |
Run ioxide-desktop.exe. If SmartScreen appears: More info, then Run anyway. |
| macOS | …-macos-arm64.tar.gz for Apple silicon, amd64 for Intel |
Move iOxide.app to Applications, then run xattr -dr com.apple.quarantine /Applications/iOxide.app once. |
| Linux | …-linux-amd64.tar.gz (or arm64) |
Install GTK 4 and WebKitGTK 6 (Ubuntu 24.04: sudo apt install libgtk-4-1 libwebkitgtk-6.0-4), then run ./ioxide-desktop. Needs a Secret Service keyring and a tray. |
SHA256SUMS holds checksums for all archives. To look around without signing in, start the app with -preview: it shows every screen with sample data.
What to test
- Sign-in, including the verification step, an authenticator code and a separate mailbox password if your account uses them.
- Connecting a calendar app on the same computer, and on a phone through Tailscale or your own HTTPS address.
- The tray menu: start and stop the bridge, connection details, quit. Closing the window should leave iOxide running in the tray.
- Start at login, and unlocking an account that was added with the command-line version.
Known limits
- Do not run the command-line bridge and the desktop app on port 8081 at the same time.
- Only authenticator-app codes are supported as a second factor, not security keys.
- The computer running iOxide must stay awake for other devices to sync.
Report problems in issues. Leave out passwords, bridge passwords and verification tokens.
v1.0.0
Full Changelog: https://github.com/mrk1987/iOxide/commits/v1.0.0