aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/ui/src/main/java/com/wireguard/android/util/ErrorMessages.kt (follow)
Commit message (Collapse)AuthorAgeFilesLines
* ui: reformat all codeJason A. Donenfeld2023-05-051-36/+47
| | | | Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
* ui: always show visible localized error messagesJason A. Donenfeld2023-04-071-3/+3
| | | | Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
* global: bump copyright dateJason A. Donenfeld2023-03-211-1/+1
| | | | Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
* ui: allow importing tunnel from an QR image stored on the deviceNikita Pustovoi2022-03-061-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | Add a new feature to import a tunnel from a saved QR image, this feature integrates into 'import from file' flow, however adds a condition, if file is an image, attempt to parse it as QR image file. My use case for this feature, is to allow easier sharing of tunnels to family. Scanning QR code is ok when you have an external display to show it, but if you sent QR code to someone, there is no way to import it in the app. If you share a config file, that becomes way harder for a non-technical person to import as now they need to find a file with that name in the file picker etc etc, Where the images are very visible in the file picker, and user can easily recognize it for import. Testing: - Click "+" blue button, try to import a valid `.conf` file - the 'original' file flow should not be affected - Click "+" blue button, try to import a valid QR code image - if QR code was parsed, then a new tunnel will be added. - Click "+" blue button, try to import an invalid QR code image - Error message will be shown Signed-off-by: Nikita Pustovoi <deishelon@gmail.com> Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
* global: bump copyright yearJason A. Donenfeld2021-10-291-1/+1
| | | | Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
* tunnel: retry DNS resolution for 10 secondsJason A. Donenfeld2021-05-261-1/+2
| | | | | | | | | | This has several problems: 1) it blocks the main thread; 2) it doesn't distinguish between a permanent error and a transient one; 3) the 10 seconds is hard coded; 4) there's no way for the user to cancel it. We'll have to improve this. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
* ui: queue up tunnel mutating on activity scope instead of fragment scopeJason A. Donenfeld2020-09-261-2/+2
| | | | | | | | | | | | Fragment scopes get cancelled when the fragment goes away, but we don't actually want to cancel an in-flight transition in that case. Also, before when the fragment would cancel, there'd be an exception, and the exception handler would call Fragment::getString, which in turn called requireContext, which caused an exception. Work around this by using the `activity ?: Application.get()` idiom to always have a context for strings and toasts. Signed-off-by: Jason A. Donenfeld <Jason@zx2c4.com>
* Convert ErrorMessages to KotlinHarsh Shandilya2020-03-271-0/+138
Signed-off-by: Harsh Shandilya <me@msfjarvis.dev>
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.