briar issueshttps://code.briarproject.org/briar/briar/-/issues2019-10-28T12:16:31Zhttps://code.briarproject.org/briar/briar/-/issues/1405When emoji drawer is open, clicking text field should show keyboard2019-10-28T12:16:31ZakwizgranWhen emoji drawer is open, clicking text field should show keyboard* Android version: 8.0.0
* Briar version: 1.0.13
* Phone model: Sony Xperia X Compact
* User feedback: "Sony X compact, Android 8.0, BlackBerry Keyboard, Briar-master with new emoji. In conversation click on emoji icon -> open BB Keyboar...* Android version: 8.0.0
* Briar version: 1.0.13
* Phone model: Sony Xperia X Compact
* User feedback: "Sony X compact, Android 8.0, BlackBerry Keyboard, Briar-master with new emoji. In conversation click on emoji icon -> open BB Keyboard and emoji drawer (not side by side, BB is open behind emoji drawer) -> click on Type message and do nothing (expect show keyboard)."
I'm assuming "click on Type message" means click on the keyboard icon next to the text field. The soft keyboard should be shown in this case, even if there's a custom keyboard app. But possibly the user expects that clicking on the text field itself should hide the emoji drawer and show the keyboard again?Android 1.2Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1399IllegalArgumentException after stopping UnlockActivity2022-06-13T14:54:58ZakwizgranIllegalArgumentException after stopping UnlockActivity* Android version: 8.1.0
* Briar version: 1.1.1 (9476782)
* Phone model: Xiaomi Mi A1 (tissot)
* User feedback: "Blank screen."
Stacktrace:
```
java.lang.IllegalArgumentException: View=DecorView@47d51c6[] not attached to window manager
...* Android version: 8.1.0
* Briar version: 1.1.1 (9476782)
* Phone model: Xiaomi Mi A1 (tissot)
* User feedback: "Blank screen."
Stacktrace:
```
java.lang.IllegalArgumentException: View=DecorView@47d51c6[] not attached to window manager
at android.view.WindowManagerGlobal.findViewLocked(WindowManagerGlobal.java:485)
at android.view.WindowManagerGlobal.updateViewLayout(WindowManagerGlobal.java:380)
at android.view.WindowManagerImpl.updateViewLayout(WindowManagerImpl.java:101)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3728)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1650)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:172)
at android.app.ActivityThread.main(ActivityThread.java:6590)
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)
```
The log seems to show navigation between screens with BriarRecyclerViews leading up to the crash:
```
09-25 14:23:10.402 I/RenewableWakeLock: Acquiring wake lock LocationManagerService
09-25 14:23:10.402 I/RenewableWakeLock: Already acquired
09-25 14:23:35.872 I/Poller: Polling plugin org.briarproject.bramble.tor
09-25 14:23:56.187 I/BriarRecyclerView: Adding Handler Callback
09-25 14:23:56.238 I/BriarRecyclerView: Removing Handler Callback
09-25 14:23:56.310 I/BriarRecyclerView: Adding Handler Callback
09-25 14:23:56.554 I/BriarRecyclerView: Removing Handler Callback
09-25 14:23:58.197 I/BriarRecyclerView: Adding Handler Callback
09-25 14:24:01.792 I/BriarRecyclerView: Removing Handler Callback
09-25 14:24:03.169 I/RenewableWakeLock: Renewing wake lock LocationManagerService
09-25 14:24:03.841 I/BriarRecyclerView: Adding Handler Callback
```
Judging by the short stacktrace, this looks like a platform bug without a place where we could insert a workaround. Therefore I'm not adding this to the current milestone unless we get more reports.Android 1.2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1395IllegalStateException when hiding UI due to low memory2018-10-08T12:03:31ZakwizgranIllegalStateException when hiding UI due to low memory* Android version: 8.1.0
* Briar version: 1.1.1 (9476782)
* Phone model: Xiaomi Mi A1 (tissot)
Stacktrace:
```
java.lang.RuntimeException: Unable to stop activity {org.briarproject.briar.android/org.briarproject.briar.android.logout.Hid...* Android version: 8.1.0
* Briar version: 1.1.1 (9476782)
* Phone model: Xiaomi Mi A1 (tissot)
Stacktrace:
```
java.lang.RuntimeException: Unable to stop activity {org.briarproject.briar.android/org.briarproject.briar.android.logout.HideUiActivity}: java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity.
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:4369)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:4425)
at android.app.ActivityThread.-wrap5(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1661)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:172)
at android.app.ActivityThread.main(ActivityThread.java:6590)
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.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity.
at android.support.v7.app.AppCompatDelegateImplV9.createSubDecor(AppCompatDelegateImplV9.java:354)
at android.support.v7.app.AppCompatDelegateImplV9.ensureSubDecor(AppCompatDelegateImplV9.java:323)
at android.support.v7.app.AppCompatDelegateImplV9.initWindowDecorActionBar(AppCompatDelegateImplV9.java:175)
at android.support.v7.app.AppCompatDelegateImplBase.getSupportActionBar(AppCompatDelegateImplBase.java:145)
at android.support.v7.app.AppCompatDelegateImplV9.onStop(AppCompatDelegateImplV9.java:259)
at android.support.v7.app.AppCompatDelegateImplV14.onStop(AppCompatDelegateImplV14.java:131)
at android.support.v7.app.AppCompatActivity.onStop(AppCompatActivity.java:184)
at org.briarproject.briar.android.activity.BaseActivity.onStop(BaseActivity.java:128)
at android.app.Instrumentation.callActivityOnStop(Instrumentation.java:1376)
at android.app.Activity.performStop(Activity.java:7205)
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:4364)
... 9 more
java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity.
at android.support.v7.app.AppCompatDelegateImplV9.createSubDecor(AppCompatDelegateImplV9.java:354)
at android.support.v7.app.AppCompatDelegateImplV9.ensureSubDecor(AppCompatDelegateImplV9.java:323)
at android.support.v7.app.AppCompatDelegateImplV9.initWindowDecorActionBar(AppCompatDelegateImplV9.java:175)
at android.support.v7.app.AppCompatDelegateImplBase.getSupportActionBar(AppCompatDelegateImplBase.java:145)
at android.support.v7.app.AppCompatDelegateImplV9.onStop(AppCompatDelegateImplV9.java:259)
at android.support.v7.app.AppCompatDelegateImplV14.onStop(AppCompatDelegateImplV14.java:131)
at android.support.v7.app.AppCompatActivity.onStop(AppCompatActivity.java:184)
at org.briarproject.briar.android.activity.BaseActivity.onStop(BaseActivity.java:128)
at android.app.Instrumentation.callActivityOnStop(Instrumentation.java:1376)
at android.app.Activity.performStop(Activity.java:7205)
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:4364)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:4425)
at android.app.ActivityThread.-wrap5(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1661)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:172)
at android.app.ActivityThread.main(ActivityThread.java:6590)
at java.lang.reflect.Method.invoke(Native Method)
at android.app.ActivityThread.-wrap5(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1661)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:172)
at android.app.ActivityThread.main(ActivityThread.java:6590)
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.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity.
at android.support.v7.app.AppCompatDelegateImplV9.createSubDecor(AppCompatDelegateImplV9.java:354)
at android.support.v7.app.AppCompatDelegateImplV9.ensureSubDecor(AppCompatDelegateImplV9.java:323)
at android.support.v7.app.AppCompatDelegateImplV9.initWindowDecorActionBar(AppCompatDelegateImplV9.java:175)
at android.support.v7.app.AppCompatDelegateImplBase.getSupportActionBar(AppCompatDelegateImplBase.java:145)
at android.support.v7.app.AppCompatDelegateImplV9.onStop(AppCompatDelegateImplV9.java:259)
at android.support.v7.app.AppCompatDelegateImplV14.onStop(AppCompatDelegateImplV14.java:131)
at android.support.v7.app.AppCompatActivity.onStop(AppCompatActivity.java:184)
at org.briarproject.briar.android.activity.BaseActivity.onStop(BaseActivity.java:128)
at android.app.Instrumentation.callActivityOnStop(Instrumentation.java:1376)
at android.app.Activity.performStop(Activity.java:7205)
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:4364)
... 9 more
java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity.
at android.support.v7.app.AppCompatDelegateImplV9.createSubDecor(AppCompatDelegateImplV9.java:354)
at android.support.v7.app.AppCompatDelegateImplV9.ensureSubDecor(AppCompatDelegateImplV9.java:323)
at android.support.v7.app.AppCompatDelegateImplV9.initWindowDecorActionBar(AppCompatDelegateImplV9.java:175)
at android.support.v7.app.AppCompatDelegateImplBase.getSupportActionBar(AppCompatDelegateImplBase.java:145)
at android.support.v7.app.AppCompatDelegateImplV9.onStop(AppCompatDelegateImplV9.java:259)
at android.support.v7.app.AppCompatDelegateImplV14.onStop(AppCompatDelegateImplV14.java:131)
at android.support.v7.app.AppCompatActivity.onStop(AppCompatActivity.java:184)
at org.briarproject.briar.android.activity.BaseActivity.onStop(BaseActivity.java:128)
at android.app.Instrumentation.callActivityOnStop(Instrumentation.java:1376)
at android.app.Activity.performStop(Activity.java:7205)
at android.app.ActivityThread.performDestroyActivity(ActivityThread.java:4364)
at android.app.ActivityThread.handleDestroyActivity(ActivityThread.java:4425)
at android.app.ActivityThread.-wrap5(Unknown Source:0)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1661)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:172)
at android.app.ActivityThread.main(ActivityThread.java:6590)
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 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1393Error page is shown when trying to install Ripple from Google Play2019-06-12T10:45:27ZakwizgranError page is shown when trying to install Ripple from Google PlayWhen no panic button app is installed, touching the "Panic Button App" preference automatically opens a market:// link to install Ripple. If the device has Google Play but not F-Droid, a Play Store error page is shown. This may be confus...When no panic button app is installed, touching the "Panic Button App" preference automatically opens a market:// link to install Ripple. If the device has Google Play but not F-Droid, a Play Store error page is shown. This may be confusing for the user, as we haven't given any indication that we're about to search for an app on Google Play.
If the device has both Google Play and F-Droid, an app chooser is shown. Choosing Google Play leads to the error page.
![device-2018-09-28-110048](/uploads/5eb85f3d601c31b661f9071d70638c20/device-2018-09-28-110048.png)Android 1.1https://code.briarproject.org/briar/briar/-/issues/1392List of panic button apps isn't updated after installing app2019-02-21T10:34:00ZakwizgranList of panic button apps isn't updated after installing appSteps to reproduce:
* Uninstall Ripple
* Start Briar
* Go to "Settings > Panic button setup > Panic Button App"
* A dialog opens showing "None" as the only choice
* An app chooser opens to install Ripple (if you only have one market app...Steps to reproduce:
* Uninstall Ripple
* Start Briar
* Go to "Settings > Panic button setup > Panic Button App"
* A dialog opens showing "None" as the only choice
* An app chooser opens to install Ripple (if you only have one market app, perhaps it opens automatically?)
* Install Ripple from F-Droid
* Press back to return to Briar
* Expected:
* The dialog has closed
* Pressing "Panic Button App" again shows a list that includes Ripple
* Pressing "Panic Button App" again doesn't open the app chooser to install Ripple again
* Actual:
* The dialog is still open showing "None" as the only choice
* Pressing "Panic Button App" again shows a list with "None" as the only choice
* Pressing "Panic Button App" again opens the app chooser to install Ripple againAndroid 1.1akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1391Layout issues with author view on Android 4.0.42018-09-28T09:48:57ZakwizgranLayout issues with author view on Android 4.0.4There seem to be some problems with the author layout on the Sony Xperia Tipo (Android 4.0.4):
![device-2018-09-26-173540](/uploads/08c9d86a38c69feacd229d1428c43f5f/device-2018-09-26-173540.png)
![device-2018-09-26-175901](/uploads/cd4...There seem to be some problems with the author layout on the Sony Xperia Tipo (Android 4.0.4):
![device-2018-09-26-173540](/uploads/08c9d86a38c69feacd229d1428c43f5f/device-2018-09-26-173540.png)
![device-2018-09-26-175901](/uploads/cd43908e618a05c10cf1725a58508f8e/device-2018-09-26-175901.png)Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1390PasswordActivity is shown after backing out of crash report, can't back out o...2019-06-18T16:51:50ZakwizgranPasswordActivity is shown after backing out of crash report, can't back out of PasswordActivitySteps to reproduce:
* Sign into Briar (debug build)
* Go to Settings > Crash
* Choose "Send Report"
* Back out of the report creation screen
* Expected behaviour: Return to home screen
* Actual behaviour: PasswordActivity is shown
* Pre...Steps to reproduce:
* Sign into Briar (debug build)
* Go to Settings > Crash
* Choose "Send Report"
* Back out of the report creation screen
* Expected behaviour: Return to home screen
* Actual behaviour: PasswordActivity is shown
* Press back button
* Expected behaviour: Return to home screen
* Actual behaviour: PasswordActivity remains visible (or maybe another instance immediately appears?)Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1389Shadows are missing below system message bubbles2018-11-15T11:38:59ZakwizgranShadows are missing below system message bubblesThe shadows below system message bubbles are rendered wrongly on the Moto G 4G (Android 5.1):
![device-2018-09-26-173458](/uploads/b049831c8e5ff944dbf6b68b89381e63/device-2018-09-26-173458.png)The shadows below system message bubbles are rendered wrongly on the Moto G 4G (Android 5.1):
![device-2018-09-26-173458](/uploads/b049831c8e5ff944dbf6b68b89381e63/device-2018-09-26-173458.png)Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1386App locks after signing out2018-09-20T11:06:10ZTorsten GroteApp locks after signing outThe app inactivity timeout even kicks in after signing out.
Steps to reproduce:
* activate app lock in settings
* set timeout to 1 minute
* sign out
* wait for one minute
* observe the new locked notification that you can only remove by...The app inactivity timeout even kicks in after signing out.
Steps to reproduce:
* activate app lock in settings
* set timeout to 1 minute
* sign out
* wait for one minute
* observe the new locked notification that you can only remove by signing in againAndroid 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1385Link in error message for adding contacts doesn't cover entire word2019-02-21T10:34:00ZakwizgranLink in error message for adding contacts doesn't cover entire wordLooks like there's an off-by-one error in the code that turns "send feedback" into a link:
![device-2018-09-19-165301](/uploads/179050fb18775c1832076056acf8cf93/device-2018-09-19-165301.png)Looks like there's an off-by-one error in the code that turns "send feedback" into a link:
![device-2018-09-19-165301](/uploads/179050fb18775c1832076056acf8cf93/device-2018-09-19-165301.png)Android 1.1https://code.briarproject.org/briar/briar/-/issues/1382Update links in F-Droid repo2018-11-16T13:04:07ZakwizgranUpdate links in F-Droid repoThe source code and issue tracker links in the F-Droid repo still point to the old project path, akwizgran/briar.The source code and issue tracker links in the F-Droid repo still point to the old project path, akwizgran/briar.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1380Test Panic Account Deletion2019-03-19T14:17:05ZTorsten GroteTest Panic Account DeletionWhen deleting the account while the Briar Lifecycle isn't stopped, weird things happened. We should test that deleting an account in this situation works as expected and maybe stop the lifecycle before deletion, if it doesn't.
Reference...When deleting the account while the Briar Lifecycle isn't stopped, weird things happened. We should test that deleting an account in this situation works as expected and maybe stop the lifecycle before deletion, if it doesn't.
Reference https://code.briarproject.org/briar/briar/merge_requests/910#note_30939Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1379StartupFailureActivity shows wrong error message2018-09-14T13:21:11ZakwizgranStartupFailureActivity shows wrong error messageWhen the database fails to open and returns DB_ERROR, StartupFailureActivity shows the message for DATA_TOO_OLD_ERROR, which gives the wrong description of the problem.When the database fails to open and returns DB_ERROR, StartupFailureActivity shows the message for DATA_TOO_OLD_ERROR, which gives the wrong description of the problem.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1377Separate UI tests from screenshot tests2018-10-01T13:41:29ZakwizgranSeparate UI tests from screenshot testsWe can use build flavours to separate the UI tests from the screenshot tests (which are written as Espresso tests, but are used to produce screenshots rather than test behaviour). This will allow us to run the UI and screenshot tests sep...We can use build flavours to separate the UI tests from the screenshot tests (which are written as Espresso tests, but are used to produce screenshots rather than test behaviour). This will allow us to run the UI and screenshot tests separately for #1375 and #1376.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1371Recreate code_cache directory after deleting account2020-11-16T10:37:11ZakwizgranRecreate code_cache directory after deleting accountWe already recreate the `cache` directory after deleting the account because some OpenGL drivers expect it to exist. Apparently we should do the same for the `code_cache` directory. This comes from a Sony Xperia Z3 Compact (Android 6.0.1...We already recreate the `cache` directory after deleting the account because some OpenGL drivers expect it to exist. Apparently we should do the same for the `code_cache` directory. This comes from a Sony Xperia Z3 Compact (Android 6.0.1):
```
08-30 00:33:24.161 E/libEGL (14478): error creating cache file /data/user/0/org.briarproject.briar.android.debug/code_cache/com.android.opengl.shaders_cache: No such file or directory (2)
```Android 1.2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1370Reblogging a reblogged blog post sometimes triggers a notification2019-03-19T10:36:27ZJulian DehmReblogging a reblogged blog post sometimes triggers a notificationWhen reblogging an already reblogged post the blog post is opened in a dedicated fragment and from there it can be reblogged. Clicking send will take you back to the originally reblogged post and not to the feed itself. Therefore a notif...When reblogging an already reblogged post the blog post is opened in a dedicated fragment and from there it can be reblogged. Clicking send will take you back to the originally reblogged post and not to the feed itself. Therefore a notification is triggered.
Steps to reproduce:
1. Create a blog post
2. Reblog the blog post with a message
3. Reblog the reblogged postAndroid 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1369Private group layout is confusing2019-05-16T14:54:46ZakwizgranPrivate group layout is confusing"Group chat is extremely confusing with the names of the users below the messages.""Group chat is extremely confusing with the names of the users below the messages."Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1367DB Store header is corrupt2020-03-10T15:03:16ZTorsten GroteDB Store header is corruptWhen using Android emulator 27.3.9.0 with an API 28 Google APIs Intel x86 Atom System Image Revision 4 or 5, creating a new account after "forgetting the password" causes a `org.h2.jdbc.JdbcSQLException: Encryption error in file null` ex...When using Android emulator 27.3.9.0 with an API 28 Google APIs Intel x86 Atom System Image Revision 4 or 5, creating a new account after "forgetting the password" causes a `org.h2.jdbc.JdbcSQLException: Encryption error in file null` exception when reinstalling with Android Studio while still signed in.
```
I/AndroidAccountManager: No database key in preferences
I/AccountManagerImpl: Found database key in primary file
I/AndroidAccountManager: No database key in preferences
I/AccountManagerImpl: Found database key in primary file
I/BriarService: Created
I/LifecycleManagerImpl: Starting services
W/LifecycleManagerImpl: org.briarproject.bramble.api.db.DbException: org.h2.jdbc.JdbcSQLException: Encryption error in file null [90049-192]
org.briarproject.bramble.api.db.DbException: org.h2.jdbc.JdbcSQLException: Encryption error in file null [90049-192]
at org.briarproject.bramble.db.JdbcDatabase.startTransaction(JdbcDatabase.java:495)
at org.briarproject.bramble.db.JdbcDatabase.open(JdbcDatabase.java:340)
at org.briarproject.bramble.db.H2Database.open(H2Database.java:54)
at org.briarproject.bramble.db.DatabaseComponentImpl.open(DatabaseComponentImpl.java:109)
at org.briarproject.bramble.lifecycle.LifecycleManagerImpl.startServices(LifecycleManagerImpl.java:108)
at org.briarproject.briar.android.BriarService.lambda$onCreate$0$BriarService(BriarService.java:134)
at org.briarproject.briar.android.BriarService$$Lambda$0.run(Unknown Source:20)
at java.lang.Thread.run(Thread.java:764)
Caused by: org.h2.jdbc.JdbcSQLException: Encryption error in file null [90049-192]
at org.h2.mvstore.db.MVTableEngine$Store.convertIllegalStateException(MVTableEngine.java:182)
at org.h2.mvstore.db.MVTableEngine$Store.open(MVTableEngine.java:167)
at org.h2.mvstore.db.MVTableEngine.init(MVTableEngine.java:99)
at org.h2.engine.Database.getPageStore(Database.java:2463)
at org.h2.engine.Database.open(Database.java:692)
at org.h2.engine.Database.openDatabase(Database.java:270)
at org.h2.engine.Database.<init>(Database.java:264)
at org.h2.engine.Engine.openSession(Engine.java:64)
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:349)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:118)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:102)
at org.h2.Driver.connect(Driver.java:72)
at java.sql.DriverManager.getConnection(DriverManager.java:569)
at java.sql.DriverManager.getConnection(DriverManager.java:191)
at org.briarproject.bramble.db.H2Database.createConnection(H2Database.java:101)
at org.briarproject.bramble.db.JdbcDatabase.startTransaction(JdbcDatabase.java:484)
at org.briarproject.bramble.db.JdbcDatabase.open(JdbcDatabase.java:340)
at org.briarproject.bramble.db.H2Database.open(H2Database.java:54)
at org.briarproject.bramble.db.DatabaseComponentImpl.open(DatabaseComponentImpl.java:109)
at org.briarproject.bramble.lifecycle.LifecycleManagerImpl.startServices(LifecycleManagerImpl.java:108)
at org.briarproject.briar.android.BriarService.lambda$onCreate$0$BriarService(BriarService.java:134)
at org.briarproject.briar.android.BriarService$$Lambda$0.run(Unknown Source:20)
at java.lang.Thread.run(Thread.java:764)
Caused by: java.lang.IllegalStateException: Store header is corrupt: split:30:/data/data/org.briarproject.briar.android.debug/app_db/db.mv.db [1.4.192/6]
at org.h2.mvstore.DataUtils.newIllegalStateException(DataUtils.java:773)
at org.h2.mvstore.MVStore.readStoreHeader(MVStore.java:605)
at org.h2.mvstore.MVStore.<init>(MVStore.java:355)
at org.h2.mvstore.MVStore$Builder.open(MVStore.java:2893)
at org.h2.mvstore.db.MVTableEngine$Store.open(MVTableEngine.java:154)
at org.h2.mvstore.db.MVTableEngine.init(MVTableEngine.java:99)
at org.h2.engine.Database.getPageStore(Database.java:2463)
at org.h2.engine.Database.open(Database.java:692)
at org.h2.engine.Database.openDatabase(Database.java:270)
at org.h2.engine.Database.<init>(Database.java:264)
at org.h2.engine.Engine.openSession(Engine.java:64)
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:349)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:118)
at org.h2.jdbc.JdbcConnection.<init>(JdbcConnection.java:102)
at org.h2.Driver.connect(Driver.java:72)
at java.sql.DriverManager.getConnection(DriverManager.java:569)
at java.sql.DriverManager.getConnection(DriverManager.java:191)
at org.briarproject.bramble.db.H2Database.createConnection(H2Database.java:101)
at org.briarproject.bramble.db.JdbcDatabase.startTransaction(JdbcDatabase.java:484)
at org.briarproject.bramble.db.JdbcDatabase.open(JdbcDatabase.java:340)
at org.briarproject.bramble.db.H2Database.open(H2Database.java:54)
at org.briarproject.bramble.db.DatabaseComponentImpl.open(DatabaseComponentImpl.java:109)
at org.briarproject.bramble.lifecycle.LifecycleManagerImpl.startServices(LifecycleManagerImpl.java:108)
at org.briarproject.briar.android.BriarService.lambda$onCreate$0$BriarService(BriarService.java:134)
at org.briarproject.briar.android.BriarService$$Lambda$0.run(Unknown Source:20)
at java.lang.Thread.run(Thread.java:764)
W/BriarService: Startup failed: DB_ERROR
```Android 1.2akwizgranakwizgranhttps://code.briarproject.org/briar/briar/-/issues/1360Resource changes aren't included in builds2018-08-09T08:59:25ZakwizgranResource changes aren't included in buildsSince we added build flavours, changes to resources aren't included in Android Studio builds (I haven't tested command-line builds yet). Cleaning and rebuilding causes the changes to be picked up.Since we added build flavours, changes to resources aren't included in Android Studio builds (I haven't tested command-line builds yet). Cleaning and rebuilding causes the changes to be picked up.Android 1.1Torsten GroteTorsten Grotehttps://code.briarproject.org/briar/briar/-/issues/1358New Design and UX for Message Bubbles2018-08-20T19:47:36ZElio Qoshielio@ura.designNew Design and UX for Message BubblesWhile working on the Dark Theme with @grote we discovered that the message bubble colors required changes made to PNG drawables, split into 9 pieces (for dark, light, incoming, outgoing and system notices). This makes it quite rough to w...While working on the Dark Theme with @grote we discovered that the message bubble colors required changes made to PNG drawables, split into 9 pieces (for dark, light, incoming, outgoing and system notices). This makes it quite rough to work with and is time consuming when it comes to updating changes. Also, the current design is an old message bubble pattern and one can see from Facebook or Telegram that a more rounded approach might be more suitable:
![image](/uploads/59dd7e30bf3126a0e36e9fdbb6e91c9b/image.png)Android 1.1Torsten GroteTorsten Grote