@UseExperimental should take multiple marker classes [145137892]

Fixed

Feature Request

Status Update

No update yet.

Description

tr...@google.com

created issue #1

Nov 25, 2019 07:01PM

The AndroidX UseExperimental annotation only takes a single markerClass. This means only a single Experimental API can be used within the same scope. Taking an array of marker classes may be one way to fix this behavior.

By comparison, the kotlin UseExperimental annotation takes a vararg markerClass argument which allows for multiple experimental APIs in the same scope.

Comments

tr...@google.com <tr...@google.com> Nov 26, 2019 12:44AM

Assigned to al...@google.com.

al...@google.com <al...@google.com> #2Dec 3, 2019 05:33PM

Any update on this issue? We are seeing same crashes on lower end devices. Is there any temporary fix we could use?

tr...@google.com <tr...@google.com> #3Dec 3, 2019 09:00PM

al...@google.com <al...@google.com> #4Dec 4, 2019 04:38PM

deleted

al...@google.com <al...@google.com> Dec 6, 2019 08:21PM

Accepted by al...@google.com.

ap...@google.com <ap...@google.com> #5Dec 20, 2019 07:36PM

Marked as fixed.

In our case, we have b2b app running on dedicated devices.

After 1.1.0 DataStore update we had 6 terminals reported 30k androidx.datastore.core.CorruptionException fatal crashes on app start.

We use DataStore in WorkManager jobs and on regular Activity starts. Seems that after the application gets this state it will never will succeed to start successfully again. I am afraid that data is being corrupted.

Can't reproduce. But same as OP, we have very vanilla usage of DataStore Preferences. No multiple processes, just simple read/write key-values in a single process single Activity.

Issue 145137892