briar issueshttps://code.briarproject.org/groups/briar/-/issues2023-01-19T13:12:15Zhttps://code.briarproject.org/briar/briar-mailbox/-/issues/175"Bootstrapping Tor" was confusing for some testers2023-01-19T13:12:15Zakwizgran"Bootstrapping Tor" was confusing for some testers> There were conflicting opinions about the descriptions while loading. For participants who were familiar with Tor, this was good feedback as they were able to tell what is happening in the background but for participants who weren’t fa...> There were conflicting opinions about the descriptions while loading. For participants who were familiar with Tor, this was good feedback as they were able to tell what is happening in the background but for participants who weren’t familiar with Tor, the text was confusing.Mailbox: Usability testingIvanaIvanahttps://code.briarproject.org/briar/briar-mailbox/-/issues/134Rotating devices during startup causes crash2023-01-19T13:10:55ZSebastianRotating devices during startup causes crashSteps to reproduce:
* fresh install of mailbox
* disable battery optimization using do-not-kill-me dialog
* continue to startup fragment
* rotate device
Crash:
```
2022-06-10 15:27:05.320 23832-23832/org.briarproject.mailbox E/AndroidR...Steps to reproduce:
* fresh install of mailbox
* disable battery optimization using do-not-kill-me dialog
* continue to startup fragment
* rotate device
Crash:
```
2022-06-10 15:27:05.320 23832-23832/org.briarproject.mailbox E/AndroidRuntime: FATAL EXCEPTION: main
Process: org.briarproject.mailbox, PID: 23832
java.lang.IllegalArgumentException: Navigation action/destination org.briarproject.mailbox:id/action_doNotKillMeFragment_to_startupFragment cannot be found from the current destination Destination(org.briarproject.mailbox:id/startupFragment) label=StartupFragment class=org.briarproject.mailbox.android.ui.StartupFragment
at androidx.navigation.NavController.navigate(NavController.kt:1536)
at androidx.navigation.NavController.navigate(NavController.kt:1468)
at androidx.navigation.NavController.navigate(NavController.kt:1926)
at org.briarproject.mailbox.android.ui.MainActivity.onCreate$lambda-0(MainActivity.kt:68)
```IvanaIvanahttps://code.briarproject.org/briar/briar-mailbox/-/issues/142With Do-not-keep-activities enabled, after finishing onboarding, the "Wiping ...2023-01-19T13:10:40ZSebastianWith Do-not-keep-activities enabled, after finishing onboarding, the "Wiping completed" activity gets shownThis is the log filtered by `MailboxViewModel:|MainActivity:|ActivityManager:`:
```
2022-07-12 13:19:37.117 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MainActivity: [main] onCreate()
2022-07-12 13:19:37.484 3556-3556/org.briarprojec...This is the log filtered by `MailboxViewModel:|MainActivity:|ActivityManager:`:
```
2022-07-12 13:19:37.117 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MainActivity: [main] onCreate()
2022-07-12 13:19:37.484 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MailboxViewModel: [main] Created MailboxViewModel
2022-07-12 13:19:37.494 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MainActivity: [main] do we have a saved instance state? false
2022-07-12 13:19:37.527 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MainActivity: [main] lifecycle state: NOT_STARTED
2022-07-12 13:19:37.540 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MainActivity: [main] do we have a db? false
2022-07-12 13:19:37.821 22669-22669/? W/ActivityManager: Unable to start service Intent { act=android.service.appprediction.AppPredictionService cmp=com.google.android.as/com.google.android.apps.miphone.aiai.app.AiAiPredictionService } U=0: not found
2022-07-12 13:19:38.217 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MailboxViewModel: [main] cleared
2022-07-12 13:19:40.515 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MainActivity: [main] onCreate()
2022-07-12 13:19:40.523 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MailboxViewModel: [main] Created MailboxViewModel
2022-07-12 13:19:40.523 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MainActivity: [main] do we have a saved instance state? true
2022-07-12 13:19:40.533 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MainActivity: [main] lifecycle state: NOT_STARTED
2022-07-12 13:19:40.603 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MainActivity: [main] do we have a db? false
2022-07-12 13:19:40.720 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MainActivity: [main] lifecycle state: STARTING
2022-07-12 13:19:40.742 22669-22699/? I/ActivityManager: Start proc 3647:org.briarproject.mailbox:briar_mailbox_wipe_complete/u0a176 for top-activity {org.briarproject.mailbox/org.briarproject.mailbox.android.ui.WipeCompleteActivity}
2022-07-12 13:19:40.816 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MainActivity: [main] lifecycle state: STARTING_SERVICES
2022-07-12 13:19:41.115 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MainActivity: [main] lifecycle state: RUNNING
2022-07-12 13:19:41.590 22669-22687/? I/ActivityManager: PendingStartActivityUids startActivity to updateOomAdj delay:1090ms, uid:10176
2022-07-12 13:19:41.602 3556-3556/org.briarproject.mailbox I/o.b.m.a.u.MailboxViewModel: [main] cleared
```SebastianSebastianhttps://code.briarproject.org/briar/briar-mailbox/-/issues/141Move fragment navigation to activity2023-01-19T13:10:25ZSebastianMove fragment navigation to activityFor a better overview of navigation we discussed to move it to a central place in the main activity instead of having it scattered over the individual fragments.For a better overview of navigation we discussed to move it to a central place in the main activity instead of having it scattered over the individual fragments.SebastianSebastianhttps://code.briarproject.org/briar/briar-mailbox/-/issues/144MainActivity should reset everything to an initial state when recreated with ...2023-01-19T13:09:22ZSebastianMainActivity should reset everything to an initial state when recreated with a fresh lifecycleAs [discussed here](https://code.briarproject.org/briar/briar-mailbox/-/merge_requests/99#note_68817) it can happen that the system tries to restore the activity in a state such as the QR screen while the process is a fresh one with an u...As [discussed here](https://code.briarproject.org/briar/briar-mailbox/-/merge_requests/99#note_68817) it can happen that the system tries to restore the activity in a state such as the QR screen while the process is a fresh one with an unstarted lifecycle. If we do not reset the UI to the initial state, crashes happen.MailboxSebastianSebastianhttps://code.briarproject.org/briar/briar-mailbox/-/issues/150Rotating device before onboarding becomes visible makes init screen reappear ...2023-01-19T13:09:06ZSebastianRotating device before onboarding becomes visible makes init screen reappear and user is stuck thereSebastianSebastianhttps://code.briarproject.org/briar/briar-mailbox/-/issues/151Success screen doesn't show after linking with Briar2023-01-19T13:08:51ZIvanaSuccess screen doesn't show after linking with BriarDevices used: Samsung 6910, Android 4.1.2 and Samsung Core A01S, Andorid 10
Steps to reproduce:
- do not keep activities = ON
- install mailbox on a device and when the QR screen is displayed scan it wiht the Bria app on another devic...Devices used: Samsung 6910, Android 4.1.2 and Samsung Core A01S, Andorid 10
Steps to reproduce:
- do not keep activities = ON
- install mailbox on a device and when the QR screen is displayed scan it wiht the Bria app on another device
- Whilst the proress wheel is turning on Briar, wait
- When the success screen shows on the Briar app, there shoudl be a success screen on the mailbox side too.
- However, the success screen ont he mailbox side doesn't show. See the video attached...
- not the very exciting video, as most of the time it shows just the QR code.. so be patient and then towrds the end you will see that from the QR code, the next screen that shows is the mailbox status screen, and not the success screen as it should.
ps it happens without the do-not-keep-activities selected too
![device-2022-08-04-121335](/uploads/83abb8e322965c433b4f2ab23e5f094f/device-2022-08-04-121335.mp4)IvanaIvanahttps://code.briarproject.org/briar/briar-mailbox/-/issues/153At first intro screen, if mailbox app pushed into the background then foregro...2023-01-19T13:08:33ZIvanaAt first intro screen, if mailbox app pushed into the background then foreground - it skips the rest of the intro screensDevice used: Samsung 6810 API 16, Android 4.1.2
Steps to reproduce
- fresh install mailbox
- when the first intro screen shows, push the mailbox app into the background, and open any other app for a short while
- then go back to the m...Device used: Samsung 6810 API 16, Android 4.1.2
Steps to reproduce
- fresh install mailbox
- when the first intro screen shows, push the mailbox app into the background, and open any other app for a short while
- then go back to the mailbox app.
Expected results:
- mailbox should be showing the first intro screen again as the user did not make any selection there -no tap on either skip intro, or on the continue button)
Actual results:
- mailbox displays the progress wheel instead of the expected intro screens
This happens with both do-not-keep-activities selected and not selected.
Will now try another device
OK, it can also be reproduced on Samsung A01 Core, Android 10, do-not-keep(activities = ON as well as OFF) On this device, if I leave the mailbox app in the background and open another app for a short while, then go back to the mailbox - instead of the first intro screen, I see the do-not-kill-me fragment. I would expect, like above, to see the first intro screen again because I didn't make any selection on that screen before I pushed the app into the background.SebastianSebastianhttps://code.briarproject.org/briar/briar-mailbox/-/issues/152Mailbox Intro screens in Landscape not readable Samsung 68102023-01-19T13:08:19ZIvanaMailbox Intro screens in Landscape not readable Samsung 6810Device used: Samsung 6810 Android 4.1.2, API 16
this is an old device with screen that is quite small and when in landscape some of the text on the intro screens is not readable because it seems covered by other contents of the screen. ...Device used: Samsung 6810 Android 4.1.2, API 16
this is an old device with screen that is quite small and when in landscape some of the text on the intro screens is not readable because it seems covered by other contents of the screen. See photos attached.
![Screenshot_20220804_112027](/uploads/8f13eda98fb45de1a7391519ef6c8eb3/Screenshot_20220804_112027.png)
![Screenshot_20220804_112045](/uploads/59e91480ee68bbea1bba0e24766e654e/Screenshot_20220804_112045.png)
![Screenshot_20220804_112100](/uploads/cb4e933c8560f12dade88d79730f171b/Screenshot_20220804_112100.png)Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar-mailbox/-/issues/155Remote wiping when Mailbox screen asleep => Wiping Complete screen presents t...2023-01-19T13:07:59ZIvanaRemote wiping when Mailbox screen asleep => Wiping Complete screen presents twice**Steps to reproduce**
Briar device: Samsung A01S Core, Android 10
Mailbox device: Motorola E2, Android 6
do not keep activities = On for both devices, but results are the same iwth do not keep activities = OFF on mailbox
- when Briar...**Steps to reproduce**
Briar device: Samsung A01S Core, Android 10
Mailbox device: Motorola E2, Android 6
do not keep activities = On for both devices, but results are the same iwth do not keep activities = OFF on mailbox
- when Briar and Mailbox are connected, wait for the Mailbox device screen to be askeep (ie to turn black)
- then tap Unlink on Briar side
- When the process finishes, and the Briar settings screen presents again, tap the Mailbox device screen to activate it
**Expected results:**
- Wiping complete screen presents on mailbox device.
- On taping the Finish button, the mailbox exits.
**Actual results**
- Wiping complete screen does present, but when the user taps the Finish button, instead of the mailbox app exiting, the same screen presents again, via a couple of other briefly visible screens. See video attached.
- The video screen is black initially because I started recording via Android Studio when I tapped Unlink on the Briar screen. The mailbox device screen was asleep at that time, and when the wiping finishes on Briar side, I tap the mailbox device to reactivate that screen...
![device-2022-08-09-124536](/uploads/2ad5c1e1aaf6460ddb4554b62e27ad94/device-2022-08-09-124536.mp4)https://code.briarproject.org/briar/briar-mailbox/-/issues/159Stuck on init fragment when navigating away quickly during start2023-01-19T13:07:29ZSebastianStuck on init fragment when navigating away quickly during startSteps to reproduce:
* Open app, before the first screen appears, navigate away using the (O) button, back to the home screen,
* wait a few seconds,
* go back to app, doesn't matter if via app launcher or recent apps list
You should be s...Steps to reproduce:
* Open app, before the first screen appears, navigate away using the (O) button, back to the home screen,
* wait a few seconds,
* go back to app, doesn't matter if via app launcher or recent apps list
You should be stuck at the init fragment that shows the green mailbox logo and "Briar Mailbox"SebastianSebastianhttps://code.briarproject.org/briar/briar/-/issues/2363Mailbox unreachable screen on Briar side - landscape - Samsung 6810 (small sc...2023-01-19T13:07:05ZIvanaMailbox unreachable screen on Briar side - landscape - Samsung 6810 (small screen) links overwriting each otherOn Samsung 6810 when the mailbox is not reachable, the screen looks like this - links overwriting each other
![Screenshot_20220907_164841](/uploads/d38b4a87b6ae1d09611f0f99d02fd193/Screenshot_20220907_164841.png)On Samsung 6810 when the mailbox is not reachable, the screen looks like this - links overwriting each other
![Screenshot_20220907_164841](/uploads/d38b4a87b6ae1d09611f0f99d02fd193/Screenshot_20220907_164841.png)IvanaIvanahttps://code.briarproject.org/briar/briar-mailbox/-/issues/160Wiping complete screen - button hides text in landscape orientation2023-01-19T13:06:34ZIvanaWiping complete screen - button hides text in landscape orientationThis happens on HTC E9 Android 5.0.2, HTC One M9 Android 7, Samsung 6810 Android 4.1.2 (very small screen), nokia 3.2 Android 10...
Whereas on the big screen of Huawei P40 lite 5G all the text and the button are displayed OK.
![Screensho...This happens on HTC E9 Android 5.0.2, HTC One M9 Android 7, Samsung 6810 Android 4.1.2 (very small screen), nokia 3.2 Android 10...
Whereas on the big screen of Huawei P40 lite 5G all the text and the button are displayed OK.
![Screenshot_20220907_171716](/uploads/a375e717fb43a0e044d67779719b3760/Screenshot_20220907_171716.png)https://code.briarproject.org/briar/briar/-/issues/2367Navigating back from Connection screen to Mailbox setup screens in Briar - se...2023-01-19T13:05:58ZIvanaNavigating back from Connection screen to Mailbox setup screens in Briar - second mailbox setup screen overwrites the first oneSteps to reproduce:
- In Briar go to Briar > settings > Connections and switch the internet and wifi connections off
- Then for to Briar > settings > mailbox => the mailbox is offline screen shows, which is correct
- Tap the check Con...Steps to reproduce:
- In Briar go to Briar > settings > Connections and switch the internet and wifi connections off
- Then for to Briar > settings > mailbox => the mailbox is offline screen shows, which is correct
- Tap the check Connections link on that screen => Connections screen shows, where the user can switch the internet and wifi back on
- switch the internet and wifi back on
- tap on Back button (arrow in upper left corner) and the first mailbox setup screen will show
- then tap continue => the second mailbxo setup screen overwrites the first one, see attached files
![device-2022-09-28-133914](/uploads/edcbf78a75a2348b7c280833da3ed82a/device-2022-09-28-133914.mp4)IvanaIvanahttps://code.briarproject.org/briar/briar-mailbox/-/issues/162Unable to start mailbox: SavedStateHandle issue2023-01-19T13:05:28ZIvanaUnable to start mailbox: SavedStateHandle issueUpdated the mailbox in AS to the build 84d336a47ff545be05f374bf7a5fae855f2f3c3d
The installation seems to run OK, and I get a message in Android Studio that the launch has succeeded.
However, when I try to launch the mailbox on a devi...Updated the mailbox in AS to the build 84d336a47ff545be05f374bf7a5fae855f2f3c3d
The installation seems to run OK, and I get a message in Android Studio that the launch has succeeded.
However, when I try to launch the mailbox on a device, I get this
![Screenshot_20220929_115848](/uploads/879aaf9e3cd6c3a1ec02daf21447f09c/Screenshot_20220929_115848.png)
If I go the screen App info, and tap on Open, I get the same message.
Michael took a look and attached this stack trace to the conversation in MM
```ruby
2022-09-29 12:05:16.432 6627-6627/org.briarproject.mailbox E/AndroidRuntime: FATAL EXCEPTION: main
Process: org.briarproject.mailbox, PID: 6627
java.lang.IllegalArgumentException: CreationExtras must have a value by `SAVED_STATE_REGISTRY_OWNER_KEY`
at androidx.lifecycle.SavedStateHandleSupport.createSavedStateHandle(SavedStateHandleSupport.kt:91)
at androidx.lifecycle.AbstractSavedStateViewModelFactory.create(AbstractSavedStateViewModelFactory.java:89)
at dagger.hilt.android.internal.lifecycle.HiltViewModelFactory.create(HiltViewModelFactory.java:111)
at androidx.lifecycle.ViewModelProvider.get(ViewModelProvider.kt:187)
at androidx.lifecycle.ViewModelProvider.get(ViewModelProvider.kt:153)
at androidx.lifecycle.ViewModelLazy.getValue(ViewModelLazy.kt:53)
at androidx.lifecycle.ViewModelLazy.getValue(ViewModelLazy.kt:35)
at org.briarproject.mailbox.android.ui.MainActivity.getViewModel(MainActivity.kt:68)
at org.briarproject.mailbox.android.ui.MainActivity.access$getViewModel(MainActivity.kt:59)
at org.briarproject.mailbox.android.ui.MainActivity$onCreate$2.invokeSuspend(MainActivity.kt:87)
at org.briarproject.mailbox.android.ui.MainActivity$onCreate$2.invoke(Unknown Source:8)
at org.briarproject.mailbox.android.ui.MainActivity$onCreate$2.invoke(Unknown Source:2)
at org.briarproject.mailbox.android.ui.UtilsKt$launchAndRepeatWhileStarted$1$1.invokeSuspend(Utils.kt:37)
at org.briarproject.mailbox.android.ui.UtilsKt$launchAndRepeatWhileStarted$1$1.invoke(Unknown Source:8)
at org.briarproject.mailbox.android.ui.UtilsKt$launchAndRepeatWhileStarted$1$1.invoke(Unknown Source:4)
at androidx.lifecycle.RepeatOnLifecycleKt$repeatOnLifecycle$3$1$1$1$1$1$1.invokeSuspend(RepeatOnLifecycle.kt:111)
at androidx.lifecycle.RepeatOnLifecycleKt$repeatOnLifecycle$3$1$1$1$1$1$1.invoke(Unknown Source:8)
at androidx.lifecycle.RepeatOnLifecycleKt$repeatOnLifecycle$3$1$1$1$1$1$1.invoke(Unknown Source:4)
at kotlinx.coroutines.intrinsics.UndispatchedKt.startUndispatchedOrReturn(Undispatched.kt:89)
at kotlinx.coroutines.CoroutineScopeKt.coroutineScope(CoroutineScope.kt:264)
at androidx.lifecycle.RepeatOnLifecycleKt$repeatOnLifecycle$3$1$1$1$1.invokeSuspend(RepeatOnLifecycle.kt:110)
at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
at kotlinx.coroutines.internal.DispatchedContinuationKt.resumeCancellableWith(DispatchedContinuation.kt:367)
at kotlinx.coroutines.intrinsics.CancellableKt.startCoroutineCancellable(Cancellable.kt:30)
at kotlinx.coroutines.intrinsics.CancellableKt.startCoroutineCancellable$default(Cancellable.kt:25)
at kotlinx.coroutines.CoroutineStart.invoke(CoroutineStart.kt:110)
at kotlinx.coroutines.AbstractCoroutine.start(AbstractCoroutine.kt:126)
at kotlinx.coroutines.BuildersKt__Builders_commonKt.launch(Builders.common.kt:56)
at kotlinx.coroutines.BuildersKt.launch(Unknown Source:1)
at kotlinx.coroutines.BuildersKt__Builders_commonKt.launch$default(Builders.common.kt:47)
at kotlinx.coroutines.BuildersKt.launch$default(Unknown Source:1)
at androidx.lifecycle.RepeatOnLifecycleKt$repeatOnLifecycle$3$1$1$1.onStateChanged(RepeatOnLifecycle.kt:106)
at androidx.lifecycle.LifecycleRegistry$ObserverWithState.dispatchEvent(LifecycleRegistry.java:360)
at androidx.lifecycle.LifecycleRegistry.forwardPass(LifecycleRegistry.java:271)
at androidx.lifecycle.LifecycleRegistry.sync(LifecycleRegistry.java:313)
at androidx.lifecycle.LifecycleRegistry.moveToState(LifecycleRegistry.java:151)
at androidx.lifecycle.LifecycleRegistry.handleLifecycleEvent(LifecycleRegistry.java:134)
```Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/2343End-to-end integration tests for communication via mailbox2023-01-19T13:05:12ZakwizgranEnd-to-end integration tests for communication via mailboxWrite end-to-end integration tests in which two Bramble components, representing a mailbox owner and a contact, communicate via a mailbox running on localhost.
Depends on #2228.Write end-to-end integration tests in which two Bramble components, representing a mailbox owner and a contact, communicate via a mailbox running on localhost.
Depends on #2228.MailboxSebastianSebastianhttps://code.briarproject.org/briar/briar/-/issues/2358Rotating screen while "Your Mailbox has been unlinked" dialogue box is displ...2023-01-19T13:04:56ZIvanaRotating screen while "Your Mailbox has been unlinked" dialogue box is displayed causes blank screenSteps to reproduce:
I used the Xiaomi MI11 Lite 5G device, and the Pixel 2 and was able to reproduce on both
- I link the Briar app on either device with a mailbox on another device
- Then I unlink the mailbox using the mailbox device...Steps to reproduce:
I used the Xiaomi MI11 Lite 5G device, and the Pixel 2 and was able to reproduce on both
- I link the Briar app on either device with a mailbox on another device
- Then I unlink the mailbox using the mailbox device, so that the Briar app is unable to reach it.
- Then I tap Unlink on the bottom of the mailbox status screen in the Briar app
- unlinking seems to run OK, and there is the progress wheel, and after that there is the dialogue box "Your mailbox has been unlinked.. Next time you have access to yoru ailbox device, please open the Mailbox app and tap the Unlink button to complete the process..." The only option a user has on this dialogue is to tap Got it.
- But if the screen is rotate at this point, BEFORE taping the Got it, then what we see if this:
![20220825_122023](/uploads/598074b5521d980a4cc7d44ff149a39a/20220825_122023.jpg)
Having problems wiht Android Studio which currently get frozen if i try to take a screenshot - so here's the photo of the screen taken with another phone.
If I tap the Back arrow in the top left corner of this blankscreen, then what I see is the mailbox status screen again.... Whereas the unlinking has been already done, so this screen should not be disaplyed again.
If I go back from that screen, I see Briar settings screen, and if I go into mailbox option, I see that the mailbox linking can be done again.
This happens both with do-not-keep-acitivities on and offIvanaIvanahttps://code.briarproject.org/briar/briar-mailbox/-/issues/18Upgrade dependencies2023-01-19T13:04:36ZSebastianUpgrade dependenciesMailboxSebastianSebastianhttps://code.briarproject.org/briar/briar-mailbox/-/issues/122Do not kill me screen shown again (empty) if activity gets killed2023-01-19T13:04:14ZakwizgranDo not kill me screen shown again (empty) if activity gets killedIf no battery settings need to be changed (eg Android < 6, or stock Android >= 6 with battery optimisations already disabled) then we should skip the battery settings screen rather than showing the graphic and the continue button with no...If no battery settings need to be changed (eg Android < 6, or stock Android >= 6 with battery optimisations already disabled) then we should skip the battery settings screen rather than showing the graphic and the continue button with no other content.
![Screenshot_20220512_134501](/uploads/55c24730f28f15e821a879c78f213396/Screenshot_20220512_134501.png)Mailbox: First runhttps://code.briarproject.org/briar/briar/-/issues/2316Usability testing for Mailbox app2023-01-19T13:03:49ZakwizgranUsability testing for Mailbox appAfter setup and pairing (#2315), test that users understand the information provided on the Mailbox app's status screen, are aware that the Mailbox device needs to remain connected to power and internet, and can understand and use the st...After setup and pairing (#2315), test that users understand the information provided on the Mailbox app's status screen, are aware that the Mailbox device needs to remain connected to power and internet, and can understand and use the stop, restart and unlink actions.Mailbox: Usability testing