androidx.datastore crashes with java.io.FileNotFoundException: /data/user/0/com.app.id/files/datastore/a_datastore.preferences_p [337870543]

Fixed

Bug

Status Update

No update yet.

Description

mk...@opera.com

created issue #1

Apr 30, 2024 06:11AM

DataStore Component used: androidx.datastore for Android DataStore Version used: 1.1.0 Devices/Android versions reproduced on: Seems not connected to any specific device/Android version as we see it on many different ones on all Android versions.

After updating androidx.datastore from 1.0.0 to 1.1.0 we started to see a lot of the following crashes.

Fatal Exception: java.io.FileNotFoundException: /data/user/0/com.app.id/files/datastore/a_datastore.preferences_pb: open failed: ENOENT (No such file or directory)
       at libcore.io.IoBridge.open(IoBridge.java:574)
       at java.io.FileInputStream.<init>(FileInputStream.java:160)
       at okio.Okio__JvmOkioKt.source(Okio__JvmOkio.kt:181)
       at okio.Okio.source(Okio.java:1)
       at okio.JvmSystemFileSystem.source(JvmSystemFileSystem.kt:96)
       at androidx.datastore.core.okio.OkioReadScope.readData$suspendImpl(OkioStorage.kt:227)
       at androidx.datastore.core.okio.OkioReadScope.readData(OkioStorage.kt:1)
       at androidx.datastore.core.StorageConnectionKt$readData$2.invokeSuspend(StorageConnection.kt:74)
       at androidx.datastore.core.StorageConnectionKt$readData$2.invoke(StorageConnection.kt:20)
       at androidx.datastore.core.StorageConnectionKt$readData$2.invoke(StorageConnection.kt:20)
       at androidx.datastore.core.okio.OkioStorageConnection.readScope(OkioStorage.kt:113)
       at androidx.datastore.core.StorageConnectionKt.readData(StorageConnection.kt:74)
       at androidx.datastore.core.DataStoreImpl.readDataFromFileOrDefault(DataStoreImpl.kt:331)
       at androidx.datastore.core.DataStoreImpl.access$readDataFromFileOrDefault(DataStoreImpl.kt:53)
       at androidx.datastore.core.DataStoreImpl$readDataOrHandleCorruption$2.invokeSuspend(DataStoreImpl.kt:378)
       at androidx.datastore.core.DataStoreImpl$readDataOrHandleCorruption$2.invoke(DataStoreImpl.kt:16)
       at androidx.datastore.core.DataStoreImpl$readDataOrHandleCorruption$2.invoke(DataStoreImpl.kt:16)
       at androidx.datastore.core.SingleProcessCoordinator.tryLock(SingleProcessCoordinator.kt:50)
       at androidx.datastore.core.DataStoreImpl.readDataOrHandleCorruption(DataStoreImpl.kt:377)
       at androidx.datastore.core.DataStoreImpl.access$readDataOrHandleCorruption(DataStoreImpl.kt:53)
       at androidx.datastore.core.DataStoreImpl$readDataAndUpdateCache$4.invokeSuspend(DataStoreImpl.kt:314)
       at androidx.datastore.core.DataStoreImpl$readDataAndUpdateCache$4.invoke(DataStoreImpl.kt:16)
       at androidx.datastore.core.DataStoreImpl$readDataAndUpdateCache$4.invoke(DataStoreImpl.kt:16)
       at androidx.datastore.core.SingleProcessCoordinator.tryLock(SingleProcessCoordinator.kt:50)
       at androidx.datastore.core.DataStoreImpl.readDataAndUpdateCache(DataStoreImpl.kt:312)
       at androidx.datastore.core.DataStoreImpl.access$readDataAndUpdateCache(DataStoreImpl.kt:53)
       at androidx.datastore.core.DataStoreImpl$readState$2.invokeSuspend(DataStoreImpl.kt:234)
       at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
       at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:104)
       at kotlinx.coroutines.internal.LimitedDispatcher$Worker.run(LimitedDispatcher.kt:111)
       at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:99)
       at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.java:585)
       at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:802)
       at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:706)
       at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:693)

The crashes happen on app startup when we try read from the datastore early in the app startup process. We see a lot of them in the wild. Happened to us locally few times as well, but it's very rare and unpredictable which makes it hard to debug.
Among other calls we use runBlocking to read from the datastore in one place
Our app is single process and we only create the datastore once
We use single process datastore (the code didn't change after updating the lib)

Comments

mk...@opera.com <mk...@opera.com> #2Apr 30, 2024 07:37AM

Information redacted by Android Beta Feedback.

se...@opera.com <se...@opera.com> #3May 8, 2024 09:17AM

Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

to...@gmail.com <to...@gmail.com> #4May 27, 2024 12:41PM

This issue is so annoying & makes battery draining too fast, especially when battery is 20% & the battery saver is enabled already.

mk...@opera.com <mk...@opera.com> #5Jun 13, 2024 11:35AM

Confirm p8p beta 4.1. GPS 100%, google play services. Huge drain.

di...@gmail.com <di...@gmail.com> #6Jul 1, 2024 09:02AM

Same issue. Pixel 7 Android 15 beta 4.1, 14+ hours of Google Play Services (basically entire time off charger). Tried clearing cache and dat from Google Play Services and Google Play Store. Multiple reboots and even leaving Google Play Services beta. No difference.

da...@asana.com <da...@asana.com> #7Jul 12, 2024 12:20AM

Same happening me. Pixel 8a

mi...@outlook.com <mi...@outlook.com> #8Jul 17, 2024 07:35PM

I'm seeing the same issue on an 8 pro

ju...@ratpsmartsystems.com <ju...@ratpsmartsystems.com> #9Jul 18, 2024 01:06PM

Seems to be affecting Pixel 9 Pro XL as well, is this fixed in QPR1 for anyone?

br...@linear.app <br...@linear.app> #10Aug 19, 2024 06:18PM

Comment #9

Not fixed here on QPR1 Beta 1, Pixel 6 Pro.

mk...@opera.com <mk...@opera.com> #11Aug 19, 2024 06:54PM

Having same issues here on 15 beta 4.2 on pixel 9 pro xl. Google play services is taking 55 percent of battery after a full day use. Battery isn't lasting nearly as long as all the reviews coming out say it is

dc...@openai.com <dc...@openai.com> #12Sep 23, 2024 10:58PM

Same issue at Pixel 7 with QPR1 Beta 1

ja...@gmail.com <ja...@gmail.com> #13Oct 21, 2024 10:30AM

not fixed on 6a QPR beta1.1

Message last modified on Oct 21, 2024 10:31AM

dc...@openai.com <dc...@openai.com> #14Oct 30, 2024 08:07PM

Thank you for reporting this issue. The issue related to high battery drain attribution to Google Play services in Google Settings has been fixed and will be available in a future release.

For other issues related to battery drain, we request you to file a separate issue with all the relevant details like bug report

du...@gmail.com <du...@gmail.com> #15Nov 14, 2024 05:46AM

Google play services and google apps is consuming excessive battery after the new update, this has been going on for a few days, I want this problem to be fixed as soon as possible

zh...@google.com <zh...@google.com> #16Dec 11, 2024 08:43PM

Reassigned to zh...@google.com.

If you continue to have this issue, please file a new issue with the bug report here https://goo.gl/TbMiIO and reference this bug for context.

ps...@google.com <ps...@google.com> #17Dec 12, 2024 09:48AM

Not fixed in stable 15, pixel 8a

ma...@marcardar.com <ma...@marcardar.com> #18Jan 13, 2025 12:42PM

Confirm the bug is not yet fixed in stable Android 15 release (Pixel 8 Pro)

Message last modified on Jan 15, 2025 10:46AM

ma...@marcardar.com <ma...@marcardar.com> #19Jan 15, 2025 10:48AM

Comment has been deleted.

Message last modified on Jan 16, 2025 03:50PM

ni...@usecopper.com <ni...@usecopper.com> #20Jan 21, 2025 02:47PM

redacted

in...@gmail.com <in...@gmail.com> #21Feb 7, 2025 01:53PM

this is not fixed

el...@google.com <el...@google.com> Feb 14, 2025 07:28AM

Reassigned to el...@google.com.

el...@google.com <el...@google.com> #22Feb 15, 2025 02:59AM

7 pro - the same problem after update to andoid 15 stable.

el...@google.com <el...@google.com> #23Feb 19, 2025 12:00AM

Marked as fixed.

Google pixel 7, Android 15
__________________________
I also confirm the very high battery consumption of +/- 50% by Google Play services. The latest version is currently installed. How much longer can we tolerate this? Fix it finally. It's been more than a month since the stable version of Android 15 was released.

ap...@google.com <ap...@google.com> #24Feb 19, 2025 12:02AM

I expected the fix to be released with the yesterday rollout of Android 15 December Feature Pack...and it was not (the status is still Fixed). Play Services are still listed in the power consumption list with a certain % amount even if it seems to be greatly reduced. Please tell us at least if this is just a visualisation bug or if they are draining the battery effectively. Will the bug be fixed wit just a Play Services update or does it need a new build (possibly the next March 2025 Feature Pack)?

ki...@protonmail.com <ki...@protonmail.com> #25Feb 24, 2025 07:14PM

pixel 7, same issue, still present since android 15 and even joining beta program on play services.
15/20% of the battery juice goes always to the play services.
any info on when this "fixed" will be rolled-out?

Message last modified on Feb 24, 2025 07:16PM

el...@google.com <el...@google.com> #26Feb 24, 2025 07:29PM

For other issues related to battery drain, we request you to file a separate issue with all the relevant details like bug report

el...@google.com <el...@google.com> #27Feb 24, 2025 07:32PM

There seems to be a theory that Google play service does not judge network conditions at all, and even requests a large number of invalid connection requests when the network is limited, resulting in power consumption. It seems that the Google app (com.google.quicksearchbox) will be the same. Because the bug interception mechanism of Android lacks some functions, it cannot be recorded in the bug report.

el...@google.com <el...@google.com> #28Feb 25, 2025 12:22AM

Hello all,

i have a brand new Pixel 9 pro. I have the same issue. Play Services is eating my battery in the background (35%).
Did a factory reset but nothing helped. All updates are installed to date.
Very annoying.

Issue 337870543

Description

Issue summary

Comments

mk...@opera.com <mk...@opera.com> #2Apr 30, 2024 07:37AM

se...@opera.com <se...@opera.com> #3May 8, 2024 09:17AM

to...@gmail.com <to...@gmail.com> #4May 27, 2024 12:41PM

mk...@opera.com <mk...@opera.com> #5Jun 13, 2024 11:35AM

di...@gmail.com <di...@gmail.com> #6Jul 1, 2024 09:02AM

da...@asana.com <da...@asana.com> #7Jul 12, 2024 12:20AM

mi...@outlook.com <mi...@outlook.com> #8Jul 17, 2024 07:35PM

ju...@ratpsmartsystems.com <ju...@ratpsmartsystems.com> #9Jul 18, 2024 01:06PM

br...@linear.app <br...@linear.app> #10Aug 19, 2024 06:18PM

mk...@opera.com <mk...@opera.com> #11Aug 19, 2024 06:54PM

dc...@openai.com <dc...@openai.com> #12Sep 23, 2024 10:58PM

ja...@gmail.com <ja...@gmail.com> #13Oct 21, 2024 10:30AM

dc...@openai.com <dc...@openai.com> #14Oct 30, 2024 08:07PM

du...@gmail.com <du...@gmail.com> #15Nov 14, 2024 05:46AM

zh...@google.com <zh...@google.com> #16Dec 11, 2024 08:43PM

ps...@google.com <ps...@google.com> #17Dec 12, 2024 09:48AM

ma...@marcardar.com <ma...@marcardar.com> #18Jan 13, 2025 12:42PM

ma...@marcardar.com <ma...@marcardar.com> #19Jan 15, 2025 10:48AM

ni...@usecopper.com <ni...@usecopper.com> #20Jan 21, 2025 02:47PM

in...@gmail.com <in...@gmail.com> #21Feb 7, 2025 01:53PM

el...@google.com <el...@google.com> Feb 14, 2025 07:28AM

el...@google.com <el...@google.com> #22Feb 15, 2025 02:59AM

el...@google.com <el...@google.com> #23Feb 19, 2025 12:00AM

ap...@google.com <ap...@google.com> #24Feb 19, 2025 12:02AM

ki...@protonmail.com <ki...@protonmail.com> #25Feb 24, 2025 07:14PM

el...@google.com <el...@google.com> #26Feb 24, 2025 07:29PM

el...@google.com <el...@google.com> #27Feb 24, 2025 07:32PM

el...@google.com <el...@google.com> #28Feb 25, 2025 12:22AM

Add comment

Issue metadata