briar issueshttps://code.briarproject.org/groups/briar/-/issues2023-04-28T17:31:20Zhttps://code.briarproject.org/briar/briar/-/issues/2430Icons are missing from our F-Droid repo2023-04-28T17:31:20ZakwizgranIcons are missing from our F-Droid repoOur F-Droid repo doesn't appear to have up-to-date icons for Briar or Mailbox. The newest icons for Briar are for the long-obsolete 1.1.6 release.Our F-Droid repo doesn't appear to have up-to-date icons for Briar or Mailbox. The newest icons for Briar are for the long-obsolete 1.1.6 release.https://code.briarproject.org/briar/briar/-/issues/2428AssertionError when loading image preview2023-04-18T14:43:25ZakwizgranAssertionError when loading image preview* Android version: 10
* Phone model: Samsung SM-A115U (a11qsq)
* Briar version: 1.4.22 (f02bbeb)
* User feedback: "Crash when sending image."
Stacktrace:
```
java.lang.AssertionError
at org.briarproject.briar.android.view.ImageP...* Android version: 10
* Phone model: Samsung SM-A115U (a11qsq)
* Briar version: 1.4.22 (f02bbeb)
* User feedback: "Crash when sending image."
Stacktrace:
```
java.lang.AssertionError
at org.briarproject.briar.android.view.ImagePreviewAdapter.loadItemPreview(ImagePreviewAdapter.java:57)
at org.briarproject.briar.android.view.ImagePreview.loadPreviewImage(ImagePreview.java:80)
at org.briarproject.briar.android.view.TextAttachmentController.onNewAttachmentItemResults(TextAttachmentController.java:206)
at org.briarproject.briar.android.view.TextAttachmentController.access$000(TextAttachmentController.java:44)
at org.briarproject.briar.android.view.TextAttachmentController$1.onChanged(TextAttachmentController.java:187)
at org.briarproject.briar.android.view.TextAttachmentController$1.onChanged(TextAttachmentController.java:179)
at androidx.lifecycle.LiveData.considerNotify(LiveData.java:133)
at androidx.lifecycle.LiveData.dispatchingValue(LiveData.java:151)
at androidx.lifecycle.LiveData.setValue(LiveData.java:309)
at androidx.lifecycle.MutableLiveData.setValue(MutableLiveData.java:50)
at androidx.lifecycle.LiveData$1.run(LiveData.java:93)
at android.os.Handler.handleCallback(Handler.java:883)
at android.os.Handler.dispatchMessage(Handler.java:100)
at android.os.Looper.loop(Looper.java:237)
at android.app.ActivityThread.main(ActivityThread.java:8107)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:496)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1100)
```
Edited log:
```
03-18 20:52:32.715 I/BaseActivity: Starting ConversationActivity
03-18 20:52:32.720 I/BaseActivity: Resuming ConversationActivity
03-18 20:52:33.024 I/ImageCompressorImpl: Original image size: 682x1024
03-18 20:52:33.024 I/ImageCompressorImpl: Scaling attachment by factor of 2
03-18 20:52:33.098 I/ImageCompressorImpl: Compressed image to 30054 bytes, quality 70
03-18 20:52:33.903 I/BaseActivity: Pausing ConversationActivity
03-18 20:52:33.924 I/BaseActivity: Starting NavDrawerActivity
03-18 20:52:33.925 I/BaseActivity: Resuming NavDrawerActivity
03-18 20:52:34.396 I/BaseActivity: Stopping ConversationActivity
03-18 20:52:34.397 I/BaseActivity: Destroying ConversationActivity
03-18 20:52:35.287 I/BaseActivity: Pausing NavDrawerActivity
03-18 20:52:35.310 I/BaseActivity: Creating ConversationActivity
03-18 20:52:35.333 I/ConversationViewModel: PrivateMessageFormat loaded: TEXT_IMAGES_AUTO_DELETE
03-18 20:52:35.382 I/BaseActivity: Starting ConversationActivity
03-18 20:52:35.384 I/BaseActivity: Resuming ConversationActivity
03-18 20:52:35.886 I/BaseActivity: Stopping NavDrawerActivity
03-18 20:52:36.322 I/ConversationActivity: Eagerly loading text for latest message
03-18 20:52:36.794 I/BaseActivity: Pausing ConversationActivity
03-18 20:52:37.403 I/BaseActivity: Stopping ConversationActivity
03-18 20:52:41.046 I/BaseActivity: Starting ConversationActivity
03-18 20:52:41.048 I/BaseActivity: Resuming ConversationActivity
03-18 20:52:41.076 I/ImageCompressorImpl: Original image size: 720x1560
03-18 20:52:41.077 I/ImageCompressorImpl: Scaling attachment by factor of 2
03-18 20:52:41.177 I/ImageCompressorImpl: Compressed image to 29301 bytes, quality 70
```Android 1.4https://code.briarproject.org/briar/briar/-/issues/2426IllegalArgumentException when receiving ACTIVATE message as introducee2023-03-31T15:22:30ZakwizgranIllegalArgumentException when receiving ACTIVATE message as introduceeStacktrace:
```
java.lang.IllegalArgumentException
at org.briarproject.bramble.transport.TransportKeyManagerImpl.activateKeys(TransportKeyManagerImpl.java:285)
at org.briarproject.bramble.transport.KeyManagerImpl.lambda$activateKeys$2(...Stacktrace:
```
java.lang.IllegalArgumentException
at org.briarproject.bramble.transport.TransportKeyManagerImpl.activateKeys(TransportKeyManagerImpl.java:285)
at org.briarproject.bramble.transport.KeyManagerImpl.lambda$activateKeys$2(KeyManagerImpl.java:176)
at org.briarproject.bramble.transport.KeyManagerImpl.$r8$lambda$hZAivP_ym8Z94pCCnZpsDSza1P4(Unknown Source:0)
at org.briarproject.bramble.transport.KeyManagerImpl$$ExternalSyntheticLambda8.run(Unknown Source:4)
at org.briarproject.bramble.transport.KeyManagerImpl.withManager(KeyManagerImpl.java:268)
at org.briarproject.bramble.transport.KeyManagerImpl.activateKeys(KeyManagerImpl.java:175)
at org.briarproject.briar.introduction.IntroduceeProtocolEngine.onRemoteActivate(IntroduceeProtocolEngine.java:511)
at org.briarproject.briar.introduction.IntroduceeProtocolEngine.onActivateMessage(IntroduceeProtocolEngine.java:234)
at org.briarproject.briar.introduction.IntroduceeProtocolEngine.onActivateMessage(IntroduceeProtocolEngine.java:63)
at org.briarproject.briar.introduction.IntroductionManagerImpl.handleMessage(IntroductionManagerImpl.java:253)
at org.briarproject.briar.introduction.IntroductionManagerImpl.incomingMessage(IntroductionManagerImpl.java:211)
at org.briarproject.bramble.api.client.BdfIncomingMessageHook.incomingMessage(BdfIncomingMessageHook.java:63)
at org.briarproject.bramble.sync.validation.ValidationManagerImpl.deliverMessage(ValidationManagerImpl.java:333)
at org.briarproject.bramble.sync.validation.ValidationManagerImpl.lambda$storeMessageContext$6(ValidationManagerImpl.java:290)
at org.briarproject.bramble.sync.validation.ValidationManagerImpl.$r8$lambda$kV95asJ25004Lz0CviD-sa65BcQ(Unknown Source:0)
at org.briarproject.bramble.sync.validation.ValidationManagerImpl$$ExternalSyntheticLambda18.run(Unknown Source:19)
at org.briarproject.bramble.db.DatabaseComponentImpl.transaction(DatabaseComponentImpl.java:200)
at org.briarproject.bramble.sync.validation.ValidationManagerImpl.storeMessageContext(ValidationManagerImpl.java:266)
at org.briarproject.bramble.sync.validation.ValidationManagerImpl.lambda$storeMessageContextAsync$5(ValidationManagerImpl.java:255)
at org.briarproject.bramble.sync.validation.ValidationManagerImpl.$r8$lambda$tOT1oX1UbzoJ5r_HnnaJxOWFjgE(Unknown Source:0)
at org.briarproject.bramble.sync.validation.ValidationManagerImpl$$ExternalSyntheticLambda8.run(Unknown Source:10)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:764)
```
The user reported that they were introduced to the contact in question, but couldn't send messages to them. They then readded the contact by exchanging links.
Possibly related to #2085?Android 1.4https://code.briarproject.org/briar/briar/-/issues/2425List of RSS feeds doesn't update when feed is removed2023-03-27T11:11:22ZakwizgranList of RSS feeds doesn't update when feed is removedThe list of RSS feeds doesn't update when the feed is removed by unsubscribing via the feed's overflow menu, rather than using the delete button in the list of RSS feeds.
Steps to reproduce:
* Add an RSS feed
* Tap the entry in the list...The list of RSS feeds doesn't update when the feed is removed by unsubscribing via the feed's overflow menu, rather than using the delete button in the list of RSS feeds.
Steps to reproduce:
* Add an RSS feed
* Tap the entry in the list of RSS feeds to open the feed
* Unsubscribe via the overflow menu ("Remove blog")
* Expected: The list of RSS feeds is shown, it's now empty
* Actual: The list of RSS feeds is show, it still contains the removed feed. Tapping the feed again causes a NoSuchGroupException (error toast, no crash)https://code.briarproject.org/briar/briar/-/issues/2423Adding contact at a distance - Tapping the 'Add contact' button before the ni...2023-03-16T16:09:15ZIvanaAdding contact at a distance - Tapping the 'Add contact' button before the nickname is typed in, leaves the screen 'in progress'...**Steps to reproduce:**
- tap the 'add contact at a distance' button
- past the contact's link into the appropriate field and tap Continue
- On the screen that follows, user needs to type in the nickname for their contact.
- Once the k...**Steps to reproduce:**
- tap the 'add contact at a distance' button
- past the contact's link into the appropriate field and tap Continue
- On the screen that follows, user needs to type in the nickname for their contact.
- Once the keyboard opens, the button Add contact and the line where the nickname needs to be typed in are quite close on the screen
![Screenshot_20230316_154402](/uploads/c72e004ce6af6af07b20d356e7f64d1f/Screenshot_20230316_154402.png)
- This means that it could happen that the user accidentally taps on the Add contact button before they type in the nickname
- if that happens, then the user sees this
![Screenshot_20230316_154221](/uploads/3d580b498a2a2a337e8fa89d9c3c818d/Screenshot_20230316_154221.png)
- the user is still able to type the nicknam in, but tapping the enter button on the keyboard doesn't do anything other than closing the keyboard.
- once the keyboard is closed, then the user sees this
![Screenshot_20230316_155028](/uploads/cee861c9ecd822405197fcc626fc769f/Screenshot_20230316_155028.png)
The screen keeps showing the small 'inprogress' circle...
it happens inMaster and in the MR 1770 ( build hash 1627f4f )
Tested onHTC Android 7, Nokia Android 10
Workaround is to navigate one screen back and tap on Continue button again...https://code.briarproject.org/briar/briar/-/issues/2422OutOfMemoryError: Could not allocate JNI Env2024-03-18T18:05:12ZakwizgranOutOfMemoryError: Could not allocate JNI Env* Android version: 7.1.2
* Phone model: UHANS A6
* Briar version: 1.4.22 (f02bbeb)
Stacktrace:
```
java.lang.OutOfMemoryError: Could not allocate JNI Env
at java.lang.Thread.nativeCreate(Native Method)
at java.lang.Threa...* Android version: 7.1.2
* Phone model: UHANS A6
* Briar version: 1.4.22 (f02bbeb)
Stacktrace:
```
java.lang.OutOfMemoryError: Could not allocate JNI Env
at java.lang.Thread.nativeCreate(Native Method)
at java.lang.Thread.start(Thread.java:730)
at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:941)
at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1359)
at org.briarproject.bramble.system.AndroidWakeLockManagerImpl.executeWakefully(AndroidWakeLockManagerImpl.java:71)
at org.briarproject.bramble.system.AndroidWakefulIoExecutorModule.lambda$provideWakefulIoExecutor$0(AndroidWakefulIoExecutorModule.java:20)
at org.briarproject.bramble.system.AndroidWakefulIoExecutorModule.$r8$lambda$tnFm9U65p91JUPzzmM4twddDl7M(AndroidWakefulIoExecutorModule.java)
at org.briarproject.bramble.system.AndroidWakefulIoExecutorModule$$ExternalSyntheticLambda0.execute(R8$$SyntheticClass)
at org.briarproject.bramble.plugin.tor.TorPlugin.connect(TorPlugin.java:638)
at org.briarproject.bramble.plugin.tor.TorPlugin.poll(TorPlugin.java:633)
at org.briarproject.bramble.plugin.PollerImpl.poll(PollerImpl.java:231)
at org.briarproject.bramble.plugin.PollerImpl.access$1000(PollerImpl.java:57)
at org.briarproject.bramble.plugin.PollerImpl$PollTask.run(PollerImpl.java:277)
at org.briarproject.bramble.system.AndroidWakeLockManagerImpl.lambda$executeWakefully$0(AndroidWakeLockManagerImpl.java:73)
at org.briarproject.bramble.system.AndroidWakeLockManagerImpl.$r8$lambda$P0v7ccI1GqbvGyqUJX4idUffuJI(AndroidWakeLockManagerImpl.java)
at org.briarproject.bramble.system.AndroidWakeLockManagerImpl$$ExternalSyntheticLambda1.run(R8$$SyntheticClass)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
```
Last lines of log:
```
03-13 04:15:57.257 I/PollerImpl: Polling plugin org.briarproject.bramble.tor
03-13 04:15:57.394 I/ConnectionRegistryImpl: 5 contacts connected or better: org.briarproject.bramble.tor
03-13 04:15:57.395 I/TorPlugin: Connecting to v3 tj2[scrubbed]
03-13 04:15:57.395 I/TorPlugin: Connecting to v3 nix[scrubbed]
03-13 04:15:57.396 I/TorPlugin: Connecting to v3 ela[scrubbed]
03-13 04:15:57.396 I/TorPlugin: Connecting to v3 jvx[scrubbed]
03-13 04:15:57.396 I/TorPlugin: Connecting to v3 72z[scrubbed]
03-13 04:15:57.397 I/TorPlugin: Connecting to v3 msd[scrubbed]
03-13 04:15:57.395 I/TorPlugin: Connecting to v3 37p[scrubbed]
03-13 04:15:57.397 I/TorPlugin: Connecting to v3 lp6[scrubbed]
03-13 04:15:57.400 I/TorPlugin: Connecting to v3 uqp[scrubbed]
03-13 04:15:57.400 I/TorPlugin: Connecting to v3 jqf[scrubbed]
03-13 04:15:57.400 I/TorPlugin: Connecting to v3 ihj[scrubbed]
03-13 04:15:57.401 I/TorPlugin: Connecting to v3 vux[scrubbed]
03-13 04:15:57.401 I/TorPlugin: Connecting to v3 ick[scrubbed]
03-13 04:15:57.402 I/TorPlugin: Connecting to v3 e2v[scrubbed]
03-13 04:15:57.402 I/TorPlugin: Connecting to v3 beq[scrubbed]
03-13 04:15:57.402 I/TorPlugin: Connecting to v3 s74[scrubbed]
03-13 04:15:57.402 I/TorPlugin: Connecting to v3 2qq[scrubbed]
03-13 04:15:57.403 I/TorPlugin: Connecting to v3 fvs[scrubbed]
03-13 04:15:57.403 I/TorPlugin: Connecting to v3 hbd[scrubbed]
03-13 04:15:57.404 I/TorPlugin: Connecting to v3 cvj[scrubbed]
03-13 04:15:57.404 I/TorPlugin: Connecting to v3 btz[scrubbed]
03-13 04:15:57.404 I/TorPlugin: Connecting to v3 e6y[scrubbed]
03-13 04:15:57.404 I/TorPlugin: Connecting to v3 d5z[scrubbed]
03-13 04:15:57.408 I/TorPlugin: Could not connect to v3 fvs[scrubbed]: java.net.ConnectException: Too many open files
03-13 04:15:57.408 I/DuplexOutgoingSession: Sending keepalive
03-13 04:15:57.416 I/TorPlugin: Could not connect to v3 jqf[scrubbed]: java.net.SocketException: Too many open files
03-13 04:15:57.416 I/TorPlugin: Could not connect to v3 ick[scrubbed]: java.net.ConnectException: Too many open files
03-13 04:15:57.418 I/TorPlugin: Connecting to v3 z7i[scrubbed]
03-13 04:15:57.420 I/TorPlugin: Connecting to v3 o2j[scrubbed]
03-13 04:15:57.420 I/TorPlugin: Could not connect to v3 o2j[scrubbed]: java.net.SocketException: Too many open files
```
* NativeHeapAllocated: 16,363,552
* NativeHeapFree: 4,607,968
* NativeHeapTotal: 20,971,520
* SystemMemoryFree: 228,368,384
* SystemMemoryLow: false
* SystemMemoryThreshold: 150,994,944
* SystemMemoryTotal: 994,488,320
* VirtualMachineMemoryFree: 323,760
* VirtualMachineMemoryMaximum: 201,326,592
* VirtualMachineMemoryTotal: 44,992,648https://code.briarproject.org/briar/briar/-/issues/2421Link to original post is lost when RSS post is very long2023-03-06T16:08:14ZakwizgranLink to original post is lost when RSS post is very longWhen an RSS post is long enough that it needs to be truncated to fit into a Briar blog post, the link to the original post is lost.
This can currently be seen with the feed https://dynomight.net/feed.xml, where the post https://dynomigh...When an RSS post is long enough that it needs to be truncated to fit into a Briar blog post, the link to the original post is lost.
This can currently be seen with the feed https://dynomight.net/feed.xml, where the post https://dynomight.net/scaling/ gets truncated.https://code.briarproject.org/briar/briar/-/issues/2418"Signing out" progress screen is no longer shown when relaunching quickly aft...2023-08-08T01:50:09Zakwizgran"Signing out" progress screen is no longer shown when relaunching quickly after signing outWhen the app was relaunched quickly after signing out, we used to show a progress screen with a "signing out" message to make it clear that the user's previous action was still being processed. But now when I relaunch the app after signi...When the app was relaunched quickly after signing out, we used to show a progress screen with a "signing out" message to make it clear that the user's previous action was still being processed. But now when I relaunch the app after signing out, the UI immediately closes again without letting me see the progress screen. This can happen several times before shutdown completes, so it's not just a race between relaunching the app and shutdown completing.
Tested on Android 13 (CalyxOS 4.6.1).https://code.briarproject.org/briar/briar-desktop/-/issues/492Private messages scroll to top when switching conversations2023-03-12T20:14:24ZSebastianPrivate messages scroll to top when switching conversationsA user gave this feedback for version 0.4.0 on Windows.A user gave this feedback for version 0.4.0 on Windows.https://code.briarproject.org/briar/briar-mailbox/-/issues/190Pairing issue: Jackson 2.14.x can't serialize on Android < 8 (SDK 26)2023-08-28T16:00:11ZTorsten GrotePairing issue: Jackson 2.14.x can't serialize on Android < 8 (SDK 26)ktor-serialization-jackson 2.2.3 depends on jackson-databind 2.14.1. but jackson 2.14 has dropped support for android < 26
upstream ticket: https://youtrack.jetbrains.com/issue/KTOR-5579/Jackson-serialization-is-broken-on-older-Android-...ktor-serialization-jackson 2.2.3 depends on jackson-databind 2.14.1. but jackson 2.14 has dropped support for android < 26
upstream ticket: https://youtrack.jetbrains.com/issue/KTOR-5579/Jackson-serialization-is-broken-on-older-Android-devices
downgrading ktor to 2.1.3 would give us a temporary workaround, if needed
https://github.com/ktorio/ktor/blob/2.1.3/gradle/libs.versions.toml
forcing a jackson version without downgrading ktor may also work.
other serialization options: https://ktor.io/docs/serialization.html#register_jsonMailbox: Releasehttps://code.briarproject.org/briar/briar-desktop/-/issues/478Windows 10: tor is put under quarantine2023-08-25T13:33:34ZSebastianWindows 10: tor is put under quarantineI installed the 0.4.0 release on both my Windows 11 and Windows 10 testing machines. It works fine under Windows 11, however on Windows 10 I seemed not to get any connection when trying to add contacts. Starting Briar.exe from the comman...I installed the 0.4.0 release on both my Windows 11 and Windows 10 testing machines. It works fine under Windows 11, however on Windows 10 I seemed not to get any connection when trying to add contacts. Starting Briar.exe from the command line, I can see an exception where the `PluginManagerImpl` is not able to run program `~\.briar\desktop\tor\tor`. It tells me it cannot run the executable because it may contain a virus. The file is actually gone afterwards as it has been put into quarantine. Looking into Windows Defender, I can see that the file has been put under quarantine because it has detected "Trojan:Win32/Sabsik.FL.B!ml".Desktop 0.7.0SebastianSebastianhttps://code.briarproject.org/briar/briar-desktop/-/issues/475Visual bug with shadow in very long private messages2023-01-31T11:24:09ZMikolai GütschowVisual bug with shadow in very long private messagesHere encountered for a NoticeMessageItem:
![image](/uploads/277a6bcb5c23e69537cac25d7c678ebd/image.png)Here encountered for a NoticeMessageItem:
![image](/uploads/277a6bcb5c23e69537cac25d7c678ebd/image.png)https://code.briarproject.org/briar/briar-desktop/-/issues/468Libnotify: Segfault when querying notification server capabilities2024-03-05T19:51:44ZMikolai GütschowLibnotify: Segfault when querying notification server capabilitiesReported by a user, when trying to start Briar on a fresh installation of Raspbian (Raspberry Pi version of Debian). On the first glance doesn't look like a platform-specific issue: we could probably handle connection issues with "proxy"...Reported by a user, when trying to start Briar on a fresh installation of Raspbian (Raspberry Pi version of Debian). On the first glance doesn't look like a platform-specific issue: we could probably handle connection issues with "proxy" more gracefully?
```
10:09:01.865 [main] INFO org.briarproject.briar.desktop.Main - This is briar-desktop version 0.3.1-snapshot
10:09:01.888 [main] INFO org.briarproject.briar.desktop.Main - Build info:
10:09:01.892 [main] INFO org.briarproject.briar.desktop.Main - Git hash 93aaf03c7b364c3e82108f729ebd8b0aac8fd959-dirty
10:09:01.897 [main] INFO org.briarproject.briar.desktop.Main - Commit time 2023-01-15 15:32:21
10:09:01.902 [main] INFO org.briarproject.briar.desktop.Main - Branch build-for-arm64
(process:3319): libnotify-WARNING **: 10:09:21.347: Failed to connect to proxy
10:09:21.355 [AWT-EventQueue-0] INFO o.b.b.d.n.l.LibnotifyNotificationProvider - Notification server capabilities:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x0000000000000000, pid=3319, tid=3464
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.5+8 (17.0.5+8) (build 17.0.5+8)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.5+8 (17.0.5+8, mixed mode, tiered, compressed oops, compressed class ptrs, serial gc, linux-aarch64)
# Problematic frame:
# C 0x0000000000000000
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/<USER>/briar-desktop-arm64-0.3.1-snapshot/bin/hs_err_pid3319.log
#
# If you would like to submit a bug report, please visit:
# https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted
```https://code.briarproject.org/briar/briar-desktop/-/issues/467Theming does not work for preview of ConversationNoticeItemView2023-01-26T09:14:50ZSebastianTheming does not work for preview of ConversationNoticeItemViewI noticed that changing the theme does not work for ConversationNoticeItemView. It does however work for sibilings ConversationRequestItemView and ConversationMessageItemView. At first glance I wasn't able to find out why.
I hope it doe...I noticed that changing the theme does not work for ConversationNoticeItemView. It does however work for sibilings ConversationRequestItemView and ConversationMessageItemView. At first glance I wasn't able to find out why.
I hope it does work in the production / non-preview scenario!https://code.briarproject.org/briar/briar/-/issues/2411Xiaomi device Android 11, API 30 - crash after 'no battery restrictions' sele...2023-01-25T17:23:06ZIvanaXiaomi device Android 11, API 30 - crash after 'no battery restrictions' selectedSteps to reproduce:
- install briar debug (build 0cea137)
- when prompted go to device settings and select 'no battery restirctions'
- Briar crashes(logfile attached)
When restarted after crash, the user is not prompted to go back to ...Steps to reproduce:
- install briar debug (build 0cea137)
- when prompted go to device settings and select 'no battery restirctions'
- Briar crashes(logfile attached)
When restarted after crash, the user is not prompted to go back to battery restriction settings, but the 'Open Security settings', 'Boost speed', then 'Manual'. But when th euser navigates back to the Briar screen (by tapping the back button on the bottom of the screen, Briar crashes (logfile 2)
[Xiaomi_Briar_crash_settings.txt](/uploads/33d9e54f54cb5ccc95d8ad76205b3e91/Xiaomi_Briar_crash_settings.txt)
[Xiaomi_crash_settings_2.txt](/uploads/591436e71141cdfbf35e82c296a11312/Xiaomi_crash_settings_2.txt)https://code.briarproject.org/briar/briar-desktop/-/issues/453Let user open forum from within request message (only) after accepting the in...2023-05-11T21:20:22ZMikolai GütschowLet user open forum from within request message (only) after accepting the invitationThis issue consists of two parts:
- Currently clicking on "Open" does not do anything (`ConversationRequestItem(onOpenRequestedShareable = {})` is the default)
- After declining an invitation, "Open" is also shown to the user which doesn...This issue consists of two parts:
- Currently clicking on "Open" does not do anything (`ConversationRequestItem(onOpenRequestedShareable = {})` is the default)
- After declining an invitation, "Open" is also shown to the user which doesn't make sense:
![image](/uploads/4c950cc496d574839b90d876ac1adf3a/image.png)https://code.briarproject.org/briar/briar-desktop/-/issues/440Sometimes when starting the test with two connected accounts, the shared foru...2023-01-09T21:51:52ZSebastianSometimes when starting the test with two connected accounts, the shared forum is only available one of both accountsI haven't seen anything unusual in the logs, but will try to record one next time I see this happen.I haven't seen anything unusual in the logs, but will try to record one next time I see this happen.https://code.briarproject.org/briar/briar/-/issues/2401Testers were concerned that Briar showed Mailbox as connected when Mailbox wa...2023-08-28T16:03:27ZakwizgranTesters were concerned that Briar showed Mailbox as connected when Mailbox was offline> Participants were complaining that even when the Mailbox device was offline, on the Briar app it looked like the connection is still working well. There were no indications that the connection is not working. They were expecting to get...> Participants were complaining that even when the Mailbox device was offline, on the Briar app it looked like the connection is still working well. There were no indications that the connection is not working. They were expecting to get a notification on their Briar app device whenever there were any problems with the Mailbox connection.
>
> This was quite concerning to them, they expressed that in everyday use they would never think to manually check the connection and they would always assume that the Mailbox is working unless they get a notification on their Briar device telling them about the problems.
>
> The “Last connection…” indicator wasn’t enough to show them the connection problems. They didn’t know how often Briar automatically check the connection. For example, Mailbox device was disconnected 3 minutes ago but the screen on the Briar app didn’t indicate any problem it just showed the time of the “Last connection: 5 minutes ago”.
Some thoughts about how to address this:
* If the last connection was not very recent (say, more than a minute ago), show a neutral status instead of a successful status, to prompt the user to use the "check connection" button to update the status
* Show some text along the lines of "Briar will automatically check the connection to your Mailbox every hour and notify you if your Mailbox is not reachable", and maybe show when the next check is dueMailbox: Usability testinghttps://code.briarproject.org/briar/briar/-/issues/2399Tester didn't know whether message had been uploaded to Mailbox2023-08-28T16:03:30ZakwizgranTester didn't know whether message had been uploaded to Mailbox> The tester was confused with the process of sending a message while the other contact is offline. He was expecting to get feedback from Briar to know if the message has been saved to Mailbox. He opened the notifications drawer on the B...> The tester was confused with the process of sending a message while the other contact is offline. He was expecting to get feedback from Briar to know if the message has been saved to Mailbox. He opened the notifications drawer on the Briar phone but didn’t find anything, then he checked the Mailbox app but didn’t find feedback there either. While he was waiting, he noticed an hourglass icon near the message and didn’t know what that meant. He thought it indicated a disappearing message. After I asked a follow-up question on how he understands if a message is delivered, he let me know that one checkmark indicates that the message is delivered and two checkmarks that the message is opened.
>
> After the other contact came back online, he noticed that the message was delivered as he saw the checkmarks, but he was wondering if the message was sent directly from the app or if it was transferred by Mailbox and he didn’t find any way to understand this.
Related to #1208.Mailbox: Usability testinghttps://code.briarproject.org/briar/briar/-/issues/2398Testers didn't understand why Mailbox was still linked after failed unlinking2023-08-28T16:03:33ZakwizgranTesters didn't understand why Mailbox was still linked after failed unlinking![unlink-1](/uploads/291b980ba78f2254b8ec690bb77f1850/unlink-1.png) ![unlink-2](/uploads/1279bbd2726de7a3d2adbc3076af895c/unlink-2.png)
> This step was confusing in most cases. Participants ignored the textboxes and when they unlinked t...![unlink-1](/uploads/291b980ba78f2254b8ec690bb77f1850/unlink-1.png) ![unlink-2](/uploads/1279bbd2726de7a3d2adbc3076af895c/unlink-2.png)
> This step was confusing in most cases. Participants ignored the textboxes and when they unlinked the device, the Mailbox still showed that it was linked. In those cases, they thought that this must be happening because of bugs in the test app.Mailbox: Usability testing