briar issueshttps://code.briarproject.org/briar/briar/-/issues2017-12-18T07:40:22Zhttps://code.briarproject.org/briar/briar/-/issues/903Tor crashing on Android 7 after first run2017-12-18T07:40:22ZJulian DehmTor crashing on Android 7 after first runAfter the first run of briar (if a tor circuit was established), almost any subsequent run crashes tor / libc for me. This happens both on my Lineage 14.1 phone and the emulator (with sdk 25).
Here's the log (I added the function name...After the first run of briar (if a tor circuit was established), almost any subsequent run crashes tor / libc for me. This happens both on my Lineage 14.1 phone and the emulator (with sdk 25).
Here's the log (I added the function names in french quotation marks for the tor binary in the backtrace (the last column)) :
````
LineageOS Version: '14.1-20170225-UNOFFICIAL-i9305'
Build fingerprint: 'samsung/m3xx/m3:4.4.4/KTU84P/I9305XXUFPB1:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 9222, tid: 9222, name: tor >>> /data/user/0/org.briarproject.briar/app_tor/tor <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4f4f4ad8
r0 befff748 r1 58b517d0 r2 410ec1c0 r3 befff754
r4 befff754 r5 4f4f4ad8 r6 00003918 r7 40e40500
r8 00000000 r9 00000000 sl 00000000 fp befff744
ip 4018f85c sp befff6e8 lr 401523c7 pc 40153bb8 cpsr 200f0030
d0 74657320746f6e20 d1 0000000000000000
d2 0000000000000000 d3 0000000000000000
d4 52414d4d55532072 d5 656e6e6f43223d59
d6 6f7420676e697463 d7 726f542065687420
d8 0000000000000000 d9 0000000000000000
d10 0000000000000000 d11 0000000000000000
d12 0000000000000000 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
d16 0000000000000000 d17 0000000000000000
d18 0000000001f66130 d19 0000000001881b68
d20 0000000000000000 d21 0000000000000000
d22 0000000000000000 d23 0000000000000000
d24 3f36c051b8f0af77 d25 3fa0842100000000
d26 3fdb6db6db6fabff d27 0000000000000000
d28 0000000000000000 d29 0000000000000000
d30 0000000000000000 d31 0000000000000000
scr 80000010
backtrace:
03-01 13:17:37.145 5444-5444/? A/DEBUG: #00 pc 0004cbb8 /system/lib/libc.so (timesub+35)
03-01 13:17:37.145 5444-5444/? A/DEBUG: #01 pc 0004b3c3 /system/lib/libc.so (gmtime_r+22)
03-01 13:17:37.145 5444-5444/? A/DEBUG: #02 pc 001fe300 /data/data/org.briarproject.briar/app_tor/tor <gmtime_r@plt>
03-01 13:17:37.145 5444-5444/? A/DEBUG: #03 pc 00212794 /data/data/org.briarproject.briar/app_tor/tor <tor_gmtime_r>
03-01 13:17:37.145 5444-5444/? A/DEBUG: #04 pc 0007d3f0 /data/data/org.briarproject.briar/app_tor/tor <format_iso_time>
03-01 13:17:37.145 5444-5444/? A/DEBUG: #05 pc 0007ebe8 /data/data/org.briarproject.briar/app_tor/tor <dump_microdescriptor>
03-01 13:17:37.145 5444-5444/? A/DEBUG: #06 pc 0007e3a0 /data/data/org.briarproject.briar/app_tor/tor <microdesc_cache_rebuild>
03-01 13:17:37.145 5444-5444/? A/DEBUG: #07 pc 0007d5e4 /data/data/org.briarproject.briar/app_tor/tor <get_microdesc_cache>
03-01 13:17:37.145 5444-5444/? A/DEBUG: #08 pc 000886ac /data/data/org.briarproject.briar/app_tor/tor <get_microdesc_cache>
03-01 13:17:37.145 5444-5444/? A/DEBUG: #09 pc 0008527c /data/data/org.briarproject.briar/app_tor/tor <nodelist_set_consensus>
03-01 13:17:37.145 5444-5444/? A/DEBUG: #10 pc 000804b0 /data/data/org.briarproject.briar/app_tor/tor <networkstatus_set_current_consensus>
03-01 13:17:37.145 5444-5444/? A/DEBUG: #11 pc 00076db8 /data/data/org.briarproject.briar/app_tor/tor <router_reload_consensus_>
03-01 13:17:37.145 5444-5444/? A/DEBUG: #12 pc 0007c3b4 /data/data/org.briarproject.briar/app_tor/tor <do_main_loop>
03-01 13:17:37.145 5444-5444/? A/DEBUG: #13 pc 000713b8 /data/data/org.briarproject.briar/app_tor/tor <tor_main>
03-01 13:17:37.145 5444-5444/? A/DEBUG: #14 pc 00016ca1 /system/lib/libc.so (__libc_init+48)
03-01 13:17:37.145 5444-5444/? A/DEBUG: #15 pc 00071358 /data/data/org.briarproject.briar/app_tor/tor <libc_init>
````
I also uploaded a tombstone https://code.briarproject.org/goapunk/briar/raw/fileStorage/tombstone_00.
Steps to reproduce:
1. Install and run Briar
2. Wait until tor established a circuit
3. Log out / Close Briar
4. Start Briar
5. Check the log (don't filter for Briar, check the unfiltered logcat)
Once tor crashed you need to close Briar through settings->apps->briar-> force closeMilestone GJulian DehmJulian Dehmhttps://code.briarproject.org/briar/briar/-/issues/893Introduction can fail if pressing ACCEPT two times2017-12-18T07:40:22ZTorsten GroteIntroduction can fail if pressing ACCEPT two timesWhen a phone is to slow to update the invitation message, and the user impatiently presses ACCEPT again, the introduction gets aborted:
```
01-04 11:24:17.048 I/IntroduceeEngine: Sending accept response in state AWAIT_RESPONSES
01-04 11...When a phone is to slow to update the invitation message, and the user impatiently presses ACCEPT again, the introduction gets aborted:
```
01-04 11:24:17.048 I/IntroduceeEngine: Sending accept response in state AWAIT_RESPONSES
01-04 11:24:17.048 I/IntroduceeEngine: Moving on to state AWAIT_REMOTE_RESPONSE
01-04 11:24:17.118 I/MessageQueueManagerImpl: Sending message with position 7
01-04 11:24:17.438 I/ConversationActivity: Marking read took 19 ms
01-04 11:24:17.878 I/DuplexOutgoingSession: Generated offer: true
01-04 11:24:17.878 I/DuplexOutgoingSession: Sent offer
01-04 11:24:18.348 I/ConversationActivity: Loading messages took 462 ms
01-04 11:24:18.428 I/DuplexOutgoingSession: Generated request: true
01-04 11:24:18.428 I/DuplexOutgoingSession: Sent request
01-04 11:24:18.438 W/ConnectionManagerImpl: java.net.SocketTimeoutException
java.net.SocketTimeoutException
at java.net.PlainSocketImpl.read(PlainSocketImpl.java:491)
at java.net.PlainSocketImpl.access$000(PlainSocketImpl.java:46)
at java.net.PlainSocketImpl$PlainSocketInputStream.read(PlainSocketImpl.java:240)
at org.briarproject.bramble.crypto.StreamDecrypterImpl.readFrame(StreamDecrypterImpl.java:70)
at org.briarproject.bramble.transport.StreamReaderImpl.readFrame(StreamReaderImpl.java:63)
at org.briarproject.bramble.transport.StreamReaderImpl.read(StreamReaderImpl.java:51)
at org.briarproject.bramble.sync.RecordReaderImpl.readRecord(RecordReaderImpl.java:59)
at org.briarproject.bramble.sync.RecordReaderImpl.eof(RecordReaderImpl.java:100)
at org.briarproject.bramble.sync.IncomingSession.run(IncomingSession.java:65)
at org.briarproject.bramble.plugin.ConnectionManagerImpl$ManageIncomingDuplexConnection.run(ConnectionManagerImpl.java:278)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
at java.lang.Thread.run(Thread.java:856)
01-04 11:24:18.438 I/ConnectionRegistryImpl: Incoming connection unregistered: org.briarproject.bramble.tor
01-04 11:24:18.438 I/ConnectionRegistryImpl: Contact disconnected
01-04 11:24:19.298 I/DuplexOutgoingSession: Generated offer: false
01-04 11:24:19.438 I/DuplexOutgoingSession: Generated request: false
01-04 11:24:19.618 W/IntroduceeEngine: Error: Invalid action in state AWAIT_REMOTE_RESPONSE
01-04 11:24:19.618 W/IntroduceeEngine: Aborting protocol session in state AWAIT_REMOTE_RESPONSE
```Milestone GTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/891Introduction requests/responses never get ACKed2017-12-18T07:40:22ZTorsten GroteIntroduction requests/responses never get ACKedIt looks like that in private conversations all messages except actual private messages, never get ACKed. There is only ever one checkbox for forum/blog and introduction messages even if the message has been delivered on the other end. L...It looks like that in private conversations all messages except actual private messages, never get ACKed. There is only ever one checkbox for forum/blog and introduction messages even if the message has been delivered on the other end. Leaving and re-entering the conversation doesn't help.
```
01-03 16:36:03.864 I/DuplexOutgoingSession: Generated ack: true
01-03 16:36:03.864 I/DuplexOutgoingSession: Sent ack
01-03 16:36:03.914 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:03.964 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.024 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.024 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.404 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.444 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.504 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.504 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.504 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.504 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.504 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.504 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.514 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.514 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.514 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.514 I/DuplexOutgoingSession: Generated ack: false
01-03 16:36:04.964 I/ConversationActivity: Messages sent
01-03 16:36:04.964 I/DuplexOutgoingSession: Generated batch: true
01-03 16:36:04.984 I/DuplexOutgoingSession: Sent batch
01-03 16:36:05.454 I/DuplexOutgoingSession: Generated batch: false
01-03 16:36:05.994 I/ConversationActivity: Messages acked
```Milestone GTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/885Lan transport properties can exceed the maximum length.2017-12-18T07:40:22ZJulian DehmLan transport properties can exceed the maximum length.The ipPort field used in the lan plugin contains a list of recent IP:port pairs which can hold up to 5 IPs. Each entry is about 11-21 chars long and therefore the overall size can exceed the `MAX_PROPERTY_LENGTH` of 100 (e.g. 21 * 5 =...The ipPort field used in the lan plugin contains a list of recent IP:port pairs which can hold up to 5 IPs. Each entry is about 11-21 chars long and therefore the overall size can exceed the `MAX_PROPERTY_LENGTH` of 100 (e.g. 21 * 5 = 105). Once the limit is reached contact exchanges always fail:
`12-29 15:00:51.233 3748-5490/org.briarproject.briar W/ContactExchangeTaskImpl: org.briarproject.bramble.api.FormatException
org.briarproject.bramble.api.FormatException at org.briarproject.bramble.data.BdfReaderImpl.readString(BdfReaderImpl.java:257) at
org.briarproject.bramble.contact.ContactExchangeTaskImpl.receiveTransportProperties(ContactExchangeTaskImpl.java:292) at
org.briarproject.bramble.contact.ContactExchangeTaskImpl.run(ContactExchangeTaskImpl.java:174)`Milestone GJulian DehmJulian Dehmhttps://code.briarproject.org/briar/briar/-/issues/884ConversationItems sometimes not displayed or loaded properly2018-11-20T17:35:26ZJulian DehmConversationItems sometimes not displayed or loaded properlyWhen opening a conversation sometimes incoming messages are not displayed properly.
The size of the "box" holding the message changes randomly, sometimes it's too small (cutting most or even all of it's content), sometimes it's too b...When opening a conversation sometimes incoming messages are not displayed properly.
The size of the "box" holding the message changes randomly, sometimes it's too small (cutting most or even all of it's content), sometimes it's too big. The same message was displayed with different wrong sizes.
Examples:
1. The frame is too big (there is **no** newline or anything - I had this one also with the complete content cut)
<img src="https://code.briarproject.org/goapunk/briar/raw/fileStorage/screens/884/conversationItem1.png" width="15%" height="15%" >
2. Part of the message cut because the frame is too small
<img src="https://code.briarproject.org/goapunk/briar/raw/fileStorage/screens/884/conversationItem2.png" width="15%" height="15%" >
3. Part of the messages cut
<img src="https://code.briarproject.org/goapunk/briar/raw/fileStorage/screens/884/conversationItem3a.png" width="15%" height="15%" >
4. Messages from 3 shown correctly
<img src="https://code.briarproject.org/goapunk/briar/raw/fileStorage/screens/884/conversationItem3b.png" width="15%" height="15%" >
(I removed everything else from the images out of privacy reasons)
If you scroll the incorrect item out of view and back in it's being displayed correctly.
Steps to reproduce:
1. Enter a conversation
2. Lock and unlock screen repeatedly until you find a bugged incoming message.Milestone GJulian DehmJulian Dehmhttps://code.briarproject.org/briar/briar/-/issues/829Create new launcher icon2017-12-18T07:40:24ZTorsten GroteCreate new launcher iconThe current launcher icon (on the left) is difficult to recognize:
![device-2016-12-13-134037](/uploads/84db532df3821ad74ba57719f0763b7b/device-2016-12-13-134037.png)
There, this ticket is about designing a new launcher icon based ...The current launcher icon (on the left) is difficult to recognize:
![device-2016-12-13-134037](/uploads/84db532df3821ad74ba57719f0763b7b/device-2016-12-13-134037.png)
There, this ticket is about designing a new launcher icon based on the new vector logo we have that adheres to the latest material design specs.Milestone GTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/144User testing sessions2018-06-12T11:32:37ZakwizgranUser testing sessionsTwo user testing sessions for Milestone G -- findings to be documented in the issue tracker.Two user testing sessions for Milestone G -- findings to be documented in the issue tracker.Milestone Ghttps://code.briarproject.org/briar/briar/-/issues/143Co-ordinate translations before 1.0 release2018-06-12T11:32:37ZakwizgranCo-ordinate translations before 1.0 releaseMilestone GTorsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/142Co-ordinate with OTF security audit2018-06-12T11:32:37ZakwizgranCo-ordinate with OTF security auditMilestone Gakwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/982Crash when creating parent stack on Android 4.0.42017-08-01T16:58:38ZakwizgranCrash when creating parent stack on Android 4.0.4The Sony Xperia Tipo (Android 4.0.4) crashed with the following stacktrace when a blog invitation was received:
```
07-14 10:41:01.999 3782-3782/org.briarproject.briar.beta E/ACRA: ACRA caught a IllegalArgumentException for org.briarpro...The Sony Xperia Tipo (Android 4.0.4) crashed with the following stacktrace when a blog invitation was received:
```
07-14 10:41:01.999 3782-3782/org.briarproject.briar.beta E/ACRA: ACRA caught a IllegalArgumentException for org.briarproject.briar.beta
java.lang.IllegalArgumentException: android.content.pm.PackageManager$NameNotFoundException: ComponentInfo{org.briarproject.briar.beta/org.briarproject.briar.beta.android.navdrawer.NavDrawerActivity}
at android.support.v4.app.TaskStackBuilder.addParentStack(TaskStackBuilder.java:247)
at android.support.v4.app.TaskStackBuilder.addParentStack(TaskStackBuilder.java:226)
at org.briarproject.briar.android.AndroidNotificationManagerImpl.updateContactNotification(AndroidNotificationManagerImpl.java:315)
at org.briarproject.briar.android.AndroidNotificationManagerImpl.access$1200(AndroidNotificationManagerImpl.java:78)
at org.briarproject.briar.android.AndroidNotificationManagerImpl$3.run(AndroidNotificationManagerImpl.java:268)
at android.os.Handler.handleCallback(Handler.java:605)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4424)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:817)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:584)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.content.pm.PackageManager$NameNotFoundException: ComponentInfo{org.briarproject.briar.beta/org.briarproject.briar.beta.android.navdrawer.NavDrawerActivity}
at android.app.ApplicationPackageManager.getActivityInfo(ApplicationPackageManager.java:223)
at android.support.v4.app.NavUtils.getParentActivityName(NavUtils.java:301)
at android.support.v4.app.NavUtils.getParentActivityIntent(NavUtils.java:262)
at android.support.v4.app.TaskStackBuilder.addParentStack(TaskStackBuilder.java:240)
at android.support.v4.app.TaskStackBuilder.addParentStack(TaskStackBuilder.java:226)
at org.briarproject.briar.android.AndroidNotificationManagerImpl.updateContactNotification(AndroidNotificationManagerImpl.java:315)
at org.briarproject.briar.android.AndroidNotificationManagerImpl.access$1200(AndroidNotificationManagerImpl.java:78)
at org.briarproject.briar.android.AndroidNotificationManagerImpl$3.run(AndroidNotificationManagerImpl.java:268)
at android.os.Handler.handleCallback(Handler.java:605)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4424)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
```
It makes sense to get a `NameNotFoundException` for `org.briarproject.briar.beta.android.navdrawer.NavDrawerActivity` because the package name is wrong - it should be `org.briarproject.briar.android.navdrawer.NavDrawerActivity` (without the `beta`). So it looks like this crash could be related to setting the package name in `build.gradle`.Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/979Removing contact fails after sharing blog2017-07-21T10:27:48ZakwizgranRemoving contact fails after sharing blogAfter sharing an RSS blog with a contact, both users get the following exception when trying to remove the contact:
```
07-07 17:46:07.045 7863-7923/org.briarproject.briar.beta W/ConversationActivity: org.briarproject.bramble.api.db.DbE...After sharing an RSS blog with a contact, both users get the following exception when trying to remove the contact:
```
07-07 17:46:07.045 7863-7923/org.briarproject.briar.beta W/ConversationActivity: org.briarproject.bramble.api.db.DbException
org.briarproject.bramble.api.db.DbException
at org.briarproject.briar.sharing.SharingManagerImpl.getSession(SharingManagerImpl.java:161)
at org.briarproject.briar.sharing.SharingManagerImpl.removingShareable(SharingManagerImpl.java:451)
at org.briarproject.briar.sharing.BlogSharingManagerImpl.removingBlog(BlogSharingManagerImpl.java:70)
at org.briarproject.briar.blog.BlogManagerImpl.removeBlog(BlogManagerImpl.java:224)
at org.briarproject.briar.blog.BlogManagerImpl.removingContact(BlogManagerImpl.java:119)
at org.briarproject.bramble.contact.ContactManagerImpl.removeContact(ContactManagerImpl.java:175)
at org.briarproject.bramble.contact.ContactManagerImpl.removeContact(ContactManagerImpl.java:137)
at org.briarproject.briar.android.contact.ConversationActivity$19.run(ConversationActivity.java:810)
at org.briarproject.briar.android.controller.DbControllerImpl$1.run(DbControllerImpl.java:37)
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 is on the 977-crash-when-opening-rss-blog branch with freshly created accounts.Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/977Crash when opening a blog2017-07-07T17:43:18ZakwizgranCrash when opening a blogAn anonymous user reported the following crash with Briar 0.13-alpha8 (an old build, so it may be fixed already):
```
java.lang.IllegalArgumentException
at org.briarproject.briar.sharing.SharingManagerImpl.respondToInvitation(Sh...An anonymous user reported the following crash with Briar 0.13-alpha8 (an old build, so it may be fixed already):
```
java.lang.IllegalArgumentException
at org.briarproject.briar.sharing.SharingManagerImpl.respondToInvitation(SharingManagerImpl.java:271)
at org.briarproject.briar.android.contact.ConversationActivity.respondToBlogRequest(ConversationActivity.java:1030)
at org.briarproject.briar.android.contact.ConversationActivity.access$3100(ConversationActivity.java:118)
at org.briarproject.briar.android.contact.ConversationActivity$26.run(ConversationActivity.java:969)
at org.briarproject.briar.android.controller.DbControllerImpl$1.run(DbControllerImpl.java:37)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:761)
```
"Crashed opening a Briar blog (RSS repost) shared via chat."
Android 7.1.2, Briar commit ID 7929ba9.Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/968H2 crashes on Android 4.0.42017-07-03T14:20:22ZakwizgranH2 crashes on Android 4.0.4Briar fails to start on the Sony Xperia Tipo (Android 4.0.4) because H2 crashes with the following stacktrace:
```
06-30 09:51:48.069 2888-3099/org.briarproject.briar E/ACRA: ACRA caught a NoClassDefFoundError for org.briarproject.briar
...Briar fails to start on the Sony Xperia Tipo (Android 4.0.4) because H2 crashes with the following stacktrace:
```
06-30 09:51:48.069 2888-3099/org.briarproject.briar E/ACRA: ACRA caught a NoClassDefFoundError for org.briarproject.briar
java.lang.NoClassDefFoundError: java.util.concurrent.ThreadLocalRandom
at org.h2.util.MathUtils.randomBytes(MathUtils.java:290)
at org.h2.engine.User.setUserPasswordHash(User.java:71)
at org.h2.engine.Engine.openSession(Engine.java:72)
at org.h2.engine.Engine.openSession(Engine.java:176)
at org.h2.engine.Engine.createSessionAndValidate(Engine.java:154)
at org.h2.engine.Engine.createSession(Engine.java:137)
at org.h2.engine.Engine.createSession(Engine.java:27)
at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:354)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:116)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:100)
at org.h2.Driver.connect(Driver.java:69)
at java.sql.DriverManager.getConnection(DriverManager.java:175)
at org.briarproject.bramble.db.H2Database.createConnection(H2Database.java:93)
at org.briarproject.bramble.db.JdbcDatabase.startTransaction(JdbcDatabase.java:364)
at org.briarproject.bramble.db.JdbcDatabase.open(JdbcDatabase.java:271)
at org.briarproject.bramble.db.H2Database.open(H2Database.java:46)
at org.briarproject.bramble.db.DatabaseComponentImpl.open(DatabaseComponentImpl.java:117)
at org.briarproject.bramble.lifecycle.LifecycleManagerImpl.startServices(LifecycleManagerImpl.java:122)
at org.briarproject.briar.android.BriarService$1.run(BriarService.java:98)
```
It looks like the recent H2 upgrade has introduce a dependency on a newer version of Java.Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/966Sharing contact's blog fails with DbException2017-07-07T14:23:49ZakwizgranSharing contact's blog fails with DbExceptionLooks like this may have the same cause as #962.
```
06-01 02:02:06.140 25336-25418/org.briarproject.briar W/tSelectorControllerImpl: org.briarproject.bramble.api.db.DbException
org.briarproject.bramble.api.db.DbException
at...Looks like this may have the same cause as #962.
```
06-01 02:02:06.140 25336-25418/org.briarproject.briar W/tSelectorControllerImpl: org.briarproject.bramble.api.db.DbException
org.briarproject.bramble.api.db.DbException
at org.briarproject.briar.sharing.SharingManagerImpl.getSession(SharingManagerImpl.java:162)
at org.briarproject.briar.sharing.SharingManagerImpl.canBeShared(SharingManagerImpl.java:433)
at org.briarproject.briar.sharing.SharingManagerImpl.canBeShared(SharingManagerImpl.java:420)
at org.briarproject.briar.android.sharing.ShareBlogControllerImpl.isDisabled(ShareBlogControllerImpl.java:54)
at org.briarproject.briar.android.contactselection.ContactSelectorControllerImpl$1.run(ContactSelectorControllerImpl.java:54)
at org.briarproject.briar.android.controller.DbControllerImpl$1.run(DbControllerImpl.java:37)
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 Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/962Removing contact fails with DbException2017-07-04T15:19:30ZakwizgranRemoving contact fails with DbExceptionWith a fresh install of Briar, I added and removed a contact. Removing the contact succeeded on one device, but failed repeatedly on the other device with the following exception:
```
05-31 18:13:01.426 2390-2584/org.briarproject.briar ...With a fresh install of Briar, I added and removed a contact. Removing the contact succeeded on one device, but failed repeatedly on the other device with the following exception:
```
05-31 18:13:01.426 2390-2584/org.briarproject.briar W/ConversationActivity: org.briarproject.bramble.api.db.DbException
org.briarproject.bramble.api.db.DbException
at org.briarproject.briar.sharing.SharingManagerImpl.getSession(SharingManagerImpl.java:162)
at org.briarproject.briar.sharing.SharingManagerImpl.removingShareable(SharingManagerImpl.java:453)
at org.briarproject.briar.sharing.BlogSharingManagerImpl.removingBlog(BlogSharingManagerImpl.java:70)
at org.briarproject.briar.blog.BlogManagerImpl.removeBlog(BlogManagerImpl.java:224)
at org.briarproject.briar.blog.BlogManagerImpl.removingContact(BlogManagerImpl.java:119)
at org.briarproject.bramble.contact.ContactManagerImpl.removeContact(ContactManagerImpl.java:175)
at org.briarproject.bramble.contact.ContactManagerImpl.removeContact(ContactManagerImpl.java:137)
at org.briarproject.briar.android.contact.ConversationActivity$19.run(ConversationActivity.java:810)
at org.briarproject.briar.android.controller.DbControllerImpl$1.run(DbControllerImpl.java:37)
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)
```
From the stacktrace, it looks like more than one session has somehow been created for sharing the contact's blog. (I didn't share the blog manually.)Android Beta 1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/957Importing RSS feed case-sensitivity2017-07-04T15:10:19ZErnir ErlingssonImporting RSS feed case-sensitivityHad a test user who was unable to import an RSS feed, the button always stayed disabled. Turned out to be a case issue, we're only accepting lower-case but at the same time we're capping the first letter of the URL..Had a test user who was unable to import an RSS feed, the button always stayed disabled. Turned out to be a case issue, we're only accepting lower-case but at the same time we're capping the first letter of the URL..Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/956Tap protection UX problems2017-07-03T11:10:08ZErnir ErlingssonTap protection UX problemsThe current UX of the tap protection isn't good enough
***Test 1***
Three "regular" users: None of the users had a IT/CS background but all were familiar with Apps and their smartphones.
* All users were left insecure about the...The current UX of the tap protection isn't good enough
***Test 1***
Three "regular" users: None of the users had a IT/CS background but all were familiar with Apps and their smartphones.
* All users were left insecure about their devices security after reading the pop-up (all users got pop-ups, I've actually not seen a device yet that doesn't have at least one app which appears on the list.). Some wondered if they should even use Briar at all due to a security breach of their device.
* One user didn't recognise all the apps listed despite all of the being safe (I checked). This made the user very insecure about his phone's general security, got questions like "Did someone install something on my phone without my knowledge ?", "Do I need to virus scan my phone?", "Does this mean I shouldn't use Briar ?"
* Two testers weren't aware that it was even possible for other apps to steal taps and had to be educated in what this means exactly.
***Test 2***
Three software developers
* All three were a bit confused about the meaning (all three read it in German). All three understood roughly what it was about in the end but it was not smooth and the final understanding varied quite a bit.
* One user thought Briar was warning against screen-shot copying (the german text actually doesn't say "tap" anywhere, only "overlaying apps".
* One user felt that Briar had scanned his phone without permission to display the list of overlaying apps.
* All three wondered if the security risk really warranted such a dominating UI response from Briar and one suggested a warning triangle you could press for more information.
***End result***
We need re-design this on the UX level, we also need to bear in mind the variation in how security conscious the users are. I feel we should split this into basic information, which is always displayed, and advanced information when user requests it. I also felt the warning triangle idea was a good one.Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/954NPE: showNewScreenFilterWarning2017-06-30T12:21:59ZTorsten GroteNPE: showNewScreenFilterWarningI got this strange crash in the log:
```
05-19 12:04:13.178 I/ActivityManager: START u0 {flg=0x14000000 cmp=org.briarproject.unofficial/org.briarproject.briar.android.navdrawer.NavDrawerActivity (has extras)} from uid 10104 on display ...I got this strange crash in the log:
```
05-19 12:04:13.178 I/ActivityManager: START u0 {flg=0x14000000 cmp=org.briarproject.unofficial/org.briarproject.briar.android.navdrawer.NavDrawerActivity (has extras)} from uid 10104 on display 0
05-19 12:04:13.210 I/art: System.exit called, status: 0
05-19 12:04:13.210 I/AndroidRuntime: VM exiting with result code 0, cleanup skipped.
05-19 12:04:13.333 W/InputDispatcher: channel '9fb7829 org.briarproject.unofficial/org.briarproject.briar.android.navdrawer.NavDrawerActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9
05-19 12:04:13.333 E/InputDispatcher: channel '9fb7829 org.briarproject.unofficial/org.briarproject.briar.android.navdrawer.NavDrawerActivity (server)' ~ Channel is unrecoverably broken and will be disposed!
05-19 12:04:13.334 D/GraphicsStats: Buffer count: 23
05-19 12:04:13.334 I/WindowManager: WIN DEATH: Window{9fb7829 u0 org.briarproject.unofficial/org.briarproject.briar.android.navdrawer.NavDrawerActivity}
05-19 12:04:13.335 I/ActivityManager: Process org.briarproject.unofficial (pid 22636) has died
05-19 12:04:13.335 D/ActivityManager: cleanUpApplicationRecord -- 22636
```Android Beta 1Julian DehmJulian Dehmhttps://code.briarproject.org/briar/briar/-/issues/951Remove visibility indicators from private group join messages2017-07-04T15:10:19ZakwizgranRemove visibility indicators from private group join messagesThis is an experiment to see if we can reduce the confusion about revealing contacts by not exposing this feature until the user navigates to the reveal contacts screen, where we can show onboarding.
Related to #801, #854.This is an experiment to see if we can reduce the confusion about revealing contacts by not exposing this feature until the user navigates to the reveal contacts screen, where we can show onboarding.
Related to #801, #854.Android Beta 1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/948ArrayIndexOutOfBoundsException in VectorDrawable on Startup2017-06-09T19:25:50ZTorsten GroteArrayIndexOutOfBoundsException in VectorDrawable on StartupRight after Briar starts, it crashes on an GT-I9515L running Android 5.0.1 with this trace:
![804206593_51066](/uploads/c03850ad83619206fc77e4ca68cdb772/804206593_51066.jpg)Right after Briar starts, it crashes on an GT-I9515L running Android 5.0.1 with this trace:
![804206593_51066](/uploads/c03850ad83619206fc77e4ca68cdb772/804206593_51066.jpg)Android Beta 1Torsten GroteTorsten Grote