VPN: There are no DNS errors to handle in the app now
This commit is contained in:
parent
6d28240531
commit
97d8570d99
|
@ -21,8 +21,6 @@ class ErrorPresenter {
|
||||||
return ("Unable to remove tunnel", "Internal error")
|
return ("Unable to remove tunnel", "Internal error")
|
||||||
|
|
||||||
// TunnelActivationError
|
// TunnelActivationError
|
||||||
case TunnelActivationError.dnsResolutionFailed:
|
|
||||||
return ("DNS resolution failure", "One or more endpoint domains could not be resolved")
|
|
||||||
case TunnelActivationError.tunnelActivationFailed:
|
case TunnelActivationError.tunnelActivationFailed:
|
||||||
return ("Activation failure", "The tunnel could not be activated due to an internal error")
|
return ("Activation failure", "The tunnel could not be activated due to an internal error")
|
||||||
case TunnelActivationError.attemptingActivationWhenAnotherTunnelIsBusy(let otherTunnelStatus):
|
case TunnelActivationError.attemptingActivationWhenAnotherTunnelIsBusy(let otherTunnelStatus):
|
||||||
|
|
|
@ -13,7 +13,6 @@ protocol TunnelsManagerDelegate: class {
|
||||||
}
|
}
|
||||||
|
|
||||||
enum TunnelActivationError: Error {
|
enum TunnelActivationError: Error {
|
||||||
case dnsResolutionFailed
|
|
||||||
case tunnelActivationFailed
|
case tunnelActivationFailed
|
||||||
case attemptingActivationWhenAnotherTunnelIsBusy(otherTunnelStatus: TunnelStatus)
|
case attemptingActivationWhenAnotherTunnelIsBusy(otherTunnelStatus: TunnelStatus)
|
||||||
case attemptingActivationWhenTunnelIsNotInactive
|
case attemptingActivationWhenTunnelIsNotInactive
|
||||||
|
|
Loading…
Reference in New Issue