Cannot log in: `No API Connectivity`

[barracuda156]

Describe the bug
The app does not log in anymore. The same account credentials work fine on the website, account status is normal.

OS and app information:

• OS: macOS 10.15.7
• App version 2.7.14

To Reproduce
Steps to reproduce the behavior:

1. Launch the app.
2. Try logging in.
3. See the error.

Expected behavior
The app should allow to log in to the account.

Screenshots

[bernerdad]

Hello. You'll unfortunately require a newer app version and OS to log in now. We've made changes to the API and macOS 11 is now our minimum supported version, with macOS 12 becoming the minimum sometime next year.

[barracuda156]

@bernerdad Will it work to build from source? I am not interested to upgrade from Catalina on my Intel machine, so some alternative solution is desirable.
Just in case, CLI app will do, I can live without a GUI.

[bernerdad]

Building from source to get macOS 10.15 support might be challenging. You'd have to roll the Qt version we use back to the last version supporting that OS (Qt 6.4). We're currently using Qt 6.8. There are also macOS API calls we make that require a newer macOS version, but one could comment those out and hope they don't break any core functionality. An AI, like Claude Code, likely would be able to help with a lot of the heavy lifting here. The CLI for macOS/Windows requires the GUI to function, so that won't help here either. Sorry we couldn't give you better news here.

[barracuda156]

@bernerdad I think that Qt 6.8 and maybe 6.10 build for Catalina in components that you use. Webengine does not, and I am not gonna try fixing it, but AFAIU it is not needed. The base and network should be at least fixable with little to moderate effort, if not building yet.
It is generally doable to backport the code to earlier Qt versions too (I had done that for Qt5-to-Qt4), though I did not look into that here specifically. If it turns out to be a lot of work, I rather try switching to Qt4 right-away, and then get this working on legacy macOS, which I still use on PowerPC hardware.

Besides, third-party OpenVPN clients are supported, as before? In the worst case I could use Tunnelblick on Catalina for a while, if native client is broken and fixing it takes time.

[bernerdad]

You'll also need the widgets Qt module. With respect to "third-party OpenVPN clients are supported", are you referring to this feature?

[barracuda156]

You'll also need the widgets Qt module.

I think it is a part of the base, at least there is no separate port for them.

With respect to "third-party OpenVPN clients are supported", are you referring to this feature?

I guess so. I did it long ago for a PowerMac, and it worked fine last time I tried (but that was a few months ago, perhaps).

[barracuda156]

The CLI for macOS/Windows requires the GUI to function, so that won't help here either.

A bit on a side note, could you say how it can build on Linux apparently without any Qt6 dependencies? https://aur.archlinux.org/packages/windscribe-v2-bin?all_deps=1&O=10
CMakeLists seem to require Qt6 libs regardless of the platform.

[bernerdad]

The CLI for macOS/Windows requires the GUI to function, so that won't help here either.

A bit on a side note, could you say how it can build on Linux apparently without any Qt6 dependencies? https://aur.archlinux.org/packages/windscribe-v2-bin?all_deps=1&O=10 CMakeLists seem to require Qt6 libs regardless of the platform.

The Qt dep is built as a static lib via vcpkg on all platforms, so no dll/dylib/so required.