Option to always stay connected to Nebula network

[ambroff]

I have been using Nebula with my iOS device for quite a while and it has been absolutely great.

I plan to add the iOS devices of some people who are not very tech savvy. My goal is to allow them to access some services via Nebula from any network, but I want it to be totally transparent to them.

I have everything working the way that I want it to at this point, except that if the device restarts for any reason the user needs to manually open the Nebula app or VPN settings to connect.

These iOS devices restart so infrequently that even I often forget for a few minutes that I need to re-connect to Nebula after a restart, so someone who is not very tech savvy is going to find this situation pretty frustrating.

It would be ideal if there were a setting in the Nebula app that allowed a user to just specify that a Nebula should always be running. I don't know much about iOS development so I have no idea whether or not that is straightforward.

If it isn't totally obvious how this could be done, I think it would be helpful to integrate with Shortcuts . I would be satisfied if I could just create a shortcut which ensures that a Nebula network connection is up any time the network configuration changes on the device.

[seaniedan]

In case it's useful, Fitbit have a notification that pops up if the app is closed.

[uselpa]

I am exactly in the same situation as @ambroff - currently using Wireguard which reconnects automatically to the site that was active before restart. Thank you for considering this option.

[marekmarecki]

This feature request is also relevant to Android.

[valodiadeseynes]

Exact same situation here.

This feature is especially helpful for organizations whose users are not tech-savvy. Transparence is a huge plus for their acceptation factor.

In my use case this would concern both iOS and Android.

[manuels]

Looks like this behavior was introduced on android intentionally when switching from on-app-start permission requests to on-site-activation permission request in this commit: 37758d4

Would it still possible to implement always-on on android besides this change of permission request?

[johnmaguire]

@manuels The referenced commit removes the VPN from the "Always On" list in the phone settings. This was done because even if enabled, the app is missing the required functionality to support "Always On."

The app supports multiple networks, with only one active at a time. So, to support "Always On," we'll need to know which network the user wants. I expect there are other API calls that will need to be implemented as well.

This is functionality we want to support but have not yet begun work on.