Ok thanks. I had the core helper installed but not updated. It needs to warn if using an older helper, or give more helpful logs to figure out why the connection is not working.
still installs the environment file in .ssh. Is there a way to avoid that?
i have an entire office full of users who suddenly and inexplicably lost their ability to connect to production resources after updating the app. and it was much more challenging than it should have been to identify the cause for the failure.
this behavior powerfully disincentivizes installing updates. that’s really bad.
also, i’m not altogether clear why the two apps must be bundled separately. a single installation package for multiple applications would resolve a lot of this confusion.
That’s our mistake, forgot to add an version mismatch alert I’m really sorry for this, we will certainly improve it in next update.
It’s a long story, the earlier versions of Core Tunnel actually distributed outside of Mac App Store, you can find the discussion from this thread:
TL;DR, Apple rejects apps that access system resources, the functionality is restricted if we didn’t introduce Core Helper. But since Core Helper access system resources (on behalf of Core Tunnel), it has no chance to land on Mac App Store (which is forbidden by Apple).
Distribute Core Helper outside of Mac App Store is a compromise that is acceptable to both Apple and users.