-
-
Notifications
You must be signed in to change notification settings - Fork 356
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
[BUG] Regression: 17.0.0 RC 1 works, but 17.2.1 RC 2 and newer crashes immediately upon opening the app #1229
Comments
Anyway you can get a crash log to us? |
How do I get a crash log? (e.g. What command should I use?) As newer versions of Orbot crashes immediately, I don't even have any chance to click on any buttons in Orbot. Android shows a popup that the app has stopped as soon as I open Orbot. |
Hello, I am willing to get a crash log so that developers can look into this issue, but can you please give me instructions on getting a crash log? |
Please check this: https://www.xda-developers.com/how-to-take-logs-android/ |
Thanks @meenbeese - to be clear, just the system log ( Also, do I have to post the log publicly? |
You can email the crashlog to [email protected] or just pull out lines that seem relevant to the crash |
Just to add detail, this is an Intel Android device, and it is running Android 6. The crash is likely related to one of those things. |
@antermin while we would love to support all chips and OS versions, it is increasingly difficult for us to support older devices like this one. Since you do care about privacy and security, it may be best for you to try to upgrade to something newer and more secure. |
Using
I wonder if 20805be is related? Full `pidcat org.torproject.android` output
|
Definitely an Android 6 issue as well. This is a problem with us overaggresively updating "Deprecated Code" when it still functions just fine. I will see what we can do. |
I have seen this error highlighted in Android Studio before. It used to work fine until we lowered the minSdk to 21, at which point I started seeing the error. I can look at it this weekend. |
This is why lowering the minSdk is not trivial and I can't fully justify it in our case. Hopefully, we can bump it to 23 again soon. |
@meenbeese the minSDK for Orbot should always match the minSDK for tor-android. |
Are there any APKs available for trying the fix in #1256? |
Describe the Bug
On my device,
Orbot-17.0.0-RC-1-tor.0.4.7.11-fullperm-universal-release
is the last known good build.Orbot-17.2.1-RC-2-tor-0.4.8.7-fullperm-universal-release
is the first known bad build.The latest version, 17.3.2 RC 1, also doesn't work.
Notes:
To Reproduce
Steps to reproduce the behavior:
Expected Behavior
The app should not crash.
What Custom Configuration Do You Use?
N/A, I haven't changed any configuration.
I uninstalled Orbot before installing the latest version of Orbot to make sure that it is a clean install.
Smartphone (please complete the following information):
Orbot-17.3.2-RC-1-tor-0.4.8.12-fullperm-universal-release
Additional Context
My device's architecture is x86 / x86-64. I wonder if this may have caused the regression.
The text was updated successfully, but these errors were encountered: