-
-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Orbot overwrites specified Exit Nodes with "{CA}" after a fresh start #77
Comments
Do you have Canada selected in the left hand side menu? That is the menu that would override any manually settings you have entered. Can you try testing from a fresh install? |
I did not select anything in the left hand side menu. But it appears is if a fresh start of the app would select Canada automatically. I also tried with a fresh install (in order to switch from the f-droid version to the GuardianProject version you have to uninstall Orbot). |
Just an idea: Would it make sence to introduce a setting allowing the user to disable the list of countries in the left hand side menu to solve this problem? That way the user would not be able to select a country and overwrite his exit node settings by accident. |
If he user manually enters something in Settings, it should disable or override the side menu for sure. Will consider this for the next release. |
Thanks a lot! I really appreciate that! ;-) |
Will you have the chance to fix this issue in the upcoming release 16 of Orbot? |
We will do a full triage of all the open tickets in January. never fear! |
Thanks! Great! ;-) |
This should be fixed in the latest beta. There is a new beta release build to try: the "armeabi-v7a" APK should work for most people, or just get the "universal" one if you aren't sure. |
No trouble after first tests! Thanks a lot for fixing this! ;-) |
When you specify exit nodes that should be used by orbot in the settings, current and recent versions of orbot seem to overwrite this setting with "{CA}" after a fresh start of the app. The last version without this problem appears to be 15.0.1-RC-3-PIE from F-Droid.
The text was updated successfully, but these errors were encountered: