diff --git a/disclaimer/index.html b/disclaimer/index.html index 9161b03..26db9bc 100644 --- a/disclaimer/index.html +++ b/disclaimer/index.html @@ -21,7 +21,7 @@ - + @@ -31,23 +31,23 @@ - + - + - - + + - - + +
diff --git a/donation/index.html b/donation/index.html index 5914e98..2572ae4 100644 --- a/donation/index.html +++ b/donation/index.html @@ -21,7 +21,7 @@ - + @@ -31,23 +31,23 @@ - + - + - - + + - - + + diff --git a/faq/index.html b/faq/index.html index 5063d99..e579b5a 100644 --- a/faq/index.html +++ b/faq/index.html @@ -21,7 +21,7 @@ - + @@ -31,23 +31,23 @@ - + - + - - + + - - + + @@ -62,11 +62,11 @@If you see the “You are not connected to any Wi-Fi network.” message, it’s coming from a known iOS 13 bug.
+ +Until Apple fixes it, you may want to try these workarounds:
+ +Unfortunately neither is guaranteed to work. While extremely sorry for the inconvenience, I can’t do more than this about this iOS bug.
+ +Anyway, you can follow this Reddit discussion for updates.
+ +The effect of the new location access requirement in iOS 13 is the inability to trust the connected Wi-Fi network. The app will either trust a bogus “Wi-Fi” or “WLAN” SSID name, or present the alert “You are not connected to any Wi-Fi network.”.
+ +To work around this issue:
+ +Since iOS version 1.9.0, Passepartout switched to a freemium model, which means free to download with paid in-app purchases. Of course, those who purchased former versions of the app will retain full access to all features and providers. Most of the time the upgrade will be seamless. In some cases, however, it will take those users an extra step to restore app functionalities.
@@ -109,17 +137,6 @@That’s why, starting from iOS app 1.9.0, Passepartout will prompt you for a location permission when trusting a Wi-Fi network. Make sure that location services (under “Privacy”) are enabled on your device, otherwise the app will be unable to ask the permission in the first place.
-In Passepartout for iOS up to 1.8.1, the effect of the new location access requirement is the inability to trust the connected Wi-Fi network. The app will either trust a bogus “Wi-Fi” or “WLAN” SSID name, or present the alert “You are not connected to any Wi-Fi network.”.
- -To work around this issue:
- -It can be several reasons, yet most of the time there could be a mismatch in compression framing. E.g. server is using LZO compression framing whereas the client is not, or vice versa. Sometimes the app gracefully shuts down with “Compression unsupported”, sometimes the error can be subtle and packet transmission could just fail silently, resulting in no data exchanged over the wire.
diff --git a/feed.xml b/feed.xml index 766596f..55db1cd 100644 --- a/feed.xml +++ b/feed.xml @@ -1 +1 @@ -