orbot
orbot copied to clipboard
guardianproject
Orbot no longer broadcasts a status message if it is already running when it receives an ACTION_START intent
In version 16.4.1-RC-2-tor.0.4.4.6 and previous, Orbot would broadcast a status message with the string "ON" if it was already connected when it received a "org.torproject.android.intent.action.START" intent. Beginning with version 16.6.0-RC-2-tor.0.4.6.9 this is no longer the case.
It does continue to broadcast the "ON" status update after it connects if it isn't connected when it receives the ACTION_START intent.
This is a problem for Privacy Browser, which uses the status broadcast to decide whether to display a "Waiting for Orbot" dialog. It can be tested by enabling the Tor proxy in the settings.
Privacy Browser has a bug report regarding the issue at https://redmine.stoutner.com/issues/814.
Orbot 16.6.1-rC-3-tor.0.4.6.10 exhibits the opposite behavior. If Orbot is not running and is started by another app with the "org.torproject.android.intent.action.START" intent, it starts and connects but never broadcasts the "ON" status update when it connects.
If Orbot is already running but not connected, it connects and correctly broadcasts the "ON" status updated. If it is already connected it correctly broadcasts the "ON" status update.