AssertionError: Already have a database key

Android version: 5.1.1
Briar version: 1.1.5 (8f4c3c45)
Phone model: Smartfren Andromax B16C2H

Log:

02-01 21:43:52.743 I/CameraView: Releasing camera
02-01 21:43:52.882 I/CameraView: Surface destroyed
02-01 21:43:53.956 I/BaseActivity: Starting NavDrawerActivity
02-01 21:43:54.138 I/BaseActivity: Stopping ContactExchangeActivity
02-01 21:44:13.750 I/BaseActivity: Starting SettingsActivity
02-01 21:44:16.276 I/BaseActivity: Stopping NavDrawerActivity
02-01 21:45:25.374 I/BaseActivity: Starting NavDrawerActivity
02-01 21:45:25.556 I/BaseActivity: Stopping SettingsActivity
02-01 21:45:26.976 I/BaseActivity: Starting SetupActivity
02-01 21:45:27.134 I/BaseActivity: Stopping NavDrawerActivity
02-01 21:45:42.017 I/SetupControllerImpl: Creating account

Stacktrace:

java.lang.AssertionError: Already have a database key
        at org.briarproject.bramble.account.AccountManagerImpl.createAccount(AccountManagerImpl.java:163)
        at org.briarproject.briar.android.login.SetupControllerImpl.lambda$createAccount$0(SetupControllerImpl.java:101)
        at org.briarproject.briar.android.login.-$$Lambda$SetupControllerImpl$u65UGqVCiIKOcwdlXIj7schCrSA.run(lambda)
        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 this could be related to previous bugs where SetupActivity reappears after setup is complete, or somehow appears in a session where setup didn't even take place (#1189 (closed), #1327 (closed), #1396 (closed)). The log here shows that the user navigated from ContactExchangeActivity -> NavDrawerActivity -> SettingsActivity -> NavDrawerActivity -> SetupActivity. Unfortunately the log isn't long enough to show whether setup occurred in this session.