Briar Mailbox issueshttps://code.briarproject.org/briar/briar-mailbox/-/issues2023-05-17T11:34:12Zhttps://code.briarproject.org/briar/briar-mailbox/-/issues/193Handle unchecking all bridges2023-05-17T11:34:12ZTorsten GroteHandle unchecking all bridgeshttps://code.briarproject.org/briar/briar-mailbox/-/merge_requests/169#note_76780https://code.briarproject.org/briar/briar-mailbox/-/merge_requests/169#note_76780Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/169Add Briar Mailbox to our F-Droid repo2023-05-16T12:36:47ZakwizgranAdd Briar Mailbox to our F-Droid repoMailbox: Releaseakwizgranakwizgranhttps://code.briarproject.org/briar/briar-mailbox/-/issues/170Add Briar Mailbox to Google Play2023-05-16T12:36:27ZakwizgranAdd Briar Mailbox to Google PlayClosed testing initially, then open testing, then production.Closed testing initially, then open testing, then production.Mailbox: Releaseakwizgranakwizgranhttps://code.briarproject.org/briar/briar-mailbox/-/issues/132Check that system clock is reasonable when starting2023-05-16T12:36:04ZakwizgranCheck that system clock is reasonable when startingThe lifecycle manager should check that the system's clock is reasonable (eg between 1 Jan 2022 and 1 Jan 2122) and return a startup error if not.The lifecycle manager should check that the system's clock is reasonable (eg between 1 Jan 2022 and 1 Jan 2122) and return a startup error if not.Mailbox: Manage app lifecycleIvanaIvanahttps://code.briarproject.org/briar/briar-mailbox/-/issues/83Add setting for opting in or out of Tor bridges2023-05-10T17:01:13ZSebastianAdd setting for opting in or out of Tor bridgesIt would make sense to have a way of configuring whether tor use bridges (and all the machinery that goes into deciding the default setting for a given country)It would make sense to have a way of configuring whether tor use bridges (and all the machinery that goes into deciding the default setting for a given country)Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/183ContactsManagerIntegrationTest is flaky2023-04-20T09:39:50ZSebastianContactsManagerIntegrationTest is flakySometimes, these checks fail on the CI:
* `ContactsManagerIntegrationTest > get contacts is initially empty() FAILED`
* `ContactsManagerIntegrationTest > owner can add contacts() FAILED`
Usually, a restart of the pipeline has fixed this...Sometimes, these checks fail on the CI:
* `ContactsManagerIntegrationTest > get contacts is initially empty() FAILED`
* `ContactsManagerIntegrationTest > owner can add contacts() FAILED`
Usually, a restart of the pipeline has fixed this.
Examples:
* https://code.briarproject.org/briar/briar-mailbox/-/jobs/25250
* https://code.briarproject.org/briar/briar-mailbox/-/jobs/24937
* https://code.briarproject.org/briar/briar-mailbox/-/jobs/25241
I have not been able to reproduce this locally yet.Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/185Add Gradle task for verifying translations2023-04-20T09:36:48ZakwizgranAdd Gradle task for verifying translationsAdd a Gradle task for verifying the translations, similar to the one we have for Briar.Add a Gradle task for verifying the translations, similar to the one we have for Briar.Mailbox: ReleaseTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/186Add support for Snowflake2023-03-29T13:41:38ZakwizgranAdd support for SnowflakeTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/174Upgrade logback and slf4j after logback-android released version 3.02023-03-27T12:36:00ZSebastianUpgrade logback and slf4j after logback-android released version 3.0logback-android does not support slf4j-api 2.0 yet and the result is that no logging appears in logcat at all when upgrading slf4j-api.
The [issue is known at logback-android](https://github.com/tony19/logback-android/issues/249) and [a...logback-android does not support slf4j-api 2.0 yet and the result is that no logging appears in logcat at all when upgrading slf4j-api.
The [issue is known at logback-android](https://github.com/tony19/logback-android/issues/249) and [a fix is on the way](https://github.com/tony19/logback-android/pull/247) with the author stating that he plans to release logback-android 3.0 after merging this.
!128 introduce an update with the result being that logs did not work any longer. !129 reverts the logging update of the former MR. Let's upgrade again once a new version of logback-android is available.SebastianSebastianhttps://code.briarproject.org/briar/briar-mailbox/-/issues/173Enable proguard minification2023-03-15T12:23:31ZSebastianEnable proguard minificationMailbox: ReleaseIvanaIvanahttps://code.briarproject.org/briar/briar-mailbox/-/issues/187Add cancel button in STARTING state2023-03-13T14:23:03ZTorsten GroteAdd cancel button in STARTING stateTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/189BindException when debug and release versions are running at the same time2023-03-07T12:55:40ZakwizgranBindException when debug and release versions are running at the same time```
2023-02-14 13:46:49.069 13109-13109 o.b.m.a.StatusManager org.briarproject.mailbox.debug I [main] state: StartedSettingUp
2023-02-14 13:46:49.166 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [T...```
2023-02-14 13:46:49.069 13109-13109 o.b.m.a.StatusManager org.briarproject.mailbox.debug I [main] state: StartedSettingUp
2023-02-14 13:46:49.166 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [Thread-6] V3 descriptor uploaded
2023-02-14 13:46:49.210 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [Thread-6] V3 descriptor uploaded
2023-02-14 13:46:49.309 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [Thread-6] V3 descriptor uploaded
2023-02-14 13:46:49.459 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [Thread-6] V3 descriptor uploaded
2023-02-14 13:46:50.103 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [Thread-6] V3 descriptor uploaded
2023-02-14 13:46:50.103 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [Thread-6] V3 descriptor uploaded
2023-02-14 13:46:50.211 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [Thread-6] V3 descriptor uploaded
2023-02-14 13:46:51.757 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [Thread-6] V3 descriptor uploaded
2023-02-14 13:46:53.896 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [Thread-6] V3 descriptor uploaded
2023-02-14 13:46:55.160 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [Thread-6] V3 descriptor uploaded
2023-02-14 13:46:56.460 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [Thread-6] V3 descriptor uploaded
2023-02-14 13:46:57.786 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [Thread-6] V3 descriptor uploaded
2023-02-14 13:47:00.449 13109-13191 o.b.m.c.t....tTorPlugin org.briarproject.mailbox.debug I [Thread-6] V3 descriptor uploaded
2023-02-14 13:47:30.228 13109-13176 o.b.m.c.s....leWakeLock org.briarproject.mailbox.debug I [pool-1-thread-1] Renewing wake lock org.briarproject.mailbox.debug
2023-02-14 13:47:30.229 13109-13176 o.b.m.c.s....leWakeLock org.briarproject.mailbox.debug V [pool-1-thread-1] Wake lock org.briarproject.mailbox.debug has 2 holders
2023-02-14 13:48:30.242 13109-13176 o.b.m.c.s....leWakeLock org.briarproject.mailbox.debug I [pool-1-thread-1] Renewing wake lock org.briarproject.mailbox.debug
2023-02-14 13:48:30.243 13109-13176 o.b.m.c.s....leWakeLock org.briarproject.mailbox.debug V [pool-1-thread-1] Wake lock org.briarproject.mailbox.debug has 2 holders
2023-02-14 13:49:23.338 14060-14108 AndroidRuntime pid-14060 E FATAL EXCEPTION: AndroidExecutor
Process: org.briarproject.mailbox, PID: 14060
java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method)
at sun.nio.ch.Net.bind(Net.java:454)
at sun.nio.ch.Net.bind(Net.java:446)
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:214)
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)
at io.netty.channel.socket.nio.NioServerSocketChannel.doBind(NioServerSocketChannel.java:32)
at io.netty.channel.AbstractChannel$AbstractUnsafe.bind(AbstractChannel.java:114)
at io.netty.channel.DefaultChannelPipeline$HeadContext.bind(DefaultChannelPipeline.java:3)
at io.netty.channel.AbstractChannelHandlerContext.bind(AbstractChannelHandlerContext.java:40)
at io.netty.channel.AbstractChannel.bind(AbstractChannel.java:5)
at io.netty.bootstrap.AbstractBootstrap$2.run(AbstractBootstrap.java:15)
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:17)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:204)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:35)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:11)
at io.ktor.server.netty.EventLoopGroupProxy$Companion$$ExternalSyntheticLambda1.run(R8$$SyntheticClass:20)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:3)
at java.lang.Thread.run(Thread.java:761)
2023-02-14 13:49:23.342 1274-3841 ActivityManager pid-1274 E App crashed! Process: org.briarproject.mailbox
at java.lang.Thread.run(Thread.java:761)
```
It looks like this is thrown after the hidden service has been published, so it's not the Tor port that's causing the conflict.Mailbox: ReleaseTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/23Add Gradle witness (or something similar)2023-03-01T12:15:22ZSebastianAdd Gradle witness (or something similar)We could use the gradle witness plugin as in briar or maybe use the checksum-dependency plugin which has already been discussed here: https://code.briarproject.org/briar/briar/-/merge_requests/1175We could use the gradle witness plugin as in briar or maybe use the checksum-dependency plugin which has already been discussed here: https://code.briarproject.org/briar/briar/-/merge_requests/1175MailboxTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/157Tapping the Unlink (briar side) and Stop (mailbox side) at the same time - ma...2023-02-21T20:12:48ZIvanaTapping the Unlink (briar side) and Stop (mailbox side) at the same time - mailbox stuck in StoppingMailbox**Steps to reproduce**
- On two devices that are linked (I used Nokia 3.2 Android 10 for Briar and HTC E9 Android 5 for Mailbox) I open the mailbox status screen on each device.
- Then on briar I tap the unlink button and immediatley a...**Steps to reproduce**
- On two devices that are linked (I used Nokia 3.2 Android 10 for Briar and HTC E9 Android 5 for Mailbox) I open the mailbox status screen on each device.
- Then on briar I tap the unlink button and immediatley after (almost at the same time) I tap the Stop button on the mailbox side.
**Expected results**
This is a bit of a corner case, and not very likely to happen, but in case it does, the expected result should be graceful handling of this situation - either the wiping complete screen should be seen on the mailbox side, or mailbox stopped.
**Actual result**
Mailbox gets stuck in the Stopping Mailbox state[unlink_and_stop_button_together.txt](/uploads/01bc05f817f642e8fb97117654f106bb/unlink_and_stop_button_together.txt)
![Screenshot_20220810_130437](/uploads/c315d676d6aa79c1cde95cb8ba3f9255/Screenshot_20220810_130437.png)IvanaIvanahttps://code.briarproject.org/briar/briar-mailbox/-/issues/171Reproducible builds2023-02-17T14:02:59ZakwizgranReproducible buildsBuild the mailbox app reproducibly, perhaps by modifying briar-reproducer. Set up CI hooks so that a reproducible build is triggered when a tag is pushed.Build the mailbox app reproducibly, perhaps by modifying briar-reproducer. Set up CI hooks so that a reproducible build is triggered when a tag is pushed.Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/156WipeComplete screen shows same message for both local and remote wiping2023-02-08T17:17:54ZSebastianWipeComplete screen shows same message for both local and remote wipingIn either case, the message says: 'Next time you have access to your Briar device, please open the Mailbox settings screen in the Briar app, then tap the \"Unlink\" button to complete the process'. That could potentially be confusing for...In either case, the message says: 'Next time you have access to your Briar device, please open the Mailbox settings screen in the Briar app, then tap the \"Unlink\" button to complete the process'. That could potentially be confusing for the user in the case of a remote wipe as this step is no longer possible and actually already happened.
Test instructions: with Briar and Mailbox successfully linked, wipe once locally and once remotely from Briar (link the apps again after the first wiping). Check that when wiping locally (i.e. from the Mailbox app's status screen), the confirmation screen shows an explainer text to wipe on Briar later on too. When wiping remotely (from Briar's mailbox status screen) check that the confirmation screen on the Mailbox app does not contain the explainer.Mailbox: UnpairingIvanaIvanahttps://code.briarproject.org/briar/briar-mailbox/-/issues/184Add Mailbox strings to Transifex2023-02-07T13:24:02ZakwizgranAdd Mailbox strings to TransifexMailbox: ReleaseTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/172Update target SDK to 332023-02-07T13:23:54ZSebastianUpdate target SDK to 33MailboxTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/163Notification does not update when app is in background2023-02-07T13:22:57ZSebastianNotification does not update when app is in backgroundI think we had this problem before and also solved it at some point, but it seems we have a regression.
Steps to reproduce:
* start non-paired mailbox
* put mailbox into background while it is starting up
* on logs, observe that tor get...I think we had this problem before and also solved it at some point, but it seems we have a regression.
Steps to reproduce:
* start non-paired mailbox
* put mailbox into background while it is starting up
* on logs, observe that tor gets into published state
* observe that the notification is still "Starting mailbox…"
* switch back to app which should be at the qr code screen now
* observe that notification has now changed to "Waiting for Briar to scan QR code…"
We're collecting the app state in MainActivity only when the activity is started, so it makes sense that currently no updates get processed when the activity is in the background.MailboxIvanaIvanahttps://code.briarproject.org/briar/briar-mailbox/-/issues/182No logs on Android since minification is enabled2023-01-27T11:40:24ZSebastianNo logs on Android since minification is enabledMailbox: ReleaseSebastianSebastian