briar issueshttps://code.briarproject.org/briar/briar/-/issues2022-02-28T15:52:29Zhttps://code.briarproject.org/briar/briar/-/issues/2097ActivityNotFoundException for OPEN_DOCUMENT intent2022-02-28T15:52:29ZakwizgranActivityNotFoundException for OPEN_DOCUMENT intent* Android version: 11
* Phone model: Pixel 4a (sunfish)
* Briar version: 1.3.5 (0040753)
* User feedback: "I tried to press the button to change profile picture."
Stacktrace:
```
No Activity found to handle Intent { act=android.intent.a...* Android version: 11
* Phone model: Pixel 4a (sunfish)
* Briar version: 1.3.5 (0040753)
* User feedback: "I tried to press the button to change profile picture."
Stacktrace:
```
No Activity found to handle Intent { act=android.intent.action.OPEN_DOCUMENT cat=[android.intent.category.OPENABLE] typ=image/* (has extras) }
android.content.ActivityNotFoundException: No Activity found to handle Intent { act=android.intent.action.OPEN_DOCUMENT cat=[android.intent.category.OPENABLE] typ=image
/* (has extras) }
at android.app.Instrumentation.checkStartActivityResult(Instrumentation.java:2067)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1727)
at android.app.Activity.startActivityForResult(Activity.java:5314)
at androidx.activity.ComponentActivity.startActivityForResult(ComponentActivity.java:574)
at androidx.core.app.ActivityCompat.startActivityForResult(ActivityCompat.java:234)
at androidx.activity.ComponentActivity$2.onLaunch(ComponentActivity.java:208)
at androidx.activity.result.ActivityResultRegistry$3.launch(ActivityResultRegistry.java:224)
at androidx.activity.result.ActivityResultLauncher.launch(ActivityResultLauncher.java:47)
at androidx.fragment.app.FragmentManager.launchStartActivityForResult(FragmentManager.java:3000)
at androidx.fragment.app.Fragment.startActivityForResult(Fragment.java:1424)
at androidx.fragment.app.Fragment.startActivityForResult(Fragment.java:1398)
at org.briarproject.briar.android.settings.SettingsFragment.lambda$onCreatePreferences$0(SettingsFragment.java:64)
at org.briarproject.briar.android.settings.SettingsFragment.lambda$onCreatePreferences$0$SettingsFragment(Unknown Source:0)
at org.briarproject.briar.android.settings.-$$Lambda$SettingsFragment$aLVt4dIN9PUOagzsIXcpqTymkBo.onPreferenceClick(Unknown Source:2)
at androidx.preference.Preference.performClick(Preference.java:1184)
at androidx.preference.Preference.performClick(Preference.java:1166)
at androidx.preference.Preference$1.onClick(Preference.java:181)
at android.view.View.performClick(View.java:7448)
at android.view.View.performClickInternal(View.java:7425)
at android.view.View.access$3600(View.java:810)
at android.view.View$PerformClick.run(View.java:28305)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:223)
at android.app.ActivityThread.main(ActivityThread.java:7664)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
```Android 1.4Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2096Crash after leaving Briar in the background before the account is actually cr...2023-03-15T12:34:51ZIvanaCrash after leaving Briar in the background before the account is actually created**Steps to reproduce **
- Install Briar on a device (I used HTC One M9 API24 and Nokia 3.1 API30)
- Open Briar app
- Create a nickname, tap Next
- Crete the password and confirm it, tap Next
- Then allow Briar to run in the background, ...**Steps to reproduce **
- Install Briar on a device (I used HTC One M9 API24 and Nokia 3.1 API30)
- Open Briar app
- Create a nickname, tap Next
- Crete the password and confirm it, tap Next
- Then allow Briar to run in the background, and then when given information 'To run in the background, Briar needs to be locked to the recent apps list' tap on 'Protect Briar'
- Then you're given this dialogue box ![device-2021-06-29-114947](/uploads/43a9fe5f5e6f9a7efe0ac765a0b9d089/device-2021-06-29-114947.png)
- at that point leave briar and go to check if briar is in the list of recently used apps
- do not change anything, just look, then come back to Briar
- Briar crashes
Here are log files of the three crashes
[crash_HTC_One_M9_29062021.txt](/uploads/3dc78f523e125a26b53bee65aec1d3bb/crash_HTC_One_M9_29062021.txt)
[Crash_HTC_One_M9_2_29062021.txt](/uploads/b1138ed3eb6bbd319ff6cbaeb64bc4d6/Crash_HTC_One_M9_2_29062021.txt)
[crash_Nokia_3.1_29062021.txt](/uploads/c477c5f0c459fc17209a18b2b620108f/crash_Nokia_3.1_29062021.txt)Android 1.4https://code.briarproject.org/briar/briar/-/issues/2095Add option to use system's Tor binary2023-10-10T18:11:51ZNicoAdd option to use system's Tor binaryThis is most likely needed for a release to Debian (~~https://code.briarproject.org/briar/briar-gtk/issues/38~~ https://code.briarproject.org/briar/briar-desktop/-/issues/261).This is most likely needed for a release to Debian (~~https://code.briarproject.org/briar/briar-gtk/issues/38~~ https://code.briarproject.org/briar/briar-desktop/-/issues/261).https://code.briarproject.org/briar/briar/-/issues/2094user report: RSS feeds are not in chronological order2021-08-27T11:46:04Zsysteruser report: RSS feeds are not in chronological orderA user reports that their RSS feeds are always not in chronological order. I could not reproduce this issue.
reporting source:
https://social.tchncs.de/@noxr/106461720184380659A user reports that their RSS feeds are always not in chronological order. I could not reproduce this issue.
reporting source:
https://social.tchncs.de/@noxr/106461720184380659https://code.briarproject.org/briar/briar/-/issues/2089Headless BriarService ignores startup errors2022-01-03T16:37:55ZakwizgranHeadless BriarService ignores startup errorsStartup errors returned by LifecycleManager#startServices() are ignored by briar-headless's BriarService.Startup errors returned by LifecycleManager#startServices() are ignored by briar-headless's BriarService.https://code.briarproject.org/briar/briar/-/issues/2088Sharing Briar offline - Crash when wifi on device is OFF and 'Start sharing' ...2021-12-07T15:20:36ZIvanaSharing Briar offline - Crash when wifi on device is OFF and 'Start sharing' tapped on Briar screenSteps to reproduce:
1. Device: Samsung Mini I9195 (API19) - go to device settings and switch the wi-fi OFF
2. Go to Briar app > settings > Share Briar app offline
3. Tap Start Sharing button
Expected results:
1. As the wifi gets switc...Steps to reproduce:
1. Device: Samsung Mini I9195 (API19) - go to device settings and switch the wi-fi OFF
2. Go to Briar app > settings > Share Briar app offline
3. Tap Start Sharing button
Expected results:
1. As the wifi gets switched ON during this process, the expected would be for the briar app sharing to continue as normal
Actual results:
1. Briar app crashes. (Reproduced 3 times in a row)
Attached screenshot of device settings, movie of user actions on Briar and Android Studio logfile for the device during this process.
![device-2021-06-23-133045](/uploads/03642e88edf23c9f00e13969cc8e08d3/device-2021-06-23-133045.mp4)[crash_samsung_mini_23062021.txt](/uploads/f4e4ca1973fc75867ea1b65b7a533d5a/crash_samsung_mini_23062021.txt)![device-2021-06-23-133011](/uploads/05ff2fdb19bc1d0bcb052c1c4e3fc51b/device-2021-06-23-133011.png)
Crash report sent from the device as well.
Checking what happens in the same scenario for devices:
- Pixel 2 (API30) - user is given a message that the wifi needs to be on and then they are taken to the device settings to enable the wi-fi = OK
- Nokia 3.1 (API29) - as Pixel2 = OK
- Samsung A01 Core (API29) - as Pixel 2 = OK
- HTC One M9 (API24)Android 1.4SebastianSebastianhttps://code.briarproject.org/briar/briar/-/issues/2085No transport keys for contact who has deleted us and been reintroduced2023-03-31T13:23:27ZakwizgranNo transport keys for contact who has deleted us and been reintroducedIf a contact has deleted us and then been reintroduced by a mutual contact, we end up without any transport keys that can be used for communicating with the reintroduced contact.
When deleting us, the contact will have removed the keys ...If a contact has deleted us and then been reintroduced by a mutual contact, we end up without any transport keys that can be used for communicating with the reintroduced contact.
When deleting us, the contact will have removed the keys that we previously shared. When re-adding us, the contact will have stored the new keys created by the introduction, but we fail to store these when a ContactExistsException is thrown:
https://code.briarproject.org/briar/briar/-/blob/00407539d32147995ffb184ff77ab7c9c53c9920/briar-core/src/main/java/org/briarproject/briar/introduction/IntroduceeProtocolEngine.java#L453
The contradictory comments at lines 457 and 472 above suggest some confusion about the right behaviour in this case. To communicate with the reintroduced contact we should store the new keys, which will be used in preference to any existing keys as they're newer. In other words, the call to addRotationKeys() should be moved outside the try/catch block.https://code.briarproject.org/briar/briar/-/issues/2081Add to FAQ most frequent reasons why Briar fails to connect to a contact2021-06-17T12:44:27ZsysterAdd to FAQ most frequent reasons why Briar fails to connect to a contactAdd to FAQ most frequent reasons why Briar fails to connect to a contact
This is a first draft, a suggestion to include this or something like that to the FAQ.
Why is connecting to another Briar user not working for me?
There are 4...Add to FAQ most frequent reasons why Briar fails to connect to a contact
This is a first draft, a suggestion to include this or something like that to the FAQ.
Why is connecting to another Briar user not working for me?
There are 4 reasons that usually cause this, and they are easy to resolve. If you encounter another reason, please get in touch with us.
**1. You can your contact must be online over the same connection type.**
Make sure that your and your contacts own status is online at least over one of the same connection type. (internet/wifi/bluetooth)
You can check your status by touching on the menu symbol or by swiping from left to right.
The gray color means that briar will not connect over this connection type and green means it has connection. Orange means it has connection issues. Touch on it to read more and change the connection type if necessary. If it stays orange for a while, restarting your phone might fix it. Also make sure you granted Briar the necessary permissions and that you both have turned on internet/wifi/bluetooth.
If you want to reach your contact over bluethooth, you both must have a functioning bluetooth connection.
If you want to reach your contact over wifi, you both must be connection to the same wifi.
If you want to reach your contact over the internet, you both must have a functioning internet connection.
**2. clocks must be in sync.**
Make sure that your clock is in sync with the one of your contact (less then 24h difference).
That is needed because Briar rotates its encryption keys regularly to provide forward secrecy.
**3. Tor can be slow:**
Briar uses Tor to tunnel its traffic through the internet, to anonymize and counter censorship. Sometimes Tor is a bid slow, or has a connection issue. Some patience solves that most of the time. If not, restarting Briar/your phone should do so. Doing so gives you a new route through Tor, that hopefully is more stable then the one you had prior.
**4. Circumvent Tor cencorship:**
Some Internet Service Provider and some countries block Tor. (If the usage of Tor is illegal in your country, make sure to understand the risk of using it.) Briar can help you to circumvent this, by utilizing so called "bridges". A bridge is a entrance node to the Tor network, that in best case is not associated with Tor or known by the Internet Service Provider. They are not fail safe, but they often work to circumvent this censorship. Usually Briar detects such a connection issue by itself, and give you automatically access to a bridge. You can check and change this by: >menu >settings >connections >Connection method for Tor network.https://code.briarproject.org/briar/briar/-/issues/2075Upgrade Tor to 0.3.5.152021-08-27T11:46:44ZakwizgranUpgrade Tor to 0.3.5.15https://gitweb.torproject.org/tor.git/tree/ChangeLog?h=tor-0.3.5.15https://gitweb.torproject.org/tor.git/tree/ChangeLog?h=tor-0.3.5.15Android 1.3akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/2074contackt working but there is no green2021-06-15T17:52:53ZWuukocontackt working but there is no greenunable to make new contacts even rhough both persons are online at thr same timeunable to make new contacts even rhough both persons are online at thr same timehttps://code.briarproject.org/briar/briar/-/issues/2073Improve usability of error reporting2021-06-11T12:00:46ZSebastianImprove usability of error reportingWhen an error occurs and the form for reporting errors is shown to the user, it can now happen that the hint "Enter your feedback" on the input field won't be seen by the user as it may already pre-populated with the error message that m...When an error occurs and the form for reporting errors is shown to the user, it can now happen that the hint "Enter your feedback" on the input field won't be seen by the user as it may already pre-populated with the error message that made the user open the report form.
It might make sense to change that behavior in a way that the user is still made aware of being able to enter some additional feedback.https://code.briarproject.org/briar/briar/-/issues/2072Grable version 6 error..., The Android plugin interferes with compilation.2021-06-11T09:05:04ZMaxim Kopylovichmaxim380k@mail.ruGrable version 6 error..., The Android plugin interferes with compilation.For several days I tried to install android studio to compile the project.
But constantly faced with an error, the Android studio can not install Grable version 6 ... The
update autoloader constantly wants to download all the latest appl...For several days I tried to install android studio to compile the project.
But constantly faced with an error, the Android studio can not install Grable version 6 ... The
update autoloader constantly wants to download all the latest applicable in the android studio, but the Briar project contains a lot of components and commands that may not be compatible with the compilation changes.
In order to compile the Briar from the project to github, you need to pay more attention to the installation.https://code.briarproject.org/briar/briar/-/issues/2068Unsuccessful connect via BT2021-08-18T15:33:37ZIvanaUnsuccessful connect via BT| Step | Pixel2 | Nokia3.1 |
| ---- | ------ | ------ |
| 1 | Existing contact – added by 'nearby method' ('Andy') | ditto ('Belle')|
| 2 | No messages from this contact yet | No messages from this contact yet |
| 3 | No other contacts y...| Step | Pixel2 | Nokia3.1 |
| ---- | ------ | ------ |
| 1 | Existing contact – added by 'nearby method' ('Andy') | ditto ('Belle')|
| 2 | No messages from this contact yet | No messages from this contact yet |
| 3 | No other contacts yet | No other contacts yet |
| 4 | Initial Briar settings | Initial Briar settings |
| 5 | BT ON | BT ON |
| 6 | Wifi OFF | Wifi OFF |
| 7 | Internet OFF | Internet OFF |
| 8 | Switch BT OFF | keep BT ON |
| 9 | Contacts see each other as offline | Contacts see each other as offline |
| 10 | go to 'Belle' > menu > select 'Connect via BT' | go to 'Andy' > menu > select 'Connect via BT' |
| 11 | Msg:Your contact needs to be nearby...“Start” at the same time | ditto |
| 12 | Press Start | Press Start |
| 13 | Msg:Briar debug ...for 120 seconds | Msg:Briar debug ...for 120 seconds |
| 14 | Allow | Allow |
| 15 | Brief msg 'Connecting via Bluetooth' | Brief msg 'Connecting via Bluetooth' |
| 16 | Brief msg 'Successfully connected via BT' | Brief msg 'Successfully connected via BT' |
| 17 | Contacts see each other as online | Contacts see each other as online |
| 18 | Contacts can send each other messages | Contacts can send each other messages |
| 19 | Repeat steps 4-18 | Repeat steps 4-18 |
| 20 | Repeat steps 4-18 | Repeat steps 4-18 |
| 21 | Repeat steps 4-18 | Repeat steps 4-18 |
Repeating these steps a few times in a row - connecting via BT works OK. But then, I delete contact on one phone, and re-add it via nearby method and things begin to look different. I performed the following steps:
| Step | Pixel2 | Nokia3.1 |
| ---- | ------ | ------ |
| 22 | Delete contact 'Belle' | Keep contact 'Andy' |
| 23 | Re-add contact Belle, using nearby method | re-add contact Andy using nearby method |
| 24 | Contacts is added | Contact is not added as it already exists = OK|
| 25 | Contacts see each other as offline | Contacts see each other as offline|
Is this correct behaviour? That contacts should see each other as offline when re-added successfully via nearby method?
| Step | Pixel2 | Nokia3.1 |
| ---- | ------ | ------ |
| 26 | This process turns the wifi and BT to ON (in Briar app) | ditto |
| 27 | BT = ON, WiFi= ON in Briar app | BT = ON, WiFi= ON in Briar app |
| 28 | Repeat steps 10-15 | Repeat steps 10-15 |
Expeced result: BT connection should be established, contacts shoudl see each other online and be able to send each other messages.
Actual result: Message: successfully connected via BT on both devices,
However, **the contacts see each other as offline, and cannot send messages **
If I try to send a message from one to the other (Nokia to Pixel) message is not delivered to Pixel.
Trying to Reconnect again via BT, as in steps 10-14, there is a brief message at the bottom of the Pixel2 screen 'connecting via BT', and then 'unable to connect via BT', but no equivalent messages at all on Nokia screen - they just don't show.
Contacts still see each other offline and cannot send each other messages.
Android Studio log for PIxel 2 attached - the first file covers all the user actions up to the 'actual results'
[unsuccessful_connect_via_bT_log_08062021.txt](/uploads/6feb65977e516ed2cedc7c913d1450d9/unsuccessful_connect_via_bT_log_08062021.txt)
This file covers only the last attempt to reconnect after the 'actual results'
[Culd_not_connect_via_BT_0862021.txt](/uploads/6bf8b104b6d5d6b888551633853f7fe5/Culd_not_connect_via_BT_0862021.txt)IvanaIvanahttps://code.briarproject.org/briar/briar/-/issues/2067Add version/build info to settings dialog2022-07-11T15:13:46ZNorbert 80Add version/build info to settings dialogI cannot find a version string somewhere in the Briar app. I suggest to add build info at the bottom of the settings screen.I cannot find a version string somewhere in the Briar app. I suggest to add build info at the bottom of the settings screen.Android 1.4https://code.briarproject.org/briar/briar/-/issues/2066Error: NoSuchGroupException2021-06-07T16:08:35ZNorbert 80Error: NoSuchGroupExceptionOn Briar 1.3.4 Android I ALWAYS get an "Error: NoSuchGroupException" when deleting groups.
(Additional info: I just created test groups with no other participants. I don't know at the moment if this error only happens in this particular...On Briar 1.3.4 Android I ALWAYS get an "Error: NoSuchGroupException" when deleting groups.
(Additional info: I just created test groups with no other participants. I don't know at the moment if this error only happens in this particular case.)
Another issue:https://code.briarproject.org/briar/briar/-/issues/2064Image quality is very low when sending and receiving images.2022-07-08T11:19:20ZAman AroraImage quality is very low when sending and receiving images.Trying sending hd images but it's size getting compressed to few kbs only from mbs.
Event not able to read text from images. Please fix thisTrying sending hd images but it's size getting compressed to few kbs only from mbs.
Event not able to read text from images. Please fix thisMulti-block messageshttps://code.briarproject.org/briar/briar/-/issues/2062Show connectivity status in ongoing notification2021-06-02T18:43:53ZakwizgranShow connectivity status in ongoing notificationA user asked for the app's connectivity status to be included in the ongoing notification so it can be checked easily.A user asked for the app's connectivity status to be included in the ongoing notification so it can be checked easily.https://code.briarproject.org/briar/briar/-/issues/2060[delete]2022-02-25T15:01:48ZLucy Lu[delete]https://code.briarproject.org/briar/briar/-/issues/2059NoSuchGroupException toast is shown when private group is removed2021-06-14T14:58:58ZakwizgranNoSuchGroupException toast is shown when private group is removed* Android version: 4.4.2
* Phone model: LGE LG-D150 (w35_global_com)
* Briar version: 1.3.4 (76b7e6f)
* User feedback: "NoSuchGroupException"
Log:
```
05-23 22:32:59.452 I/GroupListViewModel: Private group removed
05-23 22:32:59.453 I/T...* Android version: 4.4.2
* Phone model: LGE LG-D150 (w35_global_com)
* Briar version: 1.3.4 (76b7e6f)
* User feedback: "NoSuchGroupException"
Log:
```
05-23 22:32:59.452 I/GroupListViewModel: Private group removed
05-23 22:32:59.453 I/ThreadListViewModel: Group removed
05-23 22:32:59.456 I/BaseActivity: Pausing GroupActivity
05-23 22:32:59.467 I/BaseActivity: Starting NavDrawerActivity
05-23 22:32:59.467 I/BaseActivity: Resuming NavDrawerActivity
05-23 22:32:59.950 I/BaseActivity: Stopping GroupActivity
05-23 22:32:59.954 I/BaseActivity: Destroying GroupActivity
05-23 22:32:59.967 W/DbViewModel: org.briarproject.bramble.api.db.NoSuchGroupException
org.briarproject.bramble.api.db.NoSuchGroupException
at org.briarproject.bramble.db.DatabaseComponentImpl.mergeGroupMetadata(DatabaseComponentImpl.java:784)
at org.briarproject.bramble.client.ClientHelperImpl.mergeGroupMetadata(ClientHelperImpl.java:224)
at org.briarproject.bramble.client.ClientHelperImpl.lambda$mergeGroupMetadata$7(ClientHelperImpl.java:218)
at org.briarproject.bramble.client.ClientHelperImpl.lambda$mergeGroupMetadata$7$ClientHelperImpl(ClientHelperImpl.java)
at org.briarproject.bramble.client.-$$Lambda$ClientHelperImpl$7us-EF4vPLR_8c0LCNvGmtb6d4I.run(lambda)
at org.briarproject.bramble.db.DatabaseComponentImpl.transaction(DatabaseComponentImpl.java:200)
at org.briarproject.bramble.client.ClientHelperImpl.mergeGroupMetadata(ClientHelperImpl.java:218)
at org.briarproject.briar.client.MessageTrackerImpl.storeMessageId(MessageTrackerImpl.java:92)
at org.briarproject.briar.android.threaded.ThreadListViewModel.lambda$storeMessageId$1(ThreadListViewModel.java:222)
at org.briarproject.briar.android.threaded.ThreadListViewModel.lambda$storeMessageId$1$ThreadListViewModel(ThreadListViewModel.java)
at org.briarproject.briar.android.threaded.-$$Lambda$ThreadListViewModel$8pSkGFRn7z9NtDqesywkHNLVqgk.run(lambda)
at org.briarproject.briar.android.viewmodel.DbViewModel.lambda$runOnDbThread$0(DbViewModel.java:77)
at org.briarproject.briar.android.viewmodel.DbViewModel.lambda$runOnDbThread$0$DbViewModel(DbViewModel.java)
at org.briarproject.briar.android.viewmodel.-$$Lambda$DbViewModel$WFnJ2C0vmjF_vFVS_futFODEXKA.run(lambda)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
```
What seems to be happening is that ThreadListViewModel is asynchronously storing the list position, and it gets a NoSuchGroupException because the group has recently been removed. The exception is harmless and should probably be logged rather than shown in the UI.Android 1.3Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2058Disabled settings are difficult to read2021-06-08T12:56:08ZakwizgranDisabled settings are difficult to read* Briar version: 1.3.4
* User feedback: "The greyed out options in the settings are a bit to difficult to read (for me).
A bit more contrast could still signal it's greyed out, but offer better readability."* Briar version: 1.3.4
* User feedback: "The greyed out options in the settings are a bit to difficult to read (for me).
A bit more contrast could still signal it's greyed out, but offer better readability."