You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When attempting to implement the NEProvider overrides for starting & stopping the tunnel on device sleep and wake, I noticed that sending the StopRequest to the .dylib causes the entire NE process to SIGABRT. We'll need to fix this if we'd like the VPN to start and stop itself on sleep and wake.
For example, this can be reproduced by modifying the sleep handler:
Uh oh!
There was an error while loading. Please reload this page.
When attempting to implement the NEProvider overrides for starting & stopping the tunnel on device sleep and wake, I noticed that sending the
StopRequest
to the.dylib
causes the entire NE process toSIGABRT
. We'll need to fix this if we'd like the VPN to start and stop itself on sleep and wake.For example, this can be reproduced by modifying the sleep handler:
Then starting the VPN, and putting the device to sleep. After waking, you'll see an internal error indicating a crash of the NE.
We currently only send the
StopRequest
when shutting down the tunnel, so this crash can't happen with normal use of the app.The text was updated successfully, but these errors were encountered: