briar issueshttps://code.briarproject.org/briar/briar/-/issues2018-01-28T11:30:28Zhttps://code.briarproject.org/briar/briar/-/issues/342Organise strings.xml to make life easier for translators2018-01-28T11:30:28ZakwizgranOrganise strings.xml to make life easier for translatorsGroup the strings according to where they appear in the app so that translators can see the context in which each string is used. We'll also need a section for strings that appear in multiple places, such as dialog button labels.
Subt...Group the strings according to where they appear in the app so that translators can see the context in which each string is used. We'll also need a section for strings that appear in multiple places, such as dialog button labels.
Subtask of #341.Milestone DTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/343Explain why password is too weak2018-06-11T10:15:17ZakwizgranExplain why password is too weakTesters wanted to know the minimum requirements for passwords. If the user's password is too weak, explain why.
We could solve this by showing "password is too short" if it's below a minimum length, "password is too common" if it's on...Testers wanted to know the minimum requirements for passwords. If the user's password is too weak, explain why.
We could solve this by showing "password is too short" if it's below a minimum length, "password is too common" if it's on a blacklist of common passwords, or "password is too simple" if it's neither too short nor too common but the strength estimate is low due to insufficient variety of characters.https://code.briarproject.org/briar/briar/-/issues/344Tester could not find contact screen2018-06-12T11:32:29ZakwizgranTester could not find contact screenA tester could not find the contact screen when he was already there. The contact list was empty, but the "No contacts" empty state message should have been visible, and the window title should have been "Contacts". I'm not sure what we ...A tester could not find the contact screen when he was already there. The contact list was empty, but the "No contacts" empty state message should have been visible, and the window title should have been "Contacts". I'm not sure what we can do to make this clearer.
Related to #327.Milestone Dhttps://code.briarproject.org/briar/briar/-/issues/345Identity selector when adding contacts is confusing2018-06-12T11:32:29ZakwizgranIdentity selector when adding contacts is confusingTesters found the identity selector confusing when adding contacts.Testers found the identity selector confusing when adding contacts.Milestone DTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/346Some cameras can't focus on QR codes2023-06-08T12:13:45ZakwizgranSome cameras can't focus on QR codesSome testers found that their cameras couldn't focus on QR codes. This has also been an issue on some test devices:
* Sony Xperia Tipo
* Huawei Ascend Y520
* Huawei Ascend Y330
All of these devices have fixed-focus cameras. The s...Some testers found that their cameras couldn't focus on QR codes. This has also been an issue on some test devices:
* Sony Xperia Tipo
* Huawei Ascend Y520
* Huawei Ascend Y330
All of these devices have fixed-focus cameras. The size and resolution of the screen being scanned, and the resolution of the camera's preview image, may also be relevant. Scanning a small, low-resolution screen using a low-resolution, fixed-focus camera seems to be the hardest case (e.g. scanning the HTC Wildfire S using the Sony Xperia Tipo).
@ernir reported that the testers' devices were able to scan QR codes when using the zxing app - we should investigate what it's doing differently.Android Beta 2https://code.briarproject.org/briar/briar/-/issues/347Show progress indicator while loading QR code2018-06-12T11:32:29ZakwizgranShow progress indicator while loading QR codehttps://code.briarproject.org/briar/briar/-/issues/348Testers did not understand QR code workflow2022-11-18T17:24:07ZakwizgranTesters did not understand QR code workflowThree testers tried to scan each other's QR codes: A scanned B, B scanned C, and C scanned A. The testers were not able to complete the task.
In an earlier round of testing we encountered a similar problem with invitation codes.
The f...Three testers tried to scan each other's QR codes: A scanned B, B scanned C, and C scanned A. The testers were not able to complete the task.
In an earlier round of testing we encountered a similar problem with invitation codes.
The first step we should take is to detect that the device we've connected to isn't the same device we scanned, and show a helpful error message. But we may need to consider a more fundamental change: is it possible to design the key agreement protocol to accommodate what the users are trying to achieve?https://code.briarproject.org/briar/briar/-/issues/349Explain Panic Button settings better2020-11-21T19:04:18ZakwizgranExplain Panic Button settings betterSome users discovered the Panic Button settings and were confused by them.Some users discovered the Panic Button settings and were confused by them.https://code.briarproject.org/briar/briar/-/issues/350Contact list still showed unread message after message had been read2018-06-12T11:32:29ZakwizgranContact list still showed unread message after message had been readA tester got an unread message notification, switched directly to the converstion, read the message, switched to the contact screen, and there was still an unread message indicator next to the contact's name.
This may be a race condit...A tester got an unread message notification, switched directly to the converstion, read the message, switched to the contact screen, and there was still an unread message indicator next to the contact's name.
This may be a race condition between messages being marked as read and the contact list loading the message headers.Milestone ETorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/351Overlapping speech bubbles in conversation screen2020-11-21T19:03:30ZakwizgranOverlapping speech bubbles in conversation screenTesters occasionally saw overlapping speech bubbles in the conversation screen.Testers occasionally saw overlapping speech bubbles in the conversation screen.https://code.briarproject.org/briar/briar/-/issues/352Conversation screen has too much padding2018-06-12T11:32:29ZakwizgranConversation screen has too much paddingTesters reported that the speech bubbles in the conversation screen have too much padding, not enough of the conversation is visible.Testers reported that the speech bubbles in the conversation screen have too much padding, not enough of the conversation is visible.Milestone Dhttps://code.briarproject.org/briar/briar/-/issues/353Tester expected enter button to send private message2018-06-12T11:32:28ZakwizgranTester expected enter button to send private messageA tester tried to send a private message via the enter button and wondered why it didn't send. The message was no longer visible because the text entry was limited to a single line and pressing enter had created a new line.
Investigat...A tester tried to send a private message via the enter button and wondered why it didn't send. The message was no longer visible because the text entry was limited to a single line and pressing enter had created a new line.
Investigate how other messaging apps handle this. Does enter send the message, or do they start a new line and expand the text entry?https://code.briarproject.org/briar/briar/-/issues/354Layout improvements for private message composition2018-06-12T11:32:28ZakwizgranLayout improvements for private message compositionThe testing report says that the send icon is too big and the text has too little padding.The testing report says that the send icon is too big and the text has too little padding.Milestone Dhttps://code.briarproject.org/briar/briar/-/issues/355Keyboard closes when private message is sent2018-06-12T11:32:28ZakwizgranKeyboard closes when private message is sentA tester complained that he had to open the keyboard again for each new message.A tester complained that he had to open the keyboard again for each new message.Milestone Cakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/356Make it clearer who will be introduced2018-06-12T11:32:28ZakwizgranMake it clearer who will be introducedA tester asked for the ability to cancel an introduction if he had chosen the wrong contacts.A tester asked for the ability to cancel an introduction if he had chosen the wrong contacts.Milestone DTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/357Introduction feature is not very visible2018-06-12T11:32:28ZakwizgranIntroduction feature is not very visibleTesters could not easily discover the introduction feature.Testers could not easily discover the introduction feature.Milestone ETorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/358Testers did not understand introductions2018-06-12T11:32:28ZakwizgranTesters did not understand introductionsThe testing report says that the feature could be explained better.The testing report says that the feature could be explained better.Milestone Ehttps://code.briarproject.org/briar/briar/-/issues/359Introduction message can be overlooked2018-06-12T11:32:28ZakwizgranIntroduction message can be overlookedTesters tended to overlook the introduction message from the introducer, which was displayed at the same time as the system message notifying them of the introduction. A possible solution would be to combine the messages.Testers tended to overlook the introduction message from the introducer, which was displayed at the same time as the system message notifying them of the introduction. A possible solution would be to combine the messages.Milestone Bhttps://code.briarproject.org/briar/briar/-/issues/360Feedback for introducer when introduction request is sent2018-06-12T11:32:28ZakwizgranFeedback for introducer when introduction request is sentA tester tried to repeat the introduction because he didn't get immediate feedback. We already show the introduction request as an outgoing system message in the conversation, but perhaps we can make the feedback clearer.A tester tried to repeat the introduction because he didn't get immediate feedback. We already show the introduction request as an outgoing system message in the conversation, but perhaps we can make the feedback clearer.Milestone DTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/361Testers could not connect to their contacts2019-02-25T09:56:36ZakwizgranTesters could not connect to their contactsDuring a multi-day test, testers were sometimes unable to connect to their contacts and messages were delayed for days. This happened whether they were connected to wifi or mobile data.During a multi-day test, testers were sometimes unable to connect to their contacts and messages were delayed for days. This happened whether they were connected to wifi or mobile data.