Missing libtor.so #2328
Comments
|
Looks like it didn't find tor binary. How did you install the app? |
|
Here're contents of the application files in v2.1.2 
|
holmesworcester
changed the title
|
In the last working version, the contents of the same dir looks as follows: 
|
|
I know what the problem is. So far we've been using deprecated |
|
I don't think there's a way to directly access tor binary from the level of code anymore. I looked into the implementation of guardian-project's tor library for Android It spawns a separate thread for tor to run within. I'm not sure if it would work well along with our worker which is probably gonna be better long living and resource trimming resistant. But what's worse is that it uses ControlSocket instead of ControlPort by default. Why is it worse? Because we already have our NodeJS backend adapted to work with CP (it's how it operates on iOS). I see the following options:
@holmesworcester thoughts? |
|
It sounds like we're sure that rolling back RN will work, which then gives us some time to decide when we want to do this. Are there any options we think might be as easy as rolling back RN? If so we could gamble and try one, to try to protect the RN upgrade. If not, it seems best to rollback and then decide when we want to tackle this. If it's helpful to ask Guardian Projects questions, we should do that! Do we have any questions that would be helpful to have answers to? |
|
I'm referring to this thread now
|
|
For future reference, we can also look into this: https://stackoverflow.com/a/77490782 it might remove the need to include the Tor binary like we are doing in #2366 |
|
Version: 2.1.2-alpha.13 I'm not sure if this is a connected issue or something new, but I checked two Android devices and had problems with both of them. Below, you have a screenshot explaining what I mean by "white screen" and logs from the second app. Let me know if you think that it still should be handled in this issue or if this is something new that "deserves" it's own github issue. |
kingalg
changed the title
|
This blocks release for sure. |
|
As per @siepra checks, the issue with the white screen that I mentioned above deserves its own issue as the backend started and Tor bootstrapped, so it's definitely not the same issue. This is a new issue: #2381 This one will be closed as an issue with missing libtor.so that was a main problem in initial post is resolved. |
|
@holmesworcester as per my message above - the white-screen "thing" is an issue and a blocker, but it doesn't have the same origin as #2328, so I'm closing it, and the new issue is moved to another task that I put in the Sprint column. |
Android: [email protected]
Issue: App on android crashes when the user tries to open it. It just blinks for a second and closes. Backend is still running and the app tries to connect.
Below you can see logs. Among them there is this ERROR:
Full logs:
The text was updated successfully, but these errors were encountered: