briar issueshttps://code.briarproject.org/briar/briar/-/issues2023-03-15T12:34:51Zhttps://code.briarproject.org/briar/briar/-/issues/2260When a user changes their profile picture, this is reflected in forum message...2023-03-15T12:34:51ZIvanaWhen a user changes their profile picture, this is reflected in forum messages, blog messages and private group messages only after the screen is refreshed**Steps to execute**
A user is member of a private group, has reblogged some blog posts and is a member of a forum.
They have the generic profile picture.
User changes their profile picture.
**Expected results:**
New profile picture...**Steps to execute**
A user is member of a private group, has reblogged some blog posts and is a member of a forum.
They have the generic profile picture.
User changes their profile picture.
**Expected results:**
New profile picture is reflected in forum and private group messages as well as reblogged blog posts immediately.
**Actual results:**
Profile picture is updated only after the screen refresh.
Note: this is a known issue, although I was not able to find an existing ticket, so maybe it is known from attermost discussions? Raisiing this ticket so it doesn't get forgotten, but if duplicated, please close.https://code.briarproject.org/briar/briar/-/issues/2406Error fragment after scanning QR code for adding contacts does not auto-rotat...2022-12-21T12:21:47ZSebastianError fragment after scanning QR code for adding contacts does not auto-rotate to landscape modeAfter trying to add a contact nearby and scanning a random QR code, an error fragment is displayed. Since we're disabling auto-rotation in the scanning fragment and set that on the activity, the following fragment has the same restrictio...After trying to add a contact nearby and scanning a random QR code, an error fragment is displayed. Since we're disabling auto-rotation in the scanning fragment and set that on the activity, the following fragment has the same restriction. We call there:
```
requireActivity().setRequestedOrientation(SCREEN_ORIENTATION_NOSENSOR);
```
and probably could just call this in the error fragment:
```
requireActivity().setRequestedOrientation(SCREEN_ORIENTATION_UNSPECIFIED);
```https://code.briarproject.org/briar/briar/-/issues/2254QR screen hangs if user leave Briar and go to permission manager and denies l...2022-01-19T10:36:04ZIvanaQR screen hangs if user leave Briar and go to permission manager and denies location permission during the creation of nearby contactReproducible on devices: Pixel 2 API 30, Samsung A01 Core API 29, Motorola E2 API 23
It does not happen on HTC One M9 API 24
## Steps to execute
- Verify that Briar debug has location and camera permissions granted in the device setting...Reproducible on devices: Pixel 2 API 30, Samsung A01 Core API 29, Motorola E2 API 23
It does not happen on HTC One M9 API 24
## Steps to execute
- Verify that Briar debug has location and camera permissions granted in the device settings
- Go to 'add nearby contact'
- Follow instructions, and when the QR code is displayed, go to the device settings and deny the locaiton permission to Briar debug
- Return to Briar debug
- re-login when asked
## expected results
- the QR screen that was showing before, displays again
## actual results
- the QR screen hangs. See attached.![device-2022-01-18-141734](/uploads/bbc47c7fbbd01b50beba5f971278fa6c/device-2022-01-18-141734.mp4)[QR_screen_hangs_on_Pixel2.txt](/uploads/48d5e18d8e704108f0fbf9869ce77ad9/QR_screen_hangs_on_Pixel2.txt)https://code.briarproject.org/briar/briar/-/issues/1959When the 'Disappearing messages' setting is changed during the message compos...2021-04-30T13:35:24ZIvanaWhen the 'Disappearing messages' setting is changed during the message composing, no warning message in landscape orientationSteps to reproduce
Start typing a message on device1 in portrait orientation and before sending it, go to the menu in the upper right corner and change the Disappearing messages setting to On.
Continue typing the message and then send...Steps to reproduce
Start typing a message on device1 in portrait orientation and before sending it, go to the menu in the upper right corner and change the Disappearing messages setting to On.
Continue typing the message and then send.
A warning message appears in the portrait orientation, that says: "Disappearing messages changed, since you started composing your message, disappearing messages have been enabled"
Now start typing a message and the change the Disappearing setting before sending the message, turn the phone to landscape and continue typing; Then send the message.
Actual results: The message is sent OK, but the warning message does not show.
Expected results: the warning message shoudl show the same way as it does in portrait orientationhttps://code.briarproject.org/briar/briar/-/issues/1931Add new contact FAB labels not visible in landscape orientation2021-02-11T13:25:47ZIvanaAdd new contact FAB labels not visible in landscape orientationWth your device in landscape orientation
Tap on + to add a contact
The icons for adding contacts at a distance or nearby are visible, but labels are not so user doesn't know what to tap.
The workaround is: use phone in portrait orienta...Wth your device in landscape orientation
Tap on + to add a contact
The icons for adding contacts at a distance or nearby are visible, but labels are not so user doesn't know what to tap.
The workaround is: use phone in portrait orientation, where labels are clearly visible
(Mattermost conversation 11/2/21: perhaps solution is to stack icons vertically?)
Low priority as the contact creation is successful in both landscape and portrait, plus workaround super easy - it's jsut a matter of labels showing/not showing...https://code.briarproject.org/briar/briar/-/issues/267Touching persistent notification doesn't bring app to foreground2020-11-21T19:28:40ZakwizgranTouching persistent notification doesn't bring app to foregroundThe persistent notification says 'Touch to show the dashboard' but touching it has no effect.The persistent notification says 'Touch to show the dashboard' but touching it has no effect.https://code.briarproject.org/briar/briar/-/issues/463Redesign panic button settings2020-11-21T18:47:35ZMegaloxRedesign panic button settingsThe panic button settings could look better, but this is very low priority.The panic button settings could look better, but this is very low priority.https://code.briarproject.org/briar/briar/-/issues/823Combined feed uses a different fragment transition from single blogs2020-11-21T12:43:07ZakwizgranCombined feed uses a different fragment transition from single blogsThe transition from the list of posts to an individual post in the combined feed is different from the corresponding transition in a single blog. In the combined feed, the list disappears and the post slides in from the right. In a singl...The transition from the list of posts to an individual post in the combined feed is different from the corresponding transition in a single blog. In the combined feed, the list disappears and the post slides in from the right. In a single blog, the list fades out and the post fades in and slides in from the right.
This is not an important bug.https://code.briarproject.org/briar/briar/-/issues/1770Delete multiple contacts2020-11-16T10:25:31ZN6P4CFB1BSRSLDelete multiple contacts**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
There is no quick way to select and delete multiple contacts under "Contacts" view. The multiple select function is missing.
Currently each contact must be dele...**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
There is no quick way to select and delete multiple contacts under "Contacts" view. The multiple select function is missing.
Currently each contact must be deleted manually.https://code.briarproject.org/briar/briar/-/issues/1569Connection manager could fail to close connection2020-11-15T18:24:37ZakwizgranConnection manager could fail to close connectionWhen the connection manager disposes of the incoming side of a duplex connection, it interrupts the outgoing sync session (if any) so the outgoing session can finish cleanly. If this happens before the outgoing session is created, it won...When the connection manager disposes of the incoming side of a duplex connection, it interrupts the outgoing sync session (if any) so the outgoing session can finish cleanly. If this happens before the outgoing session is created, it won't be interrupted.
If the incoming side of the connection is being disposed of because of an exception then the transport connection will be closed, so the outgoing session should eventually catch an exception when it tries to write to the connection. But if the incoming side of the connection is being disposed of because the end of the stream was reached then the transport connection will be left half-open, so the outgoing session could keep running indefinitely. This might also happen in the case of an exception if there's nothing to send and the transport doesn't require keepalives, which is the case for Bluetooth.
This could result in a dangling connection that's only usable in one direction. As far as I can tell it won't prevent a new connection from being made, or cause issues like !921, because the registration and unregistration of duplex connections is based on the lifetime of the incoming session, not the outgoing session.
The opposite can also happen: if the connection manager disposes of the outgoing side of the connection before the incoming session is created, the incoming session won't be interrupted. This can only happen if an exception has been thrown (in which case the transport connection will be closed, which *should* cause the incoming session to catch an exception eventually), or if the outgoing session has finished cleanly, which only happens if it's interrupted due to the incoming side of the connection being disposed of. So the only possible cause of a bug like !921 in this case would be if closing the connection didn't cause the incoming session to catch an exception (flaky Bluetooth stacks, I'm looking at you).
Labelling this as a bug because it's unintended behaviour, although it's not clear if we need to fix it.https://code.briarproject.org/briar/briar/-/issues/1645Briar add contacts without QR code scan by camera2020-11-15T17:32:48ZricjdjwoeownsoBriar add contacts without QR code scan by cameraHello,
I don't think it's good if you can only add contacts to a QR code scan by camera. What if the camera is broken? What then? :(
I think it's better if there are more alternatives.
I imagine so.
You can connect the Android device...Hello,
I don't think it's good if you can only add contacts to a QR code scan by camera. What if the camera is broken? What then? :(
I think it's better if there are more alternatives.
I imagine so.
You can connect the Android devices in the wifi network (local android wifi hotspot) together and ask each other for a code, then enter it and you're done. So similar if you connect devices via bluetooth via code.https://code.briarproject.org/briar/briar/-/issues/1769Add non-dynamic time format2020-11-15T14:24:49ZN6P4CFB1BSRSLAdd non-dynamic time format**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
Currently, Briar only displays a dynamic time format when messages are sent and received.
It would be very good if a non-dynamic time format could be added, but...**Version**
Briar 1.2.9
**Android version**
Android 10
**Description**
Currently, Briar only displays a dynamic time format when messages are sent and received.
It would be very good if a non-dynamic time format could be added, but it uses almost the same structure as dynamic time format.
An example would be
MMM dd, yyyy, hh:mm a
Sep 3, 2020, 01:00 PMhttps://code.briarproject.org/briar/briar/-/issues/924Tester thought tap target onboarding was a bug2020-11-15T10:43:00ZakwizgranTester thought tap target onboarding was a bugA tester thought the tap target onboarding for the introduction feature was a bug - she held up her phone and asked "Is it meant to look like that?".
Perhaps we should consider using a less bold design, or changing the parameters so tha...A tester thought the tap target onboarding for the introduction feature was a bug - she held up her phone and asked "Is it meant to look like that?".
Perhaps we should consider using a less bold design, or changing the parameters so that the target appears more gradually.