-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
Goal
Open a realm database
Actual Results
In a few devices, Realm cannot initialize the file and it throws an exception:
Fatal Exception: io.realm.exceptions.RealmFileException: Unable to open a realm at path '/data/user/0/my.package.name/files/default.realm': Realm file initial open failed Path:Exception backtrace: <backtrace not supported on this platform>. (Realm file initial open failed Path: /data/user/0/my.package.name/files/default.realm Exception backtrace: <backtrace not supported on this platform>) (/data/user/0/my.package.name/files/default.realm) in /tmp/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_OsSharedRealm.cpp line 107 at io.realm.internal.OsSharedRealm.nativeGetSharedRealm(OsSharedRealm.java) at io.realm.internal.OsSharedRealm.<init>(OsSharedRealm.java:173) at io.realm.internal.OsSharedRealm.getInstance(OsSharedRealm.java:249) at io.realm.BaseRealm.<init>(BaseRealm.java:138) at io.realm.BaseRealm.<init>(BaseRealm.java:105) at io.realm.Realm.<init>(Realm.java:159) at io.realm.Realm.createInstance(Realm.java:495) at io.realm.RealmCache.createInstance(RealmCache.java:481) at io.realm.RealmCache.doCreateRealmOrGetFromCache(RealmCache.java:448) at io.realm.RealmCache.createRealmOrGetFromCache(RealmCache.java:412) at io.realm.Realm.getDefaultInstance(Realm.java:403)
Steps & Code to Reproduce
I cannot replicate the problem. I have the crash reports from open test users.
This is how I initialize the DB in the app
Realm.init(this) val realmConfiguration = RealmConfiguration.Builder() .encryptionKey(....) .assetFile("database/deploy.realm") .build() Realm.setDefaultConfiguration(realmConfiguration)
Then, later, the first time I do
Realm.getDefaultInstance()
it crashes for some users.
Version of Realm and tooling
Realm version(s): 10.3.1
Realm Sync feature enabled: No
Android Studio version: 4.1.2
Android Build Tools version: 4.1.2
Gradle version: 6.8.1
Which Android version and device(s):
at the moment it happened on different Samsung models with Android 10
Affected users are about 0.3% of the open tests user base