-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unrecoverable error. Permission denied in /Users/cm/Realm/realm-java/realm/realm-library/src/main/cpp/io_realm_internal_SharedRealm.cpp #3972
Comments
SNAPSHOT 2.2.2 fixes #3629 which might fix this? |
@Zhuinden I hope so! :) When is the release version of 2.2.2 expected to be out? |
Personally, I'm surprised that it still isn't. |
@sabergeek Can you verify that SNAPSHOT 2.2.2 works for you? |
@kneth I certainly would, but I don't have access to those specific devices, nor emulators. |
@sabergeek We will release a new version soon. I hope that you will have the time to upgrade your app and monitor Crashlytics to see if the crash still occurs. |
@kneth I will push an update with Snapshot 2.2.2 and report back. Is there anything else I should be aware of/ expect with this snapshot (known bugs)? |
@sabergeek it has less bugs than 2.2.1, and I do not know of any new bugs that were introduced. |
You can either use the snapshot or wait a day (or two) to use a proper release. |
@kneth Then I'll wait instead, and will report back soon :) |
@sabergeek We have released 2.2.2 a few hours ago :-) |
@kneth Seems to be alright! It's over a week now and no crashes yet. |
@sabergeek Cool. I'll close the issue. Don't hesitate to reopen or create new issue if you see it again. |
@kneth I am seeing the similar crash in crash reports on realm 2.2.2
|
@AamirAbro what directory are you trying to open the Realm in? |
@Zhuinden the default one. here is how am I creating the it. |
Interesting, what device is it? 2.2.2 should have fixed it as per #3629 |
@Zhuinden Its happening mostly on HUAWEI devices. |
@AamirAbro do you open Realm instance in |
@tamtom hey, just checked the implementation of
So that would be a working solution! I will try to test that when I got time someday. |
@beeender I tested it and its working, I went to first realm call happen in the app and catch the exception on catch I call |
Key info from #5142
|
Hello, I have the same issue in many HUAWEI devices. The stack is
And I think it's not friendly to use BTW, I think most crash in HUAWEI device is caused by OTA. |
Hi, I see same crashreports on Huawei P8, LIW-L21 and Honor 7
|
Close this since it is not Realm side issue. See #3972 (comment) for more details and potential workaround. |
Hi I have a similar crash on 4.3.2 but with a sligh different name. It's same issue here ? BTW: This realm instance was created at when Application Not sure this is relevant or not.
|
@kuno what's relevant is the devices that you get this error in. |
same here: On: |
@izBasit wow. Where exactly do you open the Realm and in how many processes? |
@Zhuinden just one process throughout the app. And we open realm everytime we want to read or write to it. |
io.realm:realm-gradle-plugin:3.7.2 |
We are on 5.3.0 on seeing this crash:
We init Realm on app start and no queries are executed until after it is initialized. We insert on a background thread and query on the UI thread. What other information would be helpful? Devices? OS version? |
@thorbenprimke device is good, my guess goes for Huawei P8 and Huawei P8 Lite? |
Ref to current open issue tracking this: #5715 |
We're seeing this issue on a Lenovo VIBE X3 Lite (#5715 seems specific to other devices). Currently I'm not fond of the For now we might just live with it given the number of devices hitting this and hope that the user will eventually re-install the app. Is it worth attempting |
@jalexdev we had I do not have access to that project anymore so I do not know if the |
@Zhuinden @cmelchior So, is there any workaround for this or the issue gets resolved in 5.8.0? This error has been reported once since I upload my application on play store which is around 2 months back. My daily active user is around 50 - 80 right now. I am initializing the Realm in Application's oncreate like this -
And using getDefaultInstance() wherever i need it throughout the application. Do I need to change anything? I am not able to reproduce it. The Device was OnePlus 3T - 8.0.0 |
@Deathstroke007 I wish I had anything to tell you. I actually don't even know why this issue is closed. I believe it is the most severe issue, and should be utmost priority, but it's kinda been happening for... a while now. |
Goal
Sharing a crash log (as reported by Crashlytics) on specific devices.
Expected Results
To verify if my current API usage is correct and hopefully find a resolution.
Actual Results
Code:
The RepoImpl instance is being created from two separate classes and the realm instance is being closed only when onDestroy() is triggered in each of the classes. clearRealm() is currently never called.
Realm version(s): 2.2.1
Android Studio version: 2.2.3
Which Android version and device: Samsung SM-A500F (Android 6.0) and Lenovo S1a40 (Android 4.4.4)
It's seemingly working well on other devices.
The text was updated successfully, but these errors were encountered: