Releases: jonnyhyman/ResolveCollaboration
Release 0.1.2 Beta
Resolve Mission Control Client
This beta is not notarized, so some security bypassing must be done if running from binaries:
macOS
When you open the app, it'll show this dialog:
Open System Preferences > Security and Privacy ... Click Open Anyway
- Because this is a development release, the
.app
is not notarized - If the above still fails, try running
Resolve Mission Control Debug
and copy the errors in the Terminal to a new Issue
Windows 10
Windows will issue a "SmartScreen" page. Go to More info
Click Run Anyway
Changelog:
- Made optional selection between
all internet traffic
andwireguard traffic only
using thewg_only
path in config file - Updated authentication with time-based salt
- New icon!
Release 0.1.1 Beta
Resolve Mission Control Client
This beta is not notarized, so some security bypassing must be done if running from binaries:
macOS
When you open the app, it'll show this dialog:
Open System Preferences > Security and Privacy ... Click Open Anyway
- Because this is a development release, the
.app
is not notarized - If the above still fails, try running
Resolve Mission Control Debug
and copy the errors in the Terminal to a new Issue
Windows 10
Windows will issue a "SmartScreen" page. Go to More info
Click Run Anyway
Changelog:
- Solved crash due to Wireguard disconnect
- Allow IPv4, IPv6, and Domain based connections
Release 0.1 Beta
Resolve Mission Control Client
This beta is not notarized, so some security bypassing must be done if running from binaries:
macOS
When you open the app, it'll show this dialog:
Open System Preferences > Security and Privacy ... Click Open Anyway
- Because this is a development release, the
.app
is not notarized - If the above still fails, try running
Resolve Mission Control Debug
and copy the errors in the Terminal to a new Issue
Windows 10
Windows will issue a "SmartScreen" page. Go to More info
Click Run Anyway
Changelog:
- Codesigned macOS app
- Windows executable
- Beta UI Update
- Persistent configuration file
- Updates of networking to conform to
- Wireguard config template now tunnels traffic correctly and allows IPv4 and IPv6 traffic
- Added Persistentkeepalive to Wireguard template
- Made Resolve Database Timeout message more descriptive and accurate
- Asyncio deprecation warning resolved
Release 0.0 Alpha 2
Resolve Mission Control Client
-
Because this is a development release, the
.app
is not code-signed, and macOS thinks that apps that aren't code-signed and are downloaded from the internet are bad. -
You will almost certainly get an error saying
"Resolve Mission Control is damaged and can't be opened"
. -
To force it to launch, open Terminal and run:
xattr -cr "/path/to/Resolve Mission Control.app"
- /path/to should be wherever you saved unzipped the zip, so in most cases:
xattr -cr "Downloads/macOS-Resolve.Mission.Control-v0.0.2/Resolve Mission Control.app"
- /path/to should be wherever you saved unzipped the zip, so in most cases:
-
Then double-click
Resolve Mission Control Client.app
and it should open -
If the above still fails, please post an Issue
Changelog:
- Updated UI
- Persistent configuration file
- Updates of networking to conform to
- Wireguard config template now tunnels traffic correctly and allows IPv4 and IPv6 traffic
- Added Persistentkeepalive to Wireguard template
- Made Resolve Database Timeout message more descriptive and accurate
- Asyncio deprecation warning resolved
Version 0.0 Alpha 1
Files
Resolve Collaboration.app
: This is the main app to runResolve Collaboration
: Run this if the.app
doesn't work - it should give you a detailed debug trace of what went wrong. Then head to the Issues page and see if anyone else has had the same problem! If not, post an issue!
Change-log
- Built with the
pyinstaller
dev branch, version 5.0 which resolve's some Big Sur issues - Resolves macOS Catalina styling issues
- Resolved a Catalina warning
- Launches on macOS Big Sur???
Version 0.0 Alpha 0
First macOS release!
- Has not been thoroughly tested
- Basic functionality seems to work.
- If you don't follow the straight-line path for each setup step, you may run into crashes. (Mostly: don't click "Cancel" on dialogs)