-
Notifications
You must be signed in to change notification settings - Fork 586
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
Fatal Exception: java.io.FileNotFoundException: open failed: EACCES (Permission denied) #6611
Comments
Hi @Ihor-SA, thank you for reaching out. I tried reproducing the issue, however, I did not not encounter the same error. Based on the logs you shared, it looks to me that this is not an SDK issue. Could you share the Android Gradle Plugin version you're using? Also, can you share an MCVE to help us investigate the issue further? In addition to that, I noticed that you're not using the latest SDK version. Could you try using the latest Firebase SDK version? This is to ensure that you have that latest bug fixes that might be causing the issue. Thanks! |
@lehcar09 thank you for your response. We are currently using Gradle version 8.2.2. Unfortunately, I’m unable to reproduce the issue either, as the report comes from Crashlytics. However, the problem seems to occur on Android versions 10 and above (API level 29+). Our minimum API level is 24, target and compile version is 34, and we’ve set android:installLocation="auto" in the AndroidManifest file. |
Thank you for the details @Ihor-SA. From what I gather, this issue is from Firebase dependency androidx.datastore (issuetracker/337870543). It looks like this issue is caused by a race condition where the DataStore file might not exist yet when the read operation begins. According to this comment:
I'll keep this open for now so that we can keep an eye on it. Thanks! |
[READ] Step 1: Are you in the right place?
Issues filed here should be about bugs in the code in this repository.
If you have a general question, need help debugging, or fall into some
other category use one of these other channels:
with the firebase tag.
google group.
of the above categories, reach out to the personalized
Firebase support channel.
[REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
Relevant Code:
The text was updated successfully, but these errors were encountered: