briar issueshttps://code.briarproject.org/groups/briar/-/issues2017-12-18T07:40:26Zhttps://code.briarproject.org/briar/briar/-/issues/799Who can see user's content is unclear2017-12-18T07:40:26ZTorsten GroteWho can see user's content is unclearDuring a testing session (#788), users asked whether their blog is public. It turned out, they didn't know about how public their content is in the various features and who can see it.
They didn't know that
* all their contacts get thei...During a testing session (#788), users asked whether their blog is public. It turned out, they didn't know about how public their content is in the various features and who can see it.
They didn't know that
* all their contacts get their blog posts
* their contacts can share their blogs with people they don't know
* forums can be shared with everybody and also strangers
* only the group's creator can invite other membersAndroid Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/796Unclear what RSS Import will do2017-12-18T07:40:26ZTorsten GroteUnclear what RSS Import will doDuring a testing session (#788), a user found the RSS import feature, liked it and started to import a feed. However, the user was very surprised to find lots of RSS entries posted to their personal blog and shared with all contacts auto...During a testing session (#788), a user found the RSS import feature, liked it and started to import a feed. However, the user was very surprised to find lots of RSS entries posted to their personal blog and shared with all contacts automatically. The expectation of the user was that the RSS feed is only imported for the user alone. Automatic publishing was not expected.Android Beta 1https://code.briarproject.org/briar/briar/-/issues/787Blog: Tap on name opens individual blog while being open already2017-12-18T07:40:26ZMegaloxBlog: Tap on name opens individual blog while being open alreadyIf I'm in the individual blog of a user the tap on her name opens her individual blog again and again (with a slide animation). Shouldn't it simply do nothing?
I made a recording:
![device-2016-11-30-110230](/uploads/54d5db04cf7e5af9...If I'm in the individual blog of a user the tap on her name opens her individual blog again and again (with a slide animation). Shouldn't it simply do nothing?
I made a recording:
![device-2016-11-30-110230](/uploads/54d5db04cf7e5af939eb030ce015d993/device-2016-11-30-110230.mp4)Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1229Crash when creating account after rotating screen2018-06-14T17:17:13ZakwizgranCrash when creating account after rotating screenSteps to reproduce:
* Create a new account and press 'Create Account'
* Before the next screen is shown, rotate the screen to landscape
* Rotate the screen back to portrait
* Press 'Create Account' again
Stacktrace:
```
java.lang.Il...Steps to reproduce:
* Create a new account and press 'Create Account'
* Before the next screen is shown, rotate the screen to landscape
* Rotate the screen back to portrait
* Press 'Create Account' again
Stacktrace:
```
java.lang.IllegalStateException
at org.briarproject.briar.android.login.SetupControllerImpl.createAccount(SetupControllerImpl.java:88)
at org.briarproject.briar.android.login.SetupControllerImpl.createAccount(SetupControllerImpl.java:82)
at org.briarproject.briar.android.login.SetupControllerImpl.showDozeOrCreateAccount(SetupControllerImpl.java:67)
at org.briarproject.briar.android.login.PasswordFragment.onClick(PasswordFragment.java:117)
at android.view.View.performClick(View.java:6294)
at android.view.View$PerformClick.run(View.java:24770)
at android.os.Handler.handleCallback(Handler.java:790)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6494)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
```
There are really two bugs here:
* The username and password aren't passed from the old SetupControllerImpl instance to the new one
* The result of the first account creation is returned to the old SetupActivity instance
The second bug is covered by #725, so this ticket is just for the first bug.Android 1.0akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1217DbStateException when getting status for message in invisible group2018-05-10T08:37:10ZakwizgranDbStateException when getting status for message in invisible groupI got this exception when opening a conversation with a fake test data contact.
The likely cause is that the contact has never sent any client version updates, so the contact group is invisible and therefore no status rows exist. It's p...I got this exception when opening a conversation with a fake test data contact.
The likely cause is that the contact has never sent any client version updates, so the contact group is invisible and therefore no status rows exist. It's possible for real contacts' contact groups to be invisible too, so we need to check for this instead of throwing an exception.
```
org.briarproject.bramble.api.db.DbException: org.briarproject.bramble.db.DbStateException
at org.briarproject.bramble.db.JdbcDatabase.getMessageStatus(JdbcDatabase.java:1765)
at org.briarproject.bramble.db.JdbcDatabase.getMessageStatus(JdbcDatabase.java:73)
at org.briarproject.bramble.db.DatabaseComponentImpl.getMessageStatus(DatabaseComponentImpl.java:574)
at org.briarproject.briar.introduction.IntroductionManagerImpl.getIntroductionMessages(IntroductionManagerImpl.java:416)
at org.briarproject.briar.android.contact.ConversationActivity.lambda$loadMessages$3$ConversationActivity(ConversationActivity.java:347)
at org.briarproject.briar.android.contact.ConversationActivity$$Lambda$3.run(Unknown Source)
at org.briarproject.briar.android.controller.DbControllerImpl.lambda$runOnDbThread$0$DbControllerImpl(DbControllerImpl.java:35)
at org.briarproject.briar.android.controller.DbControllerImpl$$Lambda$0.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
```Android 1.0akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1216IllegalArgumentException when creating test data with zero contacts2018-05-03T16:44:00ZakwizgranIllegalArgumentException when creating test data with zero contacts```
java.lang.IllegalArgumentException: n <= 0: 0
at java.util.Random.nextInt(Random.java:182)
at org.briarproject.briar.test.TestDataCreatorImpl.createBlogPosts(TestDataCreatorImpl.java:315)
at org.briarproject.briar.test.Te...```
java.lang.IllegalArgumentException: n <= 0: 0
at java.util.Random.nextInt(Random.java:182)
at org.briarproject.briar.test.TestDataCreatorImpl.createBlogPosts(TestDataCreatorImpl.java:315)
at org.briarproject.briar.test.TestDataCreatorImpl.createTestDataOnIoExecutor(TestDataCreatorImpl.java:135)
at org.briarproject.briar.test.TestDataCreatorImpl.lambda$createTestData$0$TestDataCreatorImpl(TestDataCreatorImpl.java:120)
at org.briarproject.briar.test.TestDataCreatorImpl$$Lambda$0.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
```Android 1.0Julian DehmJulian Dehmhttps://code.briarproject.org/briar/briar/-/issues/1213DbStateException when a connection is opened2018-04-29T15:41:17ZakwizgranDbStateException when a connection is opened@grote observed this on three phones that had been used to test the introduction protocol. In all cases the exception happened at the first connection attempt after startup. The exception was thrown for both incoming and outgoing connect...@grote observed this on three phones that had been used to test the introduction protocol. In all cases the exception happened at the first connection attempt after startup. The exception was thrown for both incoming and outgoing connections, when trying to increment the stream counter for the outgoing stream.
The exception prevents the phones from connecting, so this is a release blocker.
```
04-28 08:42:31.852 I/TcpPlugin: Connected to /192.168.1.3
04-28 08:42:31.859 W/ConnectionManagerImpl: org.briarproject.bramble.api.db.DbException: org.briarproject.bramble.db.DbStateException
org.briarproject.bramble.api.db.DbException: org.briarproject.bramble.db.DbStateException
at org.briarproject.bramble.db.JdbcDatabase.incrementStreamCounter(JdbcDatabase.java:2215)
at org.briarproject.bramble.db.JdbcDatabase.incrementStreamCounter(JdbcDatabase.java:73)
at org.briarproject.bramble.db.DatabaseComponentImpl.incrementStreamCounter(DatabaseComponentImpl.java:616)
at org.briarproject.bramble.transport.TransportKeyManagerImpl.getStreamContext(TransportKeyManagerImpl.java:314)
at org.briarproject.bramble.transport.KeyManagerImpl.getStreamContext(KeyManagerImpl.java:182)
at org.briarproject.bramble.plugin.ConnectionManagerImpl$ManageOutgoingDuplexConnection.run(ConnectionManagerImpl.java:346)
```Android 1.0akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1184RejectedExecutionException when signing out2018-03-28T11:39:16ZakwizgranRejectedExecutionException when signing outI got the following crash when signing out:
```
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@1e487d9c rejected from java.util.concurrent.ScheduledThreadPoolExe...I got the following crash when signing out:
```
java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@1e487d9c rejected from java.util.concurrent.ScheduledThreadPoolExecutor@3dcb33a5[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 2]
at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2011)
at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:793)
at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:298)
at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:503)
at java.util.concurrent.Executors$DelegatedScheduledExecutorService.schedule(Executors.java:644)
at org.briarproject.bramble.plugin.Poller.schedule(Poller.java:166)
at org.briarproject.bramble.plugin.Poller.reschedule(Poller.java:145)
at org.briarproject.bramble.plugin.Poller.eventOccurred(Poller.java:85)
at org.briarproject.bramble.event.EventBusImpl.broadcast(EventBusImpl.java:32)
at org.briarproject.bramble.plugin.ConnectionRegistryImpl.unregisterConnection(ConnectionRegistryImpl.java:94)
at org.briarproject.bramble.plugin.ConnectionManagerImpl$ManageOutgoingDuplexConnection.runIncomingSession(ConnectionManagerImpl.java:404)
at org.briarproject.bramble.plugin.ConnectionManagerImpl$ManageOutgoingDuplexConnection.bridge$lambda$0$ConnectionManagerImpl$ManageOutgoingDuplexConnection(ConnectionManagerImpl.java)
at org.briarproject.bramble.plugin.ConnectionManagerImpl$ManageOutgoingDuplexConnection$$Lambda$0.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:818)
```
Looks like unregistering a connection caused the poller to reschedule polling, which crashed because the ScheduledExecutorService had already been shut down. Our other executors are configure to discard jobs submitted after shutdown, but the ScheduledExecutorService seems to be using the default policy of throwing an exception.Android Beta 2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1181Error icon is blurry on Android 42018-03-08T15:57:48ZakwizgranError icon is blurry on Android 4Screenshot from Galaxy Nexus (Android 4.3):
![device-2018-03-08-144415](/uploads/573593a3e774ea8dc657a24c4212508d/device-2018-03-08-144415.png)
The screenshot comes from the maintenance-0.16 branch, but I think master uses the same icon.Screenshot from Galaxy Nexus (Android 4.3):
![device-2018-03-08-144415](/uploads/573593a3e774ea8dc657a24c4212508d/device-2018-03-08-144415.png)
The screenshot comes from the maintenance-0.16 branch, but I think master uses the same icon.Android Beta 2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1180Transport icons show wrong state2018-04-17T14:57:44ZakwizgranTransport icons show wrong state* Android version: 7.0
* Briar version: 0.16.18 (812522a)
* Phone model: TCL Alcatel 5085C
* User feedback: "Frequently shows my internet as offline when I have lots of 4G service."
* Mobile data status: Available, enabled, connected
* W...* Android version: 7.0
* Briar version: 0.16.18 (812522a)
* Phone model: TCL Alcatel 5085C
* User feedback: "Frequently shows my internet as offline when I have lots of 4G service."
* Mobile data status: Available, enabled, connected
* Wi-Fi address: 0.0.0.0
* Wi-Fi status: Available, not enabled, not connectedAndroid Beta 2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1177Viewfinder is blank after connection fails2018-04-23T10:44:40ZakwizgranViewfinder is blank after connection failsWhen a connection fails while adding a contact, the viewfinder is shown again but it's blank. This is a regression caused by stopping the camera preview after scanning the QR code.When a connection fails while adding a contact, the viewfinder is shown again but it's blank. This is a regression caused by stopping the camera preview after scanning the QR code.Android 1.0akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1176NPE: ScreenFilterMonitor.getApps()2018-03-08T11:33:15ZTorsten GroteNPE: ScreenFilterMonitor.getApps()When you start Briar on an outdated database, you get the notification about the database being corrupted. When you click this, you currently get this crash on `master`:
```
E/ACRA: ACRA caught a RuntimeException for org.briarproject.br...When you start Briar on an outdated database, you get the notification about the database being corrupted. When you click this, you currently get this crash on `master`:
```
E/ACRA: ACRA caught a RuntimeException for org.briarproject.briar.android.debug
java.lang.RuntimeException: Unable to start activity ComponentInfo{org.briarproject.briar.android.debug/org.briarproject.briar.android.StartupFailureActivity}: java.lang.NullPointerException: Attempt to invoke interface method 'java.util.Collection org.briarproject.briar.api.android.ScreenFilterMonitor.getApps()' on a null object reference
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2778)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2856)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1589)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6494)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
Caused by: java.lang.NullPointerException: Attempt to invoke interface method 'java.util.Collection org.briarproject.briar.api.android.ScreenFilterMonitor.getApps()' on a null object reference
at org.briarproject.briar.android.activity.BaseActivity.protectToolbar(BaseActivity.java:218)
at org.briarproject.briar.android.activity.BaseActivity.onStart(BaseActivity.java:106)
at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1334)
at android.app.Activity.performStart(Activity.java:7019)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2741)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2856)
at android.app.ActivityThread.-wrap11(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1589)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6494)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
```Android Beta 2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1174Crash when opening link from RSS post2018-03-08T11:33:15ZakwizgranCrash when opening link from RSS postI got this crash when opening a link from an RSS post, before the link warning dialog appeared.
* Android version: 4.3
* Phone model: Samsung Galaxy Nexus (yakju)
* Briar version: 0.16.18 (812522a)
Stacktrace:
```
java.lang.ClassCastEx...I got this crash when opening a link from an RSS post, before the link warning dialog appeared.
* Android version: 4.3
* Phone model: Samsung Galaxy Nexus (yakju)
* Briar version: 0.16.18 (812522a)
Stacktrace:
```
java.lang.ClassCastException: android.support.v7.widget.TintContextWrapper cannot be cast to android.support.v7.app.AppCompatActivity
at org.briarproject.briar.android.util.UiUtils$1.onClick(UiUtils.java:125)
at org.briarproject.briar.android.view.ArticleMovementMethod.onTouchEvent(ArticleMovementMethod.java:61)
at android.widget.TextView.onTouchEvent(TextView.java:7609)
at android.view.View.dispatchTouchEvent(View.java:7384)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2209)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:1952)
at com.android.internal.policy.impl.PhoneWindow$DecorView.superDispatchTouchEvent(PhoneWindow.java:1966)
at com.android.internal.policy.impl.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1418)
at android.app.Activity.dispatchTouchEvent(Activity.java:2424)
at android.support.v7.view.WindowCallbackWrapper.dispatchTouchEvent(WindowCallbackWrapper.java:68)
at android.support.v7.view.WindowCallbackWrapper.dispatchTouchEvent(WindowCallbackWrapper.java:68)
at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent(PhoneWindow.java:1914)
at android.view.View.dispatchPointerEvent(View.java:7564)
at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(ViewRootImpl.java:3883)
at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:3778)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3379)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3429)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3398)
at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:3483)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3406)
at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:3540)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3379)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:3429)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:3398)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:3406)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:3379)
at android.view.ViewRootImpl.deliverInputEvent(ViewRootImpl.java:5419)
at android.view.ViewRootImpl.doProcessInputEvents(ViewRootImpl.java:5399)
at android.view.ViewRootImpl.enqueueInputEvent(ViewRootImpl.java:5370)
at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(ViewRootImpl.java:5493)
at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:182)
at android.os.MessageQueue.nativePollOnce(Native Method)
at android.os.MessageQueue.next(MessageQueue.java:132)
at android.os.Looper.loop(Looper.java:124)
at android.app.ActivityThread.main(ActivityThread.java:5103)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:525)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
at dalvik.system.NativeStart.main(Native Method)
```Android Beta 2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1171Could not connect via wifi to phone running hotspot2018-04-23T10:44:40ZakwizgranCould not connect via wifi to phone running hotspotA user reported that when their phone was running a wifi hotspot, devices connected to the hotspot could connect to each other but not to the phone running the hotspot.
* Android version: 7.1
* Phone model: OnePlus5
* Briar version: 0.16.2A user reported that when their phone was running a wifi hotspot, devices connected to the hotspot could connect to each other but not to the phone running the hotspot.
* Android version: 7.1
* Phone model: OnePlus5
* Briar version: 0.16.2Android Beta 2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1169NPE when opening settings during failed startup2018-03-14T12:42:51ZakwizgranNPE when opening settings during failed startup* Android version: 7.1.2
* Phone model: Samsung GT-I9100
* Briar version: 0.16.17 (347c2f2)
* User feedback: "Infinite init loop after password entry in Contacts, Blogs, ... Entering Settings, Crash Report"
Stacktrace:
```
java.lang.Nul...* Android version: 7.1.2
* Phone model: Samsung GT-I9100
* Briar version: 0.16.17 (347c2f2)
* User feedback: "Infinite init loop after password entry in Contacts, Blogs, ... Entering Settings, Crash Report"
Stacktrace:
```
java.lang.NullPointerException: Attempt to invoke virtual method 'boolean org.briarproject.bramble.api.StringMap.getBoolean(java.lang.String, boolean)' on a null object reference
at org.briarproject.briar.android.settings.SettingsFragment.lambda$onCreatePreferences$0$SettingsFragment(SettingsFragment.java:151)
at org.briarproject.briar.android.settings.SettingsFragment$$Lambda$0.onPreferenceClick(Unknown Source)
at android.support.v7.preference.Preference.performClick(Preference.java:1116)
at android.support.v7.preference.Preference.performClick(Preference.java:1099)
at android.support.v7.preference.Preference$1.onClick(Preference.java:169)
at android.view.View.performClick(View.java:5637)
at android.view.View$PerformClick.run(View.java:22433)
at android.os.Handler.handleCallback(Handler.java:751)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6186)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
```
The user's comment about "infinite init loop" seems to refer to the database failing to open. The log shows `LifecycleManagerImpl` starting services at 06:52, then apparently the call to `DatabaseComponent#open()` still hasn't returned at 08:37 when the user opens the settings screen.
So we seem to have two bugs here:
* Startup failed for some reason
* SettingsFragment didn't wait for startup to complete before trying to access settings
Log extract:
```
02-16 06:52:35.663 I/ACRA (21540): ACRA is enabled for org.briarproject.briar.beta, initializing...
02-16 06:52:35.804 I/BriarApplicationImpl(21540): Created
02-16 06:52:35.904 I/CryptoComponentImpl(21540): Default SecureRandom: AndroidOpenSSL SHA1PRNG
02-16 06:52:35.985 I/CryptoComponentImpl(21540): Installed SecureRandom: LinuxPRNG SHA1PRNG
02-16 06:52:36.013 I/BriarApplicationImpl(21560): Created
02-16 06:52:36.027 I/CryptoComponentImpl(21560): Default SecureRandom: AndroidOpenSSL SHA1PRNG
02-16 06:52:36.049 I/CryptoComponentImpl(21560): Installed SecureRandom: LinuxPRNG SHA1PRNG
02-16 06:52:36.052 I/LifecycleManagerImpl(21540): Registering executor TimeLoggingExecutor
02-16 06:52:36.055 I/LifecycleManagerImpl(21540): Registering executor ThreadPoolExecutor
02-16 06:52:36.055 I/LifecycleManagerImpl(21540): Registering executor DelegatedScheduledExecutorService
02-16 06:52:36.059 I/LifecycleManagerImpl(21560): Registering executor TimeLoggingExecutor
02-16 06:52:36.059 I/LifecycleManagerImpl(21560): Registering executor ThreadPoolExecutor
02-16 06:52:36.059 I/LifecycleManagerImpl(21560): Registering executor DelegatedScheduledExecutorService
02-16 06:52:36.061 I/LifecycleManagerImpl(21540): Registering service KeyManagerImpl
02-16 06:52:36.061 I/LifecycleManagerImpl(21540): Registering executor TimeLoggingExecutor
02-16 06:52:36.064 I/LifecycleManagerImpl(21560): Registering service KeyManagerImpl
02-16 06:52:36.064 I/LifecycleManagerImpl(21540): Registering service ValidationManagerImpl
02-16 06:52:36.064 I/LifecycleManagerImpl(21560): Registering executor TimeLoggingExecutor
02-16 06:52:36.065 I/LifecycleManagerImpl(21560): Registering service ValidationManagerImpl
02-16 06:52:36.065 I/LifecycleManagerImpl(21540): Registering client TransportPropertyManagerImpl
02-16 06:52:36.065 I/LifecycleManagerImpl(21540): Registering service PluginManagerImpl
02-16 06:52:36.069 I/LifecycleManagerImpl(21540): Registering client BlogManagerImpl
02-16 06:52:36.070 I/LifecycleManagerImpl(21540): Registering client FeedManagerImpl
02-16 06:52:36.071 I/LifecycleManagerImpl(21540): Registering client GroupInvitationManagerImpl
02-16 06:52:36.071 I/LifecycleManagerImpl(21540): Registering client MessagingManagerImpl
02-16 06:52:36.072 I/LifecycleManagerImpl(21560): Registering client TransportPropertyManagerImpl
02-16 06:52:36.072 I/LifecycleManagerImpl(21560): Registering service PluginManagerImpl
02-16 06:52:36.073 I/LifecycleManagerImpl(21560): Registering client BlogManagerImpl
02-16 06:52:36.074 I/LifecycleManagerImpl(21540): Registering client ForumSharingManagerImpl
02-16 06:52:36.074 I/LifecycleManagerImpl(21560): Registering client FeedManagerImpl
02-16 06:52:36.074 I/LifecycleManagerImpl(21540): Registering client BlogSharingManagerImpl
02-16 06:52:36.074 I/LifecycleManagerImpl(21560): Registering client GroupInvitationManagerImpl
02-16 06:52:36.074 I/LifecycleManagerImpl(21560): Registering client MessagingManagerImpl
02-16 06:52:36.075 I/LifecycleManagerImpl(21560): Registering client ForumSharingManagerImpl
02-16 06:52:36.075 I/LifecycleManagerImpl(21560): Registering client BlogSharingManagerImpl
02-16 06:52:36.075 I/LifecycleManagerImpl(21540): Registering client IntroductionManagerImpl
02-16 06:52:36.082 I/LifecycleManagerImpl(21560): Registering client IntroductionManagerImpl
02-16 06:52:36.101 I/LifecycleManagerImpl(21540): Registering service AndroidNotificationManagerImpl
02-16 06:52:36.101 I/LifecycleManagerImpl(21560): Registering service AndroidNotificationManagerImpl
02-16 06:52:36.101 I/LifecycleManagerImpl(21540): Registering service NetworkUsageLogger
02-16 06:52:36.101 I/LifecycleManagerImpl(21540): Registering service DozeWatchdogImpl
02-16 06:52:36.101 I/LifecycleManagerImpl(21560): Registering service NetworkUsageLogger
02-16 06:52:36.101 I/LifecycleManagerImpl(21560): Registering service DozeWatchdogImpl
02-16 06:52:36.925 I/BriarRecyclerView(21540): Adding Handler Callback
02-16 06:52:36.994 I/TextInputLayout(21540): EditText added is not a TextInputEditText. Please switch to using that class instead.
02-16 06:52:37.744 I/BriarRecyclerView(21540): Removing Handler Callback
02-16 06:52:42.510 I/BriarRecyclerView(21540): Adding Handler Callback
02-16 06:52:42.526 I/BriarService(21540): Created
02-16 06:52:42.554 I/LifecycleManagerImpl(21540): Starting services
02-16 06:52:43.037 W/IInputConnectionWrapper(21540): finishComposingText on inactive InputConnection
02-16 06:52:45.991 I/BriarRecyclerView(21540): Removing Handler Callback
02-16 07:14:58.613 I/BriarRecyclerView(21540): Adding Handler Callback
02-16 07:15:04.718 I/BriarRecyclerView(21540): Removing Handler Callback
02-16 08:34:42.669 I/BriarRecyclerView(21540): Adding Handler Callback
02-16 08:34:54.789 I/BriarRecyclerView(21540): Removing Handler Callback
02-16 08:34:54.798 I/BriarRecyclerView(21540): Adding Handler Callback
02-16 08:35:54.856 I/BriarRecyclerView(21540): Updating Content...
02-16 08:36:54.916 I/BriarRecyclerView(21540): Updating Content...
02-16 08:37:11.963 I/BriarRecyclerView(21540): Removing Handler Callback
02-16 08:37:34.413 E/ACRA (21540): ACRA caught a NullPointerException for org.briarproject.briar.beta
```Android Beta 2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1164Bluetooth address and UUID aren't stored until contact connections are enabled2018-02-22T17:11:39ZakwizgranBluetooth address and UUID aren't stored until contact connections are enabledThe fix for #1001 caused a regression: the Bluetooth address and UUID aren't stored in the local transport properties until contact connections are enabled. This causes the following issue:
* Turn off wifi
* Start Briar with a fresh acc...The fix for #1001 caused a regression: the Bluetooth address and UUID aren't stored in the local transport properties until contact connections are enabled. This causes the following issue:
* Turn off wifi
* Start Briar with a fresh account, add a contact via Bluetooth
* Messages can be exchanged with the contact
* Sign out and back in
* Enable Bluetooth contact connections in Briar settings
* Bluetooth plugin can't connect to contact because it doesn't have contact's address or UUID
On the beta branch, which doesn't have the fix for #1001, the Bluetooth plugin connects in the last step.Android 1.0akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1154Notification light not working on some Android versions2018-03-08T15:59:19ZakwizgranNotification light not working on some Android versionsA user asked for the notification light to be supported, which should already be the case. The user was using Briar 0.16.16 on Android 7.1.2, phone model unknown.
I tested the notification light on several Android versions and it works ...A user asked for the notification light to be supported, which should already be the case. The user was using Briar 0.16.16 on Android 7.1.2, phone model unknown.
I tested the notification light on several Android versions and it works as expected up to Android 6.0.1, but it doesn't work on Android 8.1. I don't have an Android 7 device for testing.Android Beta 2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1148LAN plugin picks wrong network interface2018-02-01T17:22:44ZakwizgranLAN plugin picks wrong network interfaceDuring testing, @grote and @str4d were unable to add each other as contacts because @str4d's LAN plugin picked the wrong network interface, so although the devices were connected to the same wifi network they weren't able to connect to e...During testing, @grote and @str4d were unable to add each other as contacts because @str4d's LAN plugin picked the wrong network interface, so although the devices were connected to the same wifi network they weren't able to connect to each other.
One of the addresses was in the 10/8 range, the other was in the 192.168/16 range.Android Beta 2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1143'Screen overlay detected' error dialog wrongly appears2018-02-01T17:22:44Z-'Screen overlay detected' error dialog wrongly appears1. The 'Screen overlay detected' dialog prevents me from sending any kind of text. It claims I have multiple apps, however all of the apps listed do not have permissions.
2. After clicking 'continue', sending the message again will agai...1. The 'Screen overlay detected' dialog prevents me from sending any kind of text. It claims I have multiple apps, however all of the apps listed do not have permissions.
2. After clicking 'continue', sending the message again will again show 'Screen overlay detected'
3. The behaviour in 2. can be circumvent by clicking by shutting down the screen and activating it again.
Phone: HTCm8
Android version: 6.0
Suggestions:
Maybe you are only checking if the apps request the permission and not if they actually have it?
https://code.briarproject.org/akwizgran/briar/blob/master/briar-android/src/main/java/org/briarproject/briar/android/ScreenFilterMonitorImpl.java#L105
Thank you for your workAndroid Beta 2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1138Installing Briar from F-Droid fails2018-04-12T11:49:35ZJulian DehmInstalling Briar from F-Droid failsOn my samsung nexus (maguro), running Replicant 6.0, installing Briar via F-Droid fails with the following message:
```
Error installing Briar Beta
Failed to install due to an unknown error
```
I pulled the following from logcat:
```
E...On my samsung nexus (maguro), running Replicant 6.0, installing Briar via F-Droid fails with the following message:
```
Error installing Briar Beta
Failed to install due to an unknown error
```
I pulled the following from logcat:
```
E Installer: Permissions in APK and index.xml do not match!
E Installer: org.fdroid.fdroid.installer.ApkVerifier$ApkPermissionUnequalException: Permissions in APK and index.xml do not match!
E Installer: at org.fdroid.fdroid.installer.ApkVerifier.verifyApk(ApkVerifier.java:85)
E Installer: at org.fdroid.fdroid.installer.Installer.installPackage(Installer.java:234)
E Installer: at org.fdroid.fdroid.installer.InstallerService.onHandleIntent(InstallerService.java:77)
E Installer: at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:66)
E Installer: at android.os.Handler.dispatchMessage(Handler.java:102)
E Installer: at android.os.Looper.loop(Looper.java:148)
E Installer: at android.os.HandlerThread.run(HandlerThread.java:61)
E Installer: Falling back to AOSP DefaultInstaller!
```
This issue seems to be tracked in https://gitlab.com/fdroid/fdroidclient/issues/1139.Android Beta 2