briar issueshttps://code.briarproject.org/groups/briar/-/issues2021-11-04T11:03:23Zhttps://code.briarproject.org/briar/briar/-/issues/1903IllegalArgumentException when opening forum2021-11-04T11:03:23ZakwizgranIllegalArgumentException when opening forum* Android version: 9
* Phone model: OnePlus ONE A2003 (lineage_oneplus2)
* Briar version: 1.2.7 (eb562f8)
Stacktrace:
```
java.lang.IllegalArgumentException
at android.os.Parcel.createException(Parcel.java:1954)
at andro...* Android version: 9
* Phone model: OnePlus ONE A2003 (lineage_oneplus2)
* Briar version: 1.2.7 (eb562f8)
Stacktrace:
```
java.lang.IllegalArgumentException
at android.os.Parcel.createException(Parcel.java:1954)
at android.os.Parcel.readException(Parcel.java:1918)
at android.os.Parcel.readException(Parcel.java:1868)
at android.app.IActivityManager$Stub$Proxy.startActivity(IActivityManager.java:3756)
at android.app.Instrumentation.execStartActivity(Instrumentation.java:1669)
at android.app.Activity.startActivityForResult(Activity.java:4587)
at androidx.fragment.app.FragmentActivity.startActivityForResult(FragmentActivity.java:676)
at android.app.Activity.startActivityForResult(Activity.java:4545)
at androidx.fragment.app.FragmentActivity.startActivityForResult(FragmentActivity.java:663)
at android.app.Activity.startActivity(Activity.java:4906)
at android.app.Activity.startActivity(Activity.java:4874)
at org.briarproject.briar.android.forum.ForumListAdapter.lambda$onBindViewHolder$0$ForumListAdapter(ForumListAdapter.java:77)
at org.briarproject.briar.android.forum.-$$Lambda$ForumListAdapter$kAL6Ao0lW0KDG5V1g1qgxdCGy3I.onClick(Unknown Source:4)
at android.view.View.performClick(View.java:6597)
at android.view.View.performClickInternal(View.java:6574)
at android.view.View.access$3100(View.java:778)
at android.view.View$PerformClick.run(View.java:25906)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6718)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
Caused by: android.os.RemoteException: Remote stack trace:
at android.view.SurfaceControl.nativeCreate(Native Method)
at android.view.SurfaceControl.<init>(SurfaceControl.java:630)
at android.view.SurfaceControl.<init>(SurfaceControl.java:60)
at android.view.SurfaceControl$Builder.build(SurfaceControl.java:386)
at com.android.server.wm.WindowContainer.onParentSet(WindowContainer.java:184)
android.os.RemoteException: Remote stack trace:
at android.view.SurfaceControl.nativeCreate(Native Method)
at android.view.SurfaceControl.<init>(SurfaceControl.java:630)
at android.view.SurfaceControl.<init>(SurfaceControl.java:60)
at android.view.SurfaceControl$Builder.build(SurfaceControl.java:386)
at com.android.server.wm.WindowContainer.onParentSet(WindowContainer.java:184)
```
Edited log:
```
05-12 17:27:04.042 I/BaseActivity: Starting ForumActivity
05-12 17:27:04.091 I/ThreadListControllerImpl: Loaded last top visible message id MessageId(BF612DC59E492610586538167B84439EF006DC1023B5657A39A8C209E7547F5D)
05-12 17:27:05.922 I/ThreadScrollListener: Updating unread count: top=0 bottom=0
05-12 17:27:05.932 I/ThreadScrollListener: Updating unread count: top=0 bottom=0
05-12 17:27:06.895 I/BaseActivity: Starting NavDrawerActivity
05-12 17:27:07.458 I/BaseActivity: Stopping ForumActivity
05-12 17:27:30.902 I/BasePostFragment: Adding Handler Callback
05-12 17:27:30.903 I/BaseControllerImpl: Loaded header from cache
05-12 17:27:30.903 I/BaseControllerImpl: Loaded text from cache
05-12 17:28:03.454 I/BasePostFragment: Removing Handler Callback
05-12 17:28:12.397 I/BasePostFragment: Adding Handler Callback
05-12 17:28:12.397 I/BaseControllerImpl: Loaded header from cache
05-12 17:28:12.397 I/BaseControllerImpl: Loaded text from cache
05-12 17:28:13.457 I/BasePostFragment: Removing Handler Callback
05-12 17:28:23.866 I/BaseActivity: Stopping NavDrawerActivity
05-12 17:28:51.251 I/BaseActivity: Starting NavDrawerActivity
```
The crash happens when calling startActivity() to open ForumActivity. The extras are the group ID and forum name.
Note: on current master this call has moved to ForumViewHolder.Android 1.4https://code.briarproject.org/briar/briar/-/issues/1904IllegalStateException when backing out of blog feed2021-02-17T17:19:39ZakwizgranIllegalStateException when backing out of blog feed* Android version: 4.4.4
* Phone model: Sony Xperia X
* Briar version: 1.2.7 (eb562f8)
* User feedback: "I've pressed back button on Blogs page."
Stacktrace:
```
java.lang.IllegalStateException: Can not perform this action after onSaveI...* Android version: 4.4.4
* Phone model: Sony Xperia X
* Briar version: 1.2.7 (eb562f8)
* User feedback: "I've pressed back button on Blogs page."
Stacktrace:
```
java.lang.IllegalStateException: Can not perform this action after onSaveInstanceState
at androidx.fragment.app.FragmentManagerImpl.checkStateLoss(FragmentManagerImpl.java:1536)
at androidx.fragment.app.FragmentManagerImpl.enqueueAction(FragmentManagerImpl.java:1558)
at androidx.fragment.app.BackStackRecord.commitInternal(BackStackRecord.java:317)
at androidx.fragment.app.BackStackRecord.commit(BackStackRecord.java:282)
at org.briarproject.briar.android.navdrawer.NavDrawerActivity.startFragment(NavDrawerActivity.java:331)
at org.briarproject.briar.android.navdrawer.NavDrawerActivity.startFragment(NavDrawerActivity.java:315)
at org.briarproject.briar.android.navdrawer.NavDrawerActivity.startFragment(NavDrawerActivity.java:310)
at org.briarproject.briar.android.navdrawer.NavDrawerActivity.onBackPressed(NavDrawerActivity.java:277)
at android.app.Activity.onKeyUp(Activity.java:2193)
at android.view.KeyEvent.dispatch(KeyEvent.java:2664)
at androidx.core.view.KeyEventDispatcher.activitySuperDispatchKeyEventPre28(KeyEventDispatcher.java:137)
at androidx.core.view.KeyEventDispatcher.dispatchKeyEvent(KeyEventDispatcher.java:87)
at androidx.core.app.ComponentActivity.dispatchKeyEvent(ComponentActivity.java:133)
at androidx.appcompat.app.AppCompatActivity.dispatchKeyEvent(AppCompatActivity.java:558)
at androidx.appcompat.view.WindowCallbackWrapper.dispatchKeyEvent(WindowCallbackWrapper.java:59)
at androidx.appcompat.app.AppCompatDelegateImpl$AppCompatWindowCallback.dispatchKeyEvent(AppCompatDelegateImpl.java:2814)
at androidx.appcompat.view.WindowCallbackWrapper.dispatchKeyEvent(WindowCallbackWrapper.java:59)
at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchKeyEvent(PhoneWindow.java:1962)
at android.view.ViewRootImpl$ViewPostImeInputStage.processKeyEvent(ViewRootImpl.java:3845)
at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:3819)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3392)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3442)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3411)
at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:3518)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3419)
at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:3575)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3392)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3442)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3411)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3419)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3392)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3442)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3411)
at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:3551)
at android.view.ViewRootImpl$ImeInputStage.onFinishedInputEvent(ViewRootImpl.java:3711)
at android.view.inputmethod.InputMethodManager$PendingEvent.run(InputMethodManager.java:2043)
at android.view.inputmethod.InputMethodManager.invokeFinishedInputEventCallback(InputMethodManager.java:1737)
at android.view.inputmethod.InputMethodManager.finishedInputEvent(InputMethodManager.java:1728)
at android.view.inputmethod.InputMethodManager$ImeInputEventSender.onInputEventFinished(InputMethodManager.java:2020)
at android.view.InputEventSender.dispatchInputEventFinished(InputEventSender.java:141)
at android.os.MessageQueue.nativePollOnce(Native Method)
at android.os.MessageQueue.next(MessageQueue.java:138)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:5001)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:797)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:613)
at dalvik.system.NativeStart.main(Native Method)
```
Last lines of log:
```
10-18 21:06:06.210 I/BaseActivity: Starting NavDrawerActivity
10-18 21:06:06.247 I/BaseActivity: Stopping NavDrawerActivity
10-18 21:06:06.416 I/BaseActivity: Starting NavDrawerActivity
10-18 21:06:06.431 I/BaseActivity: Stopping NavDrawerActivity
```
This looks similar to #1423.Android 1.2IvanaIvanahttps://code.briarproject.org/briar/briar/-/issues/1905Use ContactListViewModel in ContactChooserFragment and IntroductionActivity2021-04-26T12:51:23ZSebastianUse ContactListViewModel in ContactChooserFragment and IntroductionActivity!1341 introduced the ContactListViewModel which should be reusable by ContactChooserFragment and IntroductionActivity!1341 introduced the ContactListViewModel which should be reusable by ContactChooserFragment and IntroductionActivityAdapt to changes in the Android platformSebastianSebastian2021-04-30https://code.briarproject.org/briar/briar/-/issues/1906Make app less visible.2021-01-18T22:50:15ZVladislavMake app less visible.If it is possible to have an option, or another version of briar, that would be less visible in androd launcher.
So, in case, someone get acces to your phone, he will not find there secured messenger app, and will not insult you to logi...If it is possible to have an option, or another version of briar, that would be less visible in androd launcher.
So, in case, someone get acces to your phone, he will not find there secured messenger app, and will not insult you to login.
For example: Traccar android client app '''
In addition to standard version available on the Google Play, Traccar Client for Android comes in a special hidden version. It includes modifications to make the app less visible to the phone's owner. Name is changed from "Traccar Client" to "Device Settings". Default Android settings icon is used as an app icon. After first start, the app removes itself from the launcher on older versions of Android. To open it again dial 8722227 (TRACCAR).'''https://code.briarproject.org/briar/briar/-/issues/1907Identical messages are treated as duplicates2021-01-19T12:38:48ZakwizgranIdentical messages are treated as duplicatesUnder unlikely circumstances, different devices may create identical messages. If a device receives a message that's identical to one it created, it will treat it as a redundant copy of its own message.
We could prevent this by includin...Under unlikely circumstances, different devices may create identical messages. If a device receives a message that's identical to one it created, it will treat it as a redundant copy of its own message.
We could prevent this by including salt in each message at the client layer or the sync layer.https://code.briarproject.org/briar/briar/-/issues/1908Going offline2022-02-25T15:03:53ZWuukoGoing offlineI was online but I'm offline.I was online but I'm offline.https://code.briarproject.org/briar/briar/-/issues/1909When adding contact at distance, remind that both users need to send link2023-02-23T10:17:39ZIvanaWhen adding contact at distance, remind that both users need to send linkAs a new briar user, Ivana didn't find clear how to connect to other users via internet. These are the points that came up during the walk-through..
When a phone has no access to internet, or wifi, and the briar user select to add a co...As a new briar user, Ivana didn't find clear how to connect to other users via internet. These are the points that came up during the walk-through..
When a phone has no access to internet, or wifi, and the briar user select to add a contact, via 'at a distance' option, they are not warned about absence of internet connection...
- Should there be a message to the user that they are not connected to internet, therefore cannot use the 'connect at a distance option'?
- A sender then sends the code to a contacg via SMS.
- The recipient receives the code in an SMS and retrieves it (using copy/paste of the android phone - which to this user was not immediately clear as they were not familiar with copy/paste facility of the android phones
- The recipient then briar application, add new contact page, and pastes this code into the field provided.
(To a new user who receives a code with no explanation what to do with it, it may not be clear what it is for? this presuposes some familiarity with briar app)
- Then the user taps 'continue button'. What happens next is that they get the next screen where they are given a little green 'tick' that everything was correct, and they are asked to enter a nickname for their new contact.
- However, at this point, the recipient did not send their own code back to the the person who invited them. So alhough they are given the OK by the app, this new contact (on the recipient's phone) stays in the 'connecting', or 'waiting for the contact to come online'..; and nothign else happens.
- Of course the connection cannot be established because the first user (sender) did not receive their firend's (recipient's) code at this point.
Ther was a talk on mattermost about how this could be handled in a way that guides the recipient a bit more, so that connection is actually achieved.
Suggestions made were:
- popup box before the receiving user clicks on 'Continue' - that would remind them to send their code to the person who invited them. But this wqs thought to be quite annoying to the more experienced users - hving to dismiss this popup. To get around this annoyance, they could select, maybe, a checkbox that says: 'do not show this info again'.
- another suggestion was to include a little checkbox before enabling the continue button (like the checkboxes included in webpaged to signal that the user accepts the terms and conditions). It could say something like 'I sent my own code to the person who send me their own' or whatever makes more sense; This could be easy to use for experienced users, as it woudl just be a checkbox ont he screen, but for newbies, it would be guidance to follow the propoer procedure to establish a connection.
-https://code.briarproject.org/briar/briar/-/issues/1910IllegalStateException when adding contact remotely2021-02-17T17:19:12ZakwizgranIllegalStateException when adding contact remotely* Android version: 8.0.0
* Phone model: Samsung SM-A520F (a5y17ltexx)
* Briar version: 1.2.12 (54893d2)
Stacktrace:
```
java.lang.IllegalStateException
at org.briarproject.briar.android.contact.add.remote.AddContactViewModel.add...* Android version: 8.0.0
* Phone model: Samsung SM-A520F (a5y17ltexx)
* Briar version: 1.2.12 (54893d2)
Stacktrace:
```
java.lang.IllegalStateException
at org.briarproject.briar.android.contact.add.remote.AddContactViewModel.addContact(AddContactViewModel.java:104)
at org.briarproject.briar.android.contact.add.remote.NicknameFragment.onAddButtonClicked(NicknameFragment.java:127)
at org.briarproject.briar.android.contact.add.remote.NicknameFragment.lambda$onCreateView$0$NicknameFragment(NicknameFragment.java:88)
at org.briarproject.briar.android.contact.add.remote.-$$Lambda$NicknameFragment$DP4SKMB9Kkf7jxUQrVMBWLNcvuI.onClick(Unknown Source:2)
at android.view.View.performClick(View.java:6897)
at android.widget.TextView.performClick(TextView.java:12727)
at android.view.View$PerformClick.run(View.java:26101)
at android.os.Handler.handleCallback(Handler.java:789)
at android.os.Handler.dispatchMessage(Handler.java:98)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6944)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
```
Edited log:
```
01-14 16:53:22.538 I/AndroidNetworkManager: Received broadcast android.intent.action.SCREEN_ON
01-14 16:53:33.404 I/BaseActivity: Creating NavDrawerActivity
01-14 16:53:33.504 I/BaseActivity: Starting NavDrawerActivity
01-14 16:53:33.512 I/BaseActivity: Resuming NavDrawerActivity
01-14 16:53:36.039 I/BaseActivity: Pausing NavDrawerActivity
01-14 16:53:36.059 I/BaseActivity: Creating AddContactActivity
01-14 16:53:36.114 I/BaseActivity: Starting AddContactActivity
01-14 16:53:36.779 I/BaseActivity: Resuming AddContactActivity
01-14 16:53:37.277 I/BaseActivity: Stopping NavDrawerActivity
01-14 16:53:37.298 I/BaseActivity: Destroying NavDrawerActivity
01-14 16:53:49.623 I/BaseActivity: Pausing AddContactActivity
01-14 16:53:49.643 I/BaseActivity: Stopping AddContactActivity
01-14 16:53:49.667 I/BaseActivity: Destroying AddContactActivity
01-14 16:53:53.323 I/BaseActivity: Creating AddContactActivity
01-14 16:53:53.399 I/BaseActivity: Starting AddContactActivity
01-14 16:53:53.405 I/BaseActivity: Resuming AddContactActivity
```Android 1.2IvanaIvanahttps://code.briarproject.org/briar/briar/-/issues/1911Emoji Input does not work on LG-P875H (Android 4.4)2021-05-31T13:41:01ZTorsten GroteEmoji Input does not work on LG-P875H (Android 4.4)Clicking the emoji icon brings up the normal keyboard. The icon stays emoji. When clicking it again, it turns into a keyboard icon, but the keyboard itself is still shown without change.
Running Android 4.1.2Clicking the emoji icon brings up the normal keyboard. The icon stays emoji. When clicking it again, it turns into a keyboard icon, but the keyboard itself is still shown without change.
Running Android 4.1.2https://code.briarproject.org/briar/briar/-/issues/1913Bomb icon on images not white on API 162021-03-08T12:27:36ZSebastianBomb icon on images not white on API 16The bomb icon is grey on grey background which makes it difficult to see.
Its possible that !1346 will help find a simple solution for this.
![Screen01](/uploads/2739eda519037ebf5d109d087fc44746/Screen01.png)The bomb icon is grey on grey background which makes it difficult to see.
Its possible that !1346 will help find a simple solution for this.
![Screen01](/uploads/2739eda519037ebf5d109d087fc44746/Screen01.png)Self-destructing messagesSebastianSebastian2021-01-31https://code.briarproject.org/briar/briar/-/issues/1915Optimise ConnectionRegistry calls in SharingControllerImpl2021-04-30T13:35:47ZakwizgranOptimise ConnectionRegistry calls in SharingControllerImplSubtask of #1823.Subtask of #1823.https://code.briarproject.org/briar/briar/-/issues/1916Remove locking from MessageTreeImpl and mark the interface @UiThread2021-04-30T13:35:41ZakwizgranRemove locking from MessageTreeImpl and mark the interface @UiThreadSubtask of #1823.Subtask of #1823.https://code.briarproject.org/briar/briar/-/issues/1917Crash reporter captures log from crash reporter process, not main process2021-03-24T16:05:15ZakwizgranCrash reporter captures log from crash reporter process, not main processThe new crash reporter captures the log output from the crash reporter process, not the main Briar process. This log output doesn't give any information about the cause of the crash - it just shows the crash reporter process being create...The new crash reporter captures the log output from the crash reporter process, not the main Briar process. This log output doesn't give any information about the cause of the crash - it just shows the crash reporter process being created, injecting its components and launching CrashReportActivity.Android 1.2IvanaIvanahttps://code.briarproject.org/briar/briar/-/issues/1918Onion address collision when adding contact2021-02-03T12:37:49ZakwizgranOnion address collision when adding contact* Android version: 10
* Phone model: Samsung SM-A107F (a10sxx)
* Briar version: 1.2.13 (5fdc7e7)
* User feedback: "Unfortunately, I could not connect to my friend. It didn't work. I could not understand the problem."
Log snippet:
```
02...* Android version: 10
* Phone model: Samsung SM-A107F (a10sxx)
* Briar version: 1.2.13 (5fdc7e7)
* User feedback: "Unfortunately, I could not connect to my friend. It didn't work. I could not understand the problem."
Log snippet:
```
02-03 11:37:17.631 I/PluginManagerImpl: org.briarproject.bramble.tor changed from state ENABLING to ACTIVE
02-03 11:37:17.631 I/TorPlugin: First circuit built
02-03 11:37:17.631 I/PluginViewModel: TransportStateEvent: org.briarproject.bramble.tor is ACTIVE
02-03 11:37:17.640 I/AndroidTaskScheduler: Running 1 due tasks
02-03 11:37:17.640 I/AndroidTaskScheduler: Task is 0 ms overdue
02-03 11:37:17.642 I/PollerImpl: Polling plugin org.briarproject.bramble.tor
02-03 11:37:17.643 I/ConnectionRegistryImpl: 0 contacts connected or better: org.briarproject.bramble.tor
02-03 11:37:17.688 I/TorPlugin: WARN tor_bug_occurred_(): Bug: src/feature/hs/hs_service.c:3603: hs_servic
e_add_ephemeral: Non-fatal assertion !(register_service(hs_service_map, service) < 0) failed. (on Tor 0.3.5.12 a0b827eb5b50aa81)
02-03 11:37:17.689 I/TorPlugin: WARN Bug: Tor 0.3.5.12 (git-a0b827eb5b50aa81): Non-fatal assertion !(register_service(hs_service_map, service) < 0) failed in hs_service_add_ephemeral at src/feature/hs/hs_service.c:3603. (Stack trace not available) (on Tor 0.3.5.12 a0b827eb5b50aa81)
02-03 11:37:17.689 I/TorPlugin: WARN Onion Service private key collides with an existing v3 service.
02-03 11:37:17.689 W/TorPlugin: net.freehaven.tor.control.TorControlError: Error reply: Onion address collision
net.freehaven.tor.control.TorControlError: Error reply: Onion address collision
at net.freehaven.tor.control.TorControlConnection.sendAndWaitForResponse(TorControlConnection.java:204)
at net.freehaven.tor.control.TorControlConnection.addOnion(TorControlConnection.java:837)
at net.freehaven.tor.control.TorControlConnection.addOnion(TorControlConnection.java:786)
at org.briarproject.bramble.plugin.tor.TorPlugin.createRendezvousEndpoint(TorPlugin.java:751)
at org.briarproject.bramble.rendezvous.RendezvousPollerImpl.createEndpoint(RendezvousPollerImpl.java:213)
at org.briarproject.bramble.rendezvous.RendezvousPollerImpl.addTransport(RendezvousPollerImpl.java:350)
at org.briarproject.bramble.rendezvous.RendezvousPollerImpl.lambda$addTransportAsync$5(RendezvousPollerImpl.java:339)
at org.briarproject.bramble.rendezvous.RendezvousPollerImpl.lambda$addTransportAsync$5$RendezvousPollerImpl(Unknown Source:0)
at org.briarproject.bramble.rendezvous.-$$Lambda$RendezvousPollerImpl$h19OH8Qm1qYh76tkmxUCO9U4dzc.run(Unknown Source:4)
at org.briarproject.bramble.PoliteExecutor.lambda$execute$0(PoliteExecutor.java:57)
at org.briarproject.bramble.PoliteExecutor.lambda$execute$0$PoliteExecutor(Unknown Source:0)
at org.briarproject.bramble.-$$Lambda$PoliteExecutor$wSvuPL6t_HUoaaqCVexrhJX_RSg.run(Unknown Source:6)
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:919)
```https://code.briarproject.org/briar/briar/-/issues/1919Password fields not focusable when navigated back to from the next page (keyb...2021-07-06T10:01:58ZIvanaPassword fields not focusable when navigated back to from the next page (keyboard doesn't come up when they are tapped)The test scenario was like this:
I type in my nickname on the first screen and I tap Next button. Then I proceed to type in my passwords, and click next (on the keyboard Next button).
A message comes up onthe next screen informing th...The test scenario was like this:
I type in my nickname on the first screen and I tap Next button. Then I proceed to type in my passwords, and click next (on the keyboard Next button).
A message comes up onthe next screen informing the user that briar has to stay connected and that they user should switch off the battery optimisation.
From that screen user navigates back to the password screen, because they changed their mind about what password to use and they want to change it.
The passwords cannot be changed because the keyboard doesn't come up when fields are tapped, so user cannot type. This was confirmed a bug in mattermost conversation (Testing channel, 3.2.21, around noon)
What should happen here? Should the user be able to chang etheir password from here?
Or should something else happen when they navigate back to the password page?
Please describe the details of solution in here so they can be re-tested when fied.
mp4 attached for your info.
![device-2021-02-03-124850](/uploads/2f3f336a75746a0b25efd7d786886283/device-2021-02-03-124850.mp4)Adapt to changes in the Android platformIvanaIvana2021-04-30https://code.briarproject.org/briar/briar/-/issues/1920Change Password 'Done' IME action button doesn't complete flow2021-02-03T14:09:31ZIvanaChange Password 'Done' IME action button doesn't complete flowThis is a very small issue in that when that user types up a new password, and taps Done on the keyboard, the keybaoard itself is dismissed, the the page remains disaplayed, as thought eh workflow is not complete. Only when the user tap...This is a very small issue in that when that user types up a new password, and taps Done on the keyboard, the keybaoard itself is dismissed, the the page remains disaplayed, as thought eh workflow is not complete. Only when the user taps on Change password button the screen is dismissed and the next one shows.
This is really only a very small annoyance to the user - so ... ti fix or not to fix will be a decision based on project priorities.![device-2021-02-03-142650](/uploads/ea69b203021c4b46419e86db1e156b78/device-2021-02-03-142650.mp4)https://code.briarproject.org/briar/briar/-/issues/1921PluginViewModel should wait for DB to open before loading settings2021-04-21T11:29:10ZakwizgranPluginViewModel should wait for DB to open before loading settingsWhile testing something unrelated on the 1.2.12 release I noticed this exception in the log:
```
02-03 16:15:52.017 2925-2952/org.briarproject.briar.android.debug W/PluginViewModel: org.briarproject.bramble.api.db.DbClosedException
...While testing something unrelated on the 1.2.12 release I noticed this exception in the log:
```
02-03 16:15:52.017 2925-2952/org.briarproject.briar.android.debug W/PluginViewModel: org.briarproject.bramble.api.db.DbClosedException
org.briarproject.bramble.api.db.DbClosedException
at org.briarproject.bramble.db.H2Database.createConnection(H2Database.java:97)
at org.briarproject.bramble.db.JdbcDatabase.startTransaction(JdbcDatabase.java:554)
at org.briarproject.bramble.db.JdbcDatabase.startTransaction(JdbcDatabase.java:97)
at org.briarproject.bramble.db.DatabaseComponentImpl.startTransaction(DatabaseComponentImpl.java:161)
at org.briarproject.bramble.db.DatabaseComponentImpl.transactionWithResult(DatabaseComponentImpl.java:208)
at org.briarproject.bramble.settings.SettingsManagerImpl.getSettings(SettingsManagerImpl.java:26)
at org.briarproject.briar.android.navdrawer.PluginViewModel.isPluginEnabled(PluginViewModel.java:204)
at org.briarproject.briar.android.navdrawer.PluginViewModel.lambda$loadSettings$0$PluginViewModel(PluginViewModel.java:187)
at org.briarproject.briar.android.navdrawer.-$$Lambda$PluginViewModel$HPPDOnjY7Hk6kE7RpR2no4vHis8.run(lambda)
at org.briarproject.bramble.TimeLoggingExecutor.lambda$execute$0$TimeLoggingExecutor(TimeLoggingExecutor.java:36)
at org.briarproject.bramble.-$$Lambda$TimeLoggingExecutor$Bqrtbsq_8LcRPoTWBOef6xh7gJg.run(lambda)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
```
This happens at startup when NavDrawerActivity is created before signing in, as PluginViewModel tries to load the plugin settings.
This is currently harmless because a new NavDrawerActivity instance is created after signing in, with a new view model instance that successfully loads the settings. But that's just a lucky accident. To avoid depending on that, perhaps it would be better to refactor PluginViewModel to use DbViewModel#runOnDbThread()?Adapt to changes in the Android platformSebastianSebastian2021-04-30https://code.briarproject.org/briar/briar/-/issues/1922Upgrade Tor to 0.3.5.132021-02-17T17:19:27ZakwizgranUpgrade Tor to 0.3.5.13Tor 0.3.5.13 includes the following bugfix that should improve v3 hidden service reachability:
> Major bugfixes (onion service v3, backport from 0.4.5.3-rc):
> - Stop requiring a live consensus for v3 clients and services, and
> allow...Tor 0.3.5.13 includes the following bugfix that should improve v3 hidden service reachability:
> Major bugfixes (onion service v3, backport from 0.4.5.3-rc):
> - Stop requiring a live consensus for v3 clients and services, and
> allow a "reasonably live" consensus instead. This allows v3 onion
> services to work even if the authorities fail to generate a
> consensus for more than 2 hours in a row. Fixes bug 40237; bugfix
> on 0.3.5.1-alpha.Android 1.2IvanaIvanahttps://code.briarproject.org/briar/briar/-/issues/1923Mailing list migration2021-02-16T23:06:44ZsysterMailing list migrationMailing list migration:
For the reasons:
https://code.briarproject.org/briar/briar/-/issues/988
https://code.briarproject.org/briar/briar/-/issues/1741
"_sourceforge doesn't give us access to the subscriptions_"
migration is bet...Mailing list migration:
For the reasons:
https://code.briarproject.org/briar/briar/-/issues/988
https://code.briarproject.org/briar/briar/-/issues/1741
"_sourceforge doesn't give us access to the subscriptions_"
migration is better done soonish, then later.
-----------------------------------------------------------
**Solution 1:**
Creating new lists and announcing them. Letting the old lists run for 1 year or something and regular invite folks to join the new lists.
**Solution 2:**
There is access to subscribers email pre-2017. They can be migrated to new service and sending them an email asking for confirmation. Sending announcement via sourceforge to all, that there's a new email list. There is no option that pre-2017 subscribers won't receive that same email, even if they're already part of the new list. Potential legal issue: Do you have the consent, that allows you to switch the pre-2017 subscribers to new service?
**Solution 3:**
?
Concern:
- discussion in devel list will be split between 2 lists until everyone participating switched to the new one, or if this issue is mitigated by bridging the lists (could be as simple as coping the digest of the daily mails into the other list with a link to read them in the browser)https://code.briarproject.org/briar/briar/-/issues/1924After switching language, "sign out" dialog button doesn't appear to work2021-11-04T11:03:24ZakwizgranAfter switching language, "sign out" dialog button doesn't appear to workAfter changing the app language in the Briar settings screen, a dialog is shown prompting the user to sign out. On the Samsung Galaxy Ace 2 (Android 4.1.2) the "sign out" button dismisses the dialog and brings the contact list to the for...After changing the app language in the Briar settings screen, a dialog is shown prompting the user to sign out. On the Samsung Galaxy Ace 2 (Android 4.1.2) the "sign out" button dismisses the dialog and brings the contact list to the foreground. The UI remains visible and usable for about 15 seconds and then disappears when sign out completes.
Ideally the UI should be hidden immediately and if the app's relaunched it should show the "signing out" fragment, as happens when the "sign out" menu option is used.Android 1.4SebastianSebastian