Can not run android apps that use realm (e.g. Element) after updating to 4.5

REPRODUCIBILITY: 100%
OS VERSION: 4.5.0.16
HARDWARE: Sony XA2 and Xperia 10 II
UI LANGUAGE: Ger
REGRESSION: Yes

DESCRIPTION:

After updating to 4.5 and then updating the android app element, it does not start anymore.
It does not look like this is a specific problem of element, although it might be possible

PRECONDITIONS:

STEPS TO REPRODUCE:

  1. have android app element installed via fdroid
    0a) test element ist working
  2. update to 4.5
    1a) test element is working
  3. update app element via fdroid to version 1.5.22
  4. start app element

EXPECTED RESULT:

App does start after update

ACTUAL RESULT:

App crashes directly after start

MODIFICATIONS:

Openrepos

ADDITIONAL INFORMATION:

Further information: Android app element crashes on start (4.5 ea)

02-06 10:14:27.353  1313  1313 E libprocessgroup: Failed to make and chown /acct/uid_10040: Read-only file system
02-06 10:14:27.353  1313  1313 W Zygote  : createProcessGroup failed, kernel missing CONFIG_CGROUP_CPUACCT?
02-06 10:14:27.365  1313  1313 E im.vector.app: Not starting debugger since process cannot load the jdwp agent.
02-06 10:14:27.448  1313  1313 D NetworkSecurityConfig: Using Network Security Config from resource network_security_config debugBuild: false
02-06 10:14:27.449  1313  1313 D NetworkSecurityConfig: Using Network Security Config from resource network_security_config debugBuild: false
02-06 10:14:27.451  1313  1313 I MultiDex: VM with version 2.1.0 has multidex support
02-06 10:14:27.452  1313  1313 I MultiDex: Installing application
02-06 10:14:27.452  1313  1313 I MultiDex: VM has multidex support, MultiDex support library is disabled.
02-06 10:14:27.459  1313  1313 D org.jitsi.meet.sdk.JitsiInitializer: create
02-06 10:14:27.464  1313  1313 V fb-UnpackingSoSource: locked dso store /data/user/0/im.vector.app/lib-main
02-06 10:14:27.468  1313  1313 V fb-UnpackingSoSource: deps mismatch on deps store: regenerating
02-06 10:14:27.468  1313  1313 V fb-UnpackingSoSource: so store dirty: regenerating
02-06 10:14:27.608  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libRSSupport.so: deferring to libdir
02-06 10:14:27.609  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libbutter.so: deferring to libdir
02-06 10:14:27.609  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libc++_shared.so: deferring to libdir
02-06 10:14:27.609  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libduktape.so: deferring to libdir
02-06 10:14:27.610  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libfabricjni.so: deferring to libdir
02-06 10:14:27.610  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libfb.so: deferring to libdir
02-06 10:14:27.610  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libfbjni.so: deferring to libdir
02-06 10:14:27.610  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libfolly_futures.so: deferring to libdir
02-06 10:14:27.610  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libfolly_json.so: deferring to libdir
02-06 10:14:27.611  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libgifimage.so: deferring to libdir
02-06 10:14:27.611  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libglog.so: deferring to libdir
02-06 10:14:27.611  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libglog_init.so: deferring to libdir
02-06 10:14:27.611  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libhermes-executor-debug.so: deferring to libdir
02-06 10:14:27.611  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libhermes-executor-release.so: deferring to libdir
02-06 10:14:27.611  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libimagepipeline.so: deferring to libdir
02-06 10:14:27.612  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libjingle_peerconnection_so.so: deferring to libdir
02-06 10:14:27.612  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libjnidispatch.so: deferring to libdir
02-06 10:14:27.612  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libjsc.so: deferring to libdir
02-06 10:14:27.612  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libjscexecutor.so: deferring to libdir
02-06 10:14:27.612  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libjsi.so: deferring to libdir
02-06 10:14:27.612  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libjsijniprofiler.so: deferring to libdir
02-06 10:14:27.613  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libjsinspector.so: deferring to libdir
02-06 10:14:27.613  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/liblogger.so: deferring to libdir
02-06 10:14:27.613  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libmapbox-gl.so: deferring to libdir
02-06 10:14:27.613  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libmapbufferjni.so: deferring to libdir
02-06 10:14:27.613  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libnative-filters.so: deferring to libdir
02-06 10:14:27.613  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libnative-imagetranscoder.so: deferring to libdir
02-06 10:14:27.613  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libolm.so: deferring to libdir
02-06 10:14:27.613  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libopuscodec.so: deferring to libdir
02-06 10:14:27.615  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_codegen_rncore.so: deferring to libdir
02-06 10:14:27.615  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_config.so: deferring to libdir
02-06 10:14:27.615  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_debug.so: deferring to libdir
02-06 10:14:27.616  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_nativemodule_core.so: deferring to libdir
02-06 10:14:27.616  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_animations.so: deferring to libdir
02-06 10:14:27.616  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_attributedstring.so: deferring to libdir
02-06 10:14:27.616  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_componentregistry.so: deferring to libdir
02-06 10:14:27.616  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_core.so: deferring to libdir
02-06 10:14:27.616  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_debug.so: deferring to libdir
02-06 10:14:27.616  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_graphics.so: deferring to libdir
02-06 10:14:27.617  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_imagemanager.so: deferring to libdir
02-06 10:14:27.617  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_leakchecker.so: deferring to libdir
02-06 10:14:27.617  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_mapbuffer.so: deferring to libdir
02-06 10:14:27.617  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_mounting.so: deferring to libdir
02-06 10:14:27.617  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_runtimescheduler.so: deferring to libdir
02-06 10:14:27.617  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_scheduler.so: deferring to libdir
02-06 10:14:27.617  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_telemetry.so: deferring to libdir
02-06 10:14:27.618  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_templateprocessor.so: deferring to libdir
02-06 10:14:27.618  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_textlayoutmanager.so: deferring to libdir
02-06 10:14:27.618  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_render_uimanager.so: deferring to libdir
02-06 10:14:27.618  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreact_utils.so: deferring to libdir
02-06 10:14:27.619  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreactnativeblob.so: deferring to libdir
02-06 10:14:27.619  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreactnativejni.so: deferring to libdir
02-06 10:14:27.619  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libreactperfloggerjni.so: deferring to libdir
02-06 10:14:27.619  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/librealm-jni.so: deferring to libdir
02-06 10:14:27.619  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/librrc_image.so: deferring to libdir
02-06 10:14:27.619  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/librrc_root.so: deferring to libdir
02-06 10:14:27.619  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/librrc_text.so: deferring to libdir
02-06 10:14:27.619  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/librrc_unimplementedview.so: deferring to libdir
02-06 10:14:27.619  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/librrc_view.so: deferring to libdir
02-06 10:14:27.620  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/librsjni.so: deferring to libdir
02-06 10:14:27.620  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/librsjni_androidx.so: deferring to libdir
02-06 10:14:27.620  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libruntimeexecutor.so: deferring to libdir
02-06 10:14:27.620  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libsentry-android.so: deferring to libdir
02-06 10:14:27.620  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libsentry.so: deferring to libdir
02-06 10:14:27.620  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libturbomodulejsijni.so: deferring to libdir
02-06 10:14:27.620  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libuniffi_wysiwyg_composer.so: deferring to libdir
02-06 10:14:27.620  1313  1313 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libyoga.so: deferring to libdir
02-06 10:14:27.621  1313  1313 V fb-UnpackingSoSource: regenerating DSO store com.facebook.soloader.ApkSoSource
02-06 10:14:27.622  1313  1313 V fb-UnpackingSoSource: Finished regenerating DSO store com.facebook.soloader.ApkSoSource
02-06 10:14:27.623  1313  1313 V fb-UnpackingSoSource: starting syncer worker
02-06 10:14:27.722  1313  1313 V fb-UnpackingSoSource: releasing dso store lock for /data/user/0/im.vector.app/lib-main (from syncer thread)
02-06 10:14:27.737  1313  1313 V fb-UnpackingSoSource: not releasing dso store lock for /data/user/0/im.vector.app/lib-main (syncer thread started)
02-06 10:14:27.763  1313  1313 D Sentry  : io.sentry.auto-init read: false
02-06 10:14:27.763  1313  1313 I Sentry  : Retrieving auto-init from AndroidManifest.xml
02-06 10:14:28.223  1313  1313 E REALM_JNI: jni: ThrowingException 7, No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107, .
02-06 10:14:28.223  1313  1313 E REALM_JNI: Exception has been thrown: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-06 10:14:28.224  1313  1313 D AndroidRuntime: Shutting down VM
02-06 10:14:28.227  1313  1313 E AndroidRuntime: FATAL EXCEPTION: main
02-06 10:14:28.227  1313  1313 E AndroidRuntime: Process: im.vector.app, PID: 1313
02-06 10:14:28.227  1313  1313 E AndroidRuntime: java.lang.RuntimeException: Unable to create application im.vector.app.VectorApplication: java.lang.RuntimeException: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6717)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at android.app.ActivityThread.access$1300(ActivityThread.java:237)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:106)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:223)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:7656)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:599)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: Caused by: java.lang.RuntimeException: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at io.realm.internal.OsSharedRealm.nativeGetSharedRealm(Native Method)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at io.realm.internal.OsSharedRealm.<init>(OsSharedRealm.java:11)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at io.realm.internal.OsSharedRealm.getInstance(OsSharedRealm.java:8)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at io.realm.BaseRealm.<init>(BaseRealm.java:19)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at io.realm.Realm.<init>(Realm.java:8)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at io.realm.Realm.getInstance(Realm.java:104)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at org.matrix.android.sdk.internal.auth.db.RealmPendingSessionStore.getPendingSessionData(RealmPendingSessionStore.kt:3)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at org.matrix.android.sdk.internal.auth.DefaultAuthenticationService.<init>(DefaultAuthenticationService.kt:32)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at org.matrix.android.sdk.api.Matrix.<init>(Matrix.kt:248)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at im.vector.app.DaggerVectorApplication_HiltComponents_SingletonC$SingletonCImpl$SwitchingProvider.get(DaggerVectorApplication_HiltComponents_SingletonC.java:1696)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at dagger.internal.DoubleCheck.get(DoubleCheck.java:14)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at im.vector.app.DaggerVectorApplication_HiltComponents_SingletonC$SingletonCImpl.injectVectorApplication(DaggerVectorApplication_HiltComponents_SingletonC.java:3)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at im.vector.app.Hilt_VectorApplication.onCreate(Hilt_VectorApplication.java:17)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at im.vector.app.VectorApplication.onCreate(VectorApplication.kt:1)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1192)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6712)
02-06 10:14:28.227  1313  1313 E AndroidRuntime: 	... 8 more
02-06 10:14:28.228  1313  1313 I AlienCrashLogger: Crash logs disabled, not dumping
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: JitsiMeetUncaughtExceptionHandler FATAL ERROR
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: java.lang.RuntimeException: Unable to create application im.vector.app.VectorApplication: java.lang.RuntimeException: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6717)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.app.ActivityThread.access$1300(ActivityThread.java:237)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.os.Handler.dispatchMessage(Handler.java:106)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.os.Looper.loop(Looper.java:223)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.app.ActivityThread.main(ActivityThread.java:7656)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at java.lang.reflect.Method.invoke(Native Method)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:599)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: Caused by: java.lang.RuntimeException: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at io.realm.internal.OsSharedRealm.nativeGetSharedRealm(Native Method)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at io.realm.internal.OsSharedRealm.<init>(OsSharedRealm.java:11)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at io.realm.internal.OsSharedRealm.getInstance(OsSharedRealm.java:8)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at io.realm.BaseRealm.<init>(BaseRealm.java:19)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at io.realm.Realm.<init>(Realm.java:8)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at io.realm.Realm.getInstance(Realm.java:104)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at org.matrix.android.sdk.internal.auth.db.RealmPendingSessionStore.getPendingSessionData(RealmPendingSessionStore.kt:3)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at org.matrix.android.sdk.internal.auth.DefaultAuthenticationService.<init>(DefaultAuthenticationService.kt:32)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at org.matrix.android.sdk.api.Matrix.<init>(Matrix.kt:248)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at im.vector.app.DaggerVectorApplication_HiltComponents_SingletonC$SingletonCImpl$SwitchingProvider.get(DaggerVectorApplication_HiltComponents_SingletonC.java:1696)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at dagger.internal.DoubleCheck.get(DoubleCheck.java:14)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at im.vector.app.DaggerVectorApplication_HiltComponents_SingletonC$SingletonCImpl.injectVectorApplication(DaggerVectorApplication_HiltComponents_SingletonC.java:3)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at im.vector.app.Hilt_VectorApplication.onCreate(Hilt_VectorApplication.java:17)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at im.vector.app.VectorApplication.onCreate(VectorApplication.kt:1)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1192)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6712)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	... 8 more
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: java.lang.RuntimeException: Unable to create application im.vector.app.VectorApplication: java.lang.RuntimeException: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6717)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.app.ActivityThread.access$1300(ActivityThread.java:237)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.os.Handler.dispatchMessage(Handler.java:106)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.os.Looper.loop(Looper.java:223)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.app.ActivityThread.main(ActivityThread.java:7656)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at java.lang.reflect.Method.invoke(Native Method)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:599)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: Caused by: java.lang.RuntimeException: No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at io.realm.internal.OsSharedRealm.nativeGetSharedRealm(Native Method)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at io.realm.internal.OsSharedRealm.<init>(OsSharedRealm.java:11)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at io.realm.internal.OsSharedRealm.getInstance(OsSharedRealm.java:8)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at io.realm.BaseRealm.<init>(BaseRealm.java:19)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at io.realm.Realm.<init>(Realm.java:8)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at io.realm.Realm.getInstance(Realm.java:104)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at org.matrix.android.sdk.internal.auth.db.RealmPendingSessionStore.getPendingSessionData(RealmPendingSessionStore.kt:3)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at org.matrix.android.sdk.internal.auth.DefaultAuthenticationService.<init>(DefaultAuthenticationService.kt:32)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at org.matrix.android.sdk.api.Matrix.<init>(Matrix.kt:248)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at im.vector.app.DaggerVectorApplication_HiltComponents_SingletonC$SingletonCImpl$SwitchingProvider.get(DaggerVectorApplication_HiltComponents_SingletonC.java:1696)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at dagger.internal.DoubleCheck.get(DoubleCheck.java:14)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at im.vector.app.DaggerVectorApplication_HiltComponents_SingletonC$SingletonCImpl.injectVectorApplication(DaggerVectorApplication_HiltComponents_SingletonC.java:3)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at im.vector.app.Hilt_VectorApplication.onCreate(Hilt_VectorApplication.java:17)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at im.vector.app.VectorApplication.onCreate(VectorApplication.kt:1)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1192)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6712)
02-06 10:14:28.230  1313  1313 E JitsiMeetSDK: 	... 8 more
02-06 10:14:28.314  1313  1313 I Process : Sending signal. PID: 1313 SIG: 9
4 Likes

What I understood so far. It seems, that the jni binding of realm can not initialize because it does not find cpp files.
Installing from other sources/older versions, deleting and reinstalling, does not seem to help

1 Like

I have element 1.5.22 installed and working fine. Installed via playstore (opengapps).
What command did you use to get the logs? Maybe we can find some useful differences.

I followed Collect Logs with Logcat | Sailfish OS Documentation

export MYHOME=$(pwd)
devel-su
appsupport-attach /system/bin/logcat > $MYHOME/elementcrash.log

Then i filtered the logs for the processid

1 Like

I have the same init but it starts diverging when you get this error:

02-06 10:14:28.223  1313  1313 E REALM_JNI: jni: ThrowingException 7, No such file or directory in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107,

So, yeah, it’s looking for a file it cannot find. Sorry I don’t think I can be of more help.

1 Like

Not saying that this will fix it - I don’t have the Elements app - but I had crashes happending with the Taxi EU app. For me it was an issue an outdated FakeStore installation:

Maybe that helps here as well?

1 Like

I can confirm same issue with Element crashing.

Xperia 10 II, OS VERSION: 4.5.0.16

  • no MircroG or other compatibility layers

After the update, Element worked, but started crashing after updating it from F-Droid

I have tried uninstalling, downgrading to an earlier version and also tried installing from Aurora Store.

Still crashes on start.

2 Likes

I would guess as much since it works on my end with the real PlayStore. But in that case the responsibility would fall upon Element itself for depending on the Store.

Could be related: SFOS 4.5 feedback thread - #232 by goverton

related: Best matrix client for Sailfish? (Element android app seems bust after last appstore update)

1 Like

thank you, thigg. yes, seems like a common issue.

incidentally, i am also having connectivity problems with the desktop flathub element app on opensuse tumbleweed.

I have the same issue with my new Xperia 10 II. I just flashed 4.5.0.16, did no restore from my old device and installed Element 1.5.22 via f-droid as one of my first apps. It crashes and f-droid doesn’t even seems to register it as installed.
On my Xperia 10 also with 4.5.0.16 Element 1.4.20 runs just fine and I don’t want to update it now. I cannot remember from witch source I installed it, though. So I tried installing Element 1.4.20 over Aptoide on my new Device with no such luck.

2 Likes

Agreed @str4el

Downgrading Element doesn’t seem to work, so I think this must be a problem with the Android compatibility layer in 4.5.0.16.

Has anyone tried if MicroG makes a difference?

1 Like

Ive been running with MicroG. But havent tried the element app per-se. However, in my experience, some apps that worked in 4.4.0.72 stopped working in 4.5.0.16.

I don’t run MicroG and I’m not sure if I want to. I try FluffyChat at the moment so I may be fine without Element.

1 Like

Element 1.5.22 runs fine on my Xperia 10 II with SFOS 4.5. I had element installed prior to the upgrade to SFOS 4.5 and afterwards upgraded element via F-Droid to 1.5.22. No issues here on opening / using the app.
I don’t use MicroG or some Google services replacement, just installed F-Droid and element with it (on an older SFOS version). Maybe the first time setup of element causes an issue (e.g. with permissions or requests)?

I had it installed before the upgrade as well. Did you upgrade element since the sfos upgrade?

I tried MircoG and it didn’t fix the problem.

Still unable to open Element after upgrading it from F-droid

@str4el thanks for the tip on FluffyChat, quite a nice program but unfortunately does not provide audible notifications on new messages, so I think Element is still the most functional, if we can get it working again!

fluffychat looks pretty serviceable, thanks.

is there any way to dark theme it? can’t see any options button on the main tab.

there is a dark theme in the preferences for Fluffychat. The main problem I see with it is no notifications on new messages…

In fact, the last SailfishOS update did fix notifications with Element… pity it broke after update!

1 Like

@abranson Do you think resetting appsupport might be sufficient? ([utilities] Add operation to reset aliendalvik. JB#53837 by abranson · Pull Request #57 · sailfishos/sailfish-utilities · GitHub)

1 Like