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
{{ message }}
This repository has been archived by the owner on Sep 29, 2024. It is now read-only.
While observing the VPN status notification using NotificationCenter and this libraries VPNNotification struct app crashes when attempting to retrieve a value that does not currently exist.
Connect to VPN and try to retrieve notification.vpnError in your notification reciever.
What is the current bug behavior?
App crashes with uncatchable exception (fatalError(...)).
What is the expected correct behavior?
A catchable exception is thrown.
Relevant logs and/or screenshots
Possible fixes suggested remediation
The least you can do is instead of using fatalError(...) if value does not exist in userInfo throw a catchable exception, but would prefer to somehow recieve an enum/result value of either error/status in VPN status notification.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Summary
While observing the VPN status notification using
NotificationCenter
and this librariesVPNNotification
struct app crashes when attempting to retrieve a value that does not currently exist.Steps to reproduce
Start observing VPN status using:
Connect to VPN and try to retrieve
notification.vpnError
in your notification reciever.What is the current bug behavior?
App crashes with uncatchable exception (
fatalError(...)
).What is the expected correct behavior?
A catchable exception is thrown.
Relevant logs and/or screenshots
Possible fixes suggested remediation
The least you can do is instead of using
fatalError(...)
if value does not exist in userInfo throw a catchable exception, but would prefer to somehow recieve an enum/result value of either error/status in VPN status notification.The text was updated successfully, but these errors were encountered: