Opened 5 years ago

Last modified 3 years ago

#16392 new defect

If Orbot has just been installed it cannot be started by

Reported by: dschuermann Owned by: n8fr8
Priority: Medium Milestone:
Component: Applications/Orbot Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


At OpenKeychain we will allow key updates to be routed over Orbot in a future version. This requires Orbot to be installed and then we use to start Orbot.
This does not work when Orbot hasn't been properly started before without using this Intent, i.e., it hasn't really been set up.

This should be handled somehow. At least there needs to be a message that the User first needs to start Orbot on its own.

Child Tickets

Change History (3)

comment:1 Changed 5 years ago by n8fr8

Hmm.... interesting. We are reworking this very Intent right now, so I will make sure Hans checks this issue out.

comment:2 Changed 5 years ago by dschuermann

I tested it again with a clean install and it worked this time. Maybe it was some kind of a race condition.
Before the activity showed up but the Droid didn't raise his hands ;) (Was not really started)

comment:3 Changed 3 years ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

Note: See TracTickets for help on using tickets.