[BUG] We hit a snag! (Realm File Decryption Failure Causing App Startup Error)

[bphd]

Describe the bug A clear and concise description of what the bug is. Open

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
5. open

Expected behavior A clear and concise description of what you expected to happen. Main apm

Screenshots If applicable, add screenshots to help explain your problem.

Device info(please complete the following information):

• Device: [e.g. iPhone6]
• OS: [ROM and version, ie Havoc-OS 4.12]
• App Version [e.g. 22]

Additional context Add any other context about the problem here. Stacktrace: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.fox2code.mmm/com.fox2code.mmm.MainActivity}: io.realm.exceptions.RealmFileException: Failed to open Realm file at path '/data/user/0/com.fox2code.mmm/realms/ReposList.realm': Realm file decryption failed (Decryption failed: 'unable to decrypt after 0 seconds (retry_count=4 from=i != bytes_read size=4096)') (/data/user/0/com.fox2code.mmm/realms/ReposList.realm) in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107 Kind: ACCESS_ERROR. at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4166) at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:4312) at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:101) at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:135) at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:95) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2571) at android.os.Handler.dispatchMessage(Handler.java:106) at android.os.Looper.loopOnce(Looper.java:226) at android.os.Looper.loop(Looper.java:313) at android.app.ActivityThread.main(ActivityThread.java:8741) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067) Caused by: io.realm.exceptions.RealmFileException: Failed to open Realm file at path '/data/user/0/com.fox2code.mmm/realms/ReposList.realm': Realm file decryption failed (Decryption failed: 'unable to decrypt after 0 seconds (retry_count=4 from=i != bytes_read size=4096)') (/data/user/0/com.fox2code.mmm/realms/ReposList.realm) in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107 Kind: ACCESS_ERROR. at io.realm.internal.OsSharedRealm.nativeGetSharedRealm(Native Method) at io.realm.internal.OsSharedRealm.(SourceFile:11) at io.realm.internal.OsSharedRealm.getInstance(SourceFile:6) at hg.(SourceFile:18) at lf1.(SourceFile:8) at vf1.b(SourceFile:96) at lf1.l0(SourceFile:5) at com.fox2code.mmm.MainActivity.onCreate(SourceFile:77) at android.app.Activity.performCreate(Activity.java:8578) at android.app.Activity.performCreate(Activity.java:8557) at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1384) at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4147) ... 12 more

[bphd]

I experience the same as #28, just have 2 more lines, an unknown one and at android.os.Looper.loopOnce(Looper.java:226)

You have to install signed (CRC32: 03957E94), not release (CRC32: 2E82BDD7). I've heard about problem about data/cache/app traces, so maybe deep clean or even a full uninstall if it doesn't work solely with update. Dev should name that fix 2.1.2 to differentiate further and update it to GitHub release, not just their website. Even if it's one bit modified, as long as it corrects a major problem impeaching the app from running, it deserves a version update

[androidacy-user]

I experience the same as #28, just have 2 more lines, an unknown one and at android.os.Looper.loopOnce(Looper.java:226)

You have to install signed (CRC32: 03957E94), not release (CRC32: 2E82BDD7). I've heard about problem about data/cache/app traces, so maybe deep clean or even a full uninstall if it doesn't work solely with update. Dev should name that fix 2.1.2 to differentiate further and update it to GitHub release, not just their website. Even if it's one bit modified, as long as it corrects a major problem impeaching the app from running, it deserves a version update

We're not in a position codebase wise to do a new release, and we're already planning one in the coming days. We chose the rather unusual emergency rerelease path as this issue was critical enough to need to be patched immediately.

Creating another release for a single commit never pushed to GitHub doesn't even make sense from our standpoint as the in app updater isn't reachable for users that encountered this issue, and we feel it would create confusion as to what the update includes (it does not include any newer code on GitHub nor does it bump version or version code).

[androidacy-user]

Locking this issue so it doesn't continue to be spammed. Please see our statement above for questions.