briar issueshttps://code.briarproject.org/groups/briar/-/issues2021-01-23T13:40:43Zhttps://code.briarproject.org/briar/briar-gtk/-/issues/78Notification counter stays even when msg has been seen2021-01-23T13:40:43ZdanNotification counter stays even when msg has been seenNotification doesnt go away. ![briar.notif](/uploads/565826097a0162211009d7e70c70576f/briar.notif.png)
The only way to make the notification go away, is to send a msg.
flatpak v0.1.0-beta2Notification doesnt go away. ![briar.notif](/uploads/565826097a0162211009d7e70c70576f/briar.notif.png)
The only way to make the notification go away, is to send a msg.
flatpak v0.1.0-beta2GTK Nexthttps://code.briarproject.org/briar/briar/-/issues/1792Stepper isn't read in a meaningful order by screen readers2020-11-15T13:47:05ZakwizgranStepper isn't read in a meaningful order by screen readersThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the "stepper" that shows the steps in the process of adding a contact remotely isn't read in a meaningful order by screen...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the "stepper" that shows the steps in the process of adding a contact remotely isn't read in a meaningful order by screen readers. TalkBack navigation reads the steps "1 - Exchange links, 2 - Choose nickname" as "1, 2, Exchange links, Choose nickname".https://code.briarproject.org/briar/briar/-/issues/1791Non-text content should have a textual alternative2020-11-15T13:48:30ZakwizgranNon-text content should have a textual alternativeThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) found several places in the app where non-text content lacks a textual alternative:
- [ ] Password strength indicator
- [ ] Checkmarks...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) found several places in the app where non-text content lacks a textual alternative:
- [ ] Password strength indicator
- [ ] Checkmarks in the power management setup screen
- [ ] Checkmarks in the stepper when adding a contact remotely
- [ ] Diagram explaining how QR codes should or should not be exchanged
If any of these involve a lot of work we can create subtasks.https://code.briarproject.org/briar/briar/-/issues/1789Changes to status messages aren't visible to screen readers2020-11-15T13:49:20ZakwizgranChanges to status messages aren't visible to screen readersThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that when status messages such as those shown in the pending contact list ("Connecting", etc) are updated, screen readers aren...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that when status messages such as those shown in the pending contact list ("Connecting", etc) are updated, screen readers aren't automatically aware that the text has changed.
One way to make screen readers aware that text has changed is to give focus to the changed element. The "Password is too weak" message on the setup screen is an example of a status message that's correctly handled by screen readers.https://code.briarproject.org/briar/briar/-/issues/1788Text fields should have labels2020-11-15T13:51:14ZakwizgranText fields should have labelsThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the way we style text fields, showing placeholder text but not a label, is an accessibility issue because the placeholder...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the way we style text fields, showing placeholder text but not a label, is an accessibility issue because the placeholder text disappears when the user starts to type, leaving no indication of the field's purpose.
This is my fault - I argued for removing the labels because I think the way they move and change size when the field gains or loses focus interacts badly with automatically giving focus to the first text field.https://code.briarproject.org/briar/briar/-/issues/1787Transport indicators are not accessible to colourblind people2020-11-15T13:51:37ZakwizgranTransport indicators are not accessible to colourblind peopleThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the transport indicators in the nav drawer rely on colour alone to indicate their state. A second visual cue should be pr...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) reported that the transport indicators in the nav drawer rely on colour alone to indicate their state. A second visual cue should be provided for colourblind users.https://code.briarproject.org/briar/briar/-/issues/1786Some buttons lack name/role/value for accessibility2020-11-15T13:52:36ZakwizgranSome buttons lack name/role/value for accessibilityThe [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) found several examples of buttons that weren't marked with an appropriate name, role and value to enable screen readers to handle them ...The [Accessibility Foundation audit](https://briarproject.org/raw/Accessibility_Report_NGI_Briar.pdf) found several examples of buttons that weren't marked with an appropriate name, role and value to enable screen readers to handle them properly:
- [ ] The `(i)` button for showing information lacks a role (should be "button")
- [ ] The `+` button for adding contacts lacks a name
- [ ] The speed dial buttons for adding contacts lack a role for the text and a name for the icon
- [ ] The buttons in the navigation menu lack a role
- [ ] The transport indicators lack a value
- [ ] In the private group list and possibly elsewhere, the action bar's overflow menu button and the menu items lack roles
- [ ] The button for opening/closing the emoji keyboard lacks a name
- [ ] The "Reply" button (in forums and private groups?) lacks a role
- [ ] When the buttons for scrolling up/down to the previous/next unread message are hidden, they're still visible to screen readers but don't work, and don't have a name, role or value
- [ ] The reblog button has the name "Add a comment" rather than "Reblog"
If any of these are tricky to handle we can create subtasks.https://code.briarproject.org/briar/briar/-/issues/1778Onboarding tap target wrongly positioned2021-08-19T11:13:14ZakwizgranOnboarding tap target wrongly positionedThe onboarding tap target for the connections screen is meant to be centered on the Tor icon. On the Samsung Galaxy Ace 2 (Android 4.1.2) it's centered on the top left corner of the nav drawer instead.
I can reproduce this reliably on t...The onboarding tap target for the connections screen is meant to be centered on the Tor icon. On the Samsung Galaxy Ace 2 (Android 4.1.2) it's centered on the top left corner of the nav drawer instead.
I can reproduce this reliably on the device, but it doesn't happen on the emulator running the same API version (16).
![device-2020-09-24-124455](/uploads/4b87fcb4d94c44028ae2fb0cc72dbbb1/device-2020-09-24-124455.png)https://code.briarproject.org/briar/briar/-/issues/1776NPE in exit transition2021-11-04T11:03:23ZakwizgranNPE in exit transition* Android version: 10
* Phone model: Huawei ELE-L29
* Briar version: 1.2.9 (9d96ce6)
Stacktrace:
```
java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.app.Activity.isTopOfTask()' on a null object referenc...* Android version: 10
* Phone model: Huawei ELE-L29
* Briar version: 1.2.9 (9d96ce6)
Stacktrace:
```
java.lang.NullPointerException: Attempt to invoke virtual method 'boolean android.app.Activity.isTopOfTask()' on a null object reference
at android.app.ExitTransitionCoordinator.notifyComplete(ExitTransitionCoordinator.java:437)
at android.app.ExitTransitionCoordinator.onReceiveResult(ExitTransitionCoordinator.java:91)
at android.os.ResultReceiver$MyRunnable.run(ResultReceiver.java:50)
at android.os.Handler.handleCallback(Handler.java:900)
at android.os.Handler.dispatchMessage(Handler.java:103)
at android.os.Looper.loop(Looper.java:219)
at android.app.ActivityThread.main(ActivityThread.java:8347)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:513)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1055)
```Android 1.4https://code.briarproject.org/briar/briar/-/issues/1768Declined introduction cannot be sent again immediately2020-11-15T14:26:46ZN6P4CFB1BSRSLDeclined introduction cannot be sent again immediately**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
If an introduction is accidentally declined there is no quick and easy way to undo it and accept a resend of the introduction.
Generally whether accidentally de...**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
If an introduction is accidentally declined there is no quick and easy way to undo it and accept a resend of the introduction.
Generally whether accidentally declined or really declined. The messages generated by this introduction function cannot be deleted immediately and the user does not know when it is possible to make introduction again for the same contact.https://code.briarproject.org/briar/briar/-/issues/1765Does not reconnect despite existing Wi-Fi Direct connection2020-11-15T14:30:47ZN6P4CFB1BSRSLDoes not reconnect despite existing Wi-Fi Direct connection**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
1. Connect two Android 10 devices (smartphones) via Wi-Fi Direct
2. Install the Briar app on both Android devices
3. Open the Briar app and add the Android device...**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
1. Connect two Android 10 devices (smartphones) via Wi-Fi Direct
2. Install the Briar app on both Android devices
3. Open the Briar app and add the Android devices to contacts
4. Now can send and receive messages. A green icon will light up.
5. On the first Android device in Briar app tap "Sign out" and open Briar app again and enter the password.
6. Now there is no more green icon on both Android devices and can no longer send and receive messages.
Note:
The Wi-Fi Direct connection was not disconnected. Same problem also with Bluetooth.
Can you reproduce it?https://code.briarproject.org/briar/briar/-/issues/1752After internal emulated sdcard's zero bytes disk space free condition, the da...2020-11-16T10:46:50ZmathAfter internal emulated sdcard's zero bytes disk space free condition, the database became corrupted and all Briar data was losthttps://code.briarproject.org/briar/briar/-/issues/1749Blog post dividers are hard to see2020-11-15T15:32:03ZakwizgranBlog post dividers are hard to seeA user reported that the dividers between sections of a reblogged/commented post are hard to see (there isn't enough contrast between the grey divider and the white background).A user reported that the dividers between sections of a reblogged/commented post are hard to see (there isn't enough contrast between the grey divider and the white background).https://code.briarproject.org/briar/briar/-/issues/1738Bluetooth stops working on Nokia 3.1 after a few hours2020-11-15T15:48:09ZakwizgranBluetooth stops working on Nokia 3.1 after a few hoursI've been testing some Bluetooth changes on a few devices, which involve turning off wifi and mobile data, connecting the devices via Bluetooth, leaving them running overnight, and seeing which devices are still connected, or able to rec...I've been testing some Bluetooth changes on a few devices, which involve turning off wifi and mobile data, connecting the devices via Bluetooth, leaving them running overnight, and seeing which devices are still connected, or able to reconnect, the next morning.
On several occasions the Nokia 3.1 has lost all its connections and is unable to reconnect until Bluetooth is turned off and on again, at which point it quickly reconnects to the other devices. I need to narrow down the conditions under which this happens (number of other devices, amount of time, etc) to find a workaround.https://code.briarproject.org/briar/briar/-/issues/1737Huawei P8 Lite 2017 enters device idle mode despite doze whitelisting2021-04-30T13:38:14ZakwizgranHuawei P8 Lite 2017 enters device idle mode despite doze whitelistingAfter setting up Briar as normal on the Huawei P8 Lite 2017 (Android 7.0, EMUI 5.0.1) and leaving it running for a few hours, the doze watchdog dialog was shown after unlocking the screen, indicating that the phone entered device idle mo...After setting up Briar as normal on the Huawei P8 Lite 2017 (Android 7.0, EMUI 5.0.1) and leaving it running for a few hours, the doze watchdog dialog was shown after unlocking the screen, indicating that the phone entered device idle mode despite Briar being whitelisted.
![Screenshot_20200602-214120](/uploads/8771b9bbe470ab02575ddfe0221a9656/Screenshot_20200602-214120.png)
![Screenshot_20200602-214132](/uploads/d21e2d865b68342b1a9ae4f5f9319be9/Screenshot_20200602-214132.png)
Wifi and mobile data were turned off, so there was no Tor wake lock keeping the device awake.
After tapping "fix", which prompts to add Briar to the whitelist again, I left the phone idle for more than 24 hours and didn't see the doze watchdog dialog again.
I didn't capture any logs at the time as I was running another experiment. I'll try to reproduce this when the other experiments are finished.https://code.briarproject.org/briar/briar/-/issues/1731Asynchronous sync not working2020-11-15T15:54:41ZliofmrAsynchronous sync not workingHi, I tried to test the behavior like described on this image of the official briar website :
![briar_diagram](/uploads/c88b9052c156e2043707b7e892de367e/briar_diagram.png)
But it's not working. I mean, I created a little network with 3...Hi, I tried to test the behavior like described on this image of the official briar website :
![briar_diagram](/uploads/c88b9052c156e2043707b7e892de367e/briar_diagram.png)
But it's not working. I mean, I created a little network with 3 phones not exactly like the picture but I simplified it. I will work with A, B and C phones (not the same as the picture, forgot this config). When the 3 A, B and C phones are connected to the network (wifi, bluetooth or internet 3G), it's working, everybody recieve all blog posts.
BUT, if C disconnect, and A create a blog post, then first, B will recieve it.
THEN, if I disconnect A, and connect C, the blog post is not transmitted.
The purpose is to see if B can act as a the C phone on the official picture I shared. May be I did something wrong. Please do you have an idea ? Is it a bug or non-implemented yet feature or a bug ?
Thank you for this app, if it could work like in the picture it would be the best human made app of the century !!https://code.briarproject.org/briar/briar/-/issues/1726Unable to "mark" text in private messages2020-11-15T15:56:26ZbafoobarUnable to "mark" text in private messagesI want to copy text from messages. I can long-tap on text on blogs, group and forum messages, but I am unable to do that on private messages. It only marks the message as a whole to delete it. In combination with beeing unable to click o...I want to copy text from messages. I can long-tap on text on blogs, group and forum messages, but I am unable to do that on private messages. It only marks the message as a whole to delete it. In combination with beeing unable to click on links, that makes it a very annoying issue.https://code.briarproject.org/briar/briar-gtk/-/issues/48Reliably scroll down for new messages2021-01-23T13:40:26ZNicoReliably scroll down for new messagesAs of now, every time a new message arrives in a private chat the list should scroll down. This doesn't work reliably because the message needs to be rendered before adjustment has effects; the used `idle_add()` does not always work to w...As of now, every time a new message arrives in a private chat the list should scroll down. This doesn't work reliably because the message needs to be rendered before adjustment has effects; the used `idle_add()` does not always work to wait for the rendering.
This may become unnecessary with #40.GTK Nexthttps://code.briarproject.org/briar/briar-gtk/-/issues/47Only reload contact list on changes2021-01-23T13:49:22ZNicoOnly reload contact list on changesCurrently, it's reloaded every time a message arrived, which produces a flickering list because for a tiny amount of time the selected contact gets unselected.Currently, it's reloaded every time a message arrived, which produces a flickering list because for a tiny amount of time the selected contact gets unselected.https://code.briarproject.org/briar/briar/-/issues/1710Wrong camera used for adding contacts on Iconia tablet2020-11-15T16:33:49ZakwizgranWrong camera used for adding contacts on Iconia tablet* Android version: 6.0.1
* Phone model: Android-x86 ICONIA W700P (cm_android_x86_64)
* Briar version: 1.1.6 (4d26628)
* User feedback: "Front camera reversed on any app. Please add option to switch camera. I'm unable to add contacts on t...* Android version: 6.0.1
* Phone model: Android-x86 ICONIA W700P (cm_android_x86_64)
* Briar version: 1.1.6 (4d26628)
* User feedback: "Front camera reversed on any app. Please add option to switch camera. I'm unable to add contacts on this device."
Edited log:
```
10-14 21:44:21.325 I/CameraView: Opening camera
10-14 21:44:21.325 I/CameraView: Using back-facing camera
10-14 21:44:21.339 I/CameraView: Screen rotation 0 degrees, camera orientation 0 degrees
10-14 21:44:21.339 I/CameraView: Scene modes: [auto]
10-14 21:44:21.339 I/CameraView: Focus modes: [fixed]
10-14 21:44:21.339 I/CameraView: Video stabilisation enabled: false
10-14 21:44:21.339 I/CameraView: Scene mode: auto
10-14 21:44:21.339 I/CameraView: Focus mode: fixed
10-14 21:44:21.339 I/CameraView: Flash mode: off
10-14 21:44:21.339 I/CameraView: Preview size: 1280x720
...
10-14 21:44:21.379 I/CameraView: Surface created
10-14 21:44:21.379 I/CameraView: Surface changed: 1920x944
10-14 21:44:21.379 I/CameraView: Size 160x120, stretch 1.5254238, zoom 26.041666, score 0.025173334
10-14 21:44:21.379 I/CameraView: Size 176x144, stretch 1.6640986, zoom 19.728535, score 0.030459736
10-14 21:44:21.379 I/CameraView: Size 240x160, stretch 1.3559322, zoom 13.020833, score 0.056640003
10-14 21:44:21.379 I/CameraView: Size 320x200, stretch 1.2711865, zoom 7.8125, score 0.10069333
10-14 21:44:21.379 I/CameraView: Size 320x240, stretch 1.5254238, zoom 6.5104165, score 0.10069334
10-14 21:44:21.379 I/CameraView: Size 352x288, stretch 1.6640986, zoom 4.9321337, score 0.12183894
10-14 21:44:21.379 I/CameraView: Size 432x320, stretch 1.5065913, zoom 3.616898, score 0.18351361
10-14 21:44:21.379 I/CameraView: Size 480x320, stretch 1.3559322, zoom 3.2552083, score 0.22656001
10-14 21:44:21.379 I/CameraView: Size 640x480, stretch 1.5254238, zoom 1.6276041, score 0.40277335
10-14 21:44:21.379 I/CameraView: Size 1280x720, stretch 1.1440678, zoom 1.8432, score 0.47421557
10-14 21:44:21.379 I/CameraView: Best size 1280x720
10-14 21:44:21.380 I/CameraView: Video stabilisation enabled: false
10-14 21:44:21.380 I/CameraView: Scene mode: auto
10-14 21:44:21.380 I/CameraView: Focus mode: fixed
10-14 21:44:21.380 I/CameraView: Flash mode: off
10-14 21:44:21.380 I/CameraView: Preview size: 1280x720
10-14 21:44:21.380 I/CameraView: Starting preview
```