IssueTracker

Project: platform/frameworks/support
Branch: androidx-master-dev

commit b90079595f33f58fece04026a97faa0d243acdb1
Author: Yuichi Araki <yaraki@google.com>
Date:   Wed Sep 18 16:55:49 2019

    Change the way to detect mismatch between POJO and query
   
    This fixes cursor mismatch warnings with expandProjection.
   
    Bug: 140759491
    Test: QueryMethodProcessorTest
    Change-Id: I7659002e5e0d1ef60fc1af2a625c0c36da0664d8

M       room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M       room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M       room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt
M       room/compiler/src/test/kotlin/androidx/room/processor/QueryMethodProcessorTest.kt
M       room/compiler/src/test/kotlin/androidx/room/testing/TestProcessor.kt

https://android-review.googlesource.com/1123258
https://goto.google.com/android-sha1/b90079595f33f58fece04026a97faa0d243acdb1

  The following changes were cherrypicked through Coastguard (https://android-build.googleplex.com/coastguard/)
  Release Track: (https://android-build.googleplex.com/coastguard/dashboard/6093116828680192/#/cherrypickHistory/all)
  Created: 2019-10-14 17:23:42.610596+00:00
  Changes: aosp/1123258
 

Project: platform/frameworks/support
Branch: androidx-master-dev

commit bdde5a1a970ddc9007b28de4aa29d60ffa588f08
Author: Yigit Boyar <yboyar@google.com>
Date:   Thu Apr 16 16:47:05 2020

    Re-factor how errors are dismissed when query is re-written
   
    This CL changes how we handle errors/warnings if query is
    re-written.
    There was a bug in expandProjection where we would report warnings
    for things that Room already fixes automatically (b/140759491).
    The solution to that problem (I7659002e5e0d1ef60fc1af2a625c0c36da0664d8)
    solved it by deferring validating of columns until after re-write
    decision is made. Unfortunately, this required changing PojoRowAdapter
    to have a dummy mapping until it is validating, make it hard to use
    as it does have a non-null mapping which is not useful.
   
    This CL partially reverts that change and instead rely on the log
    deferring logic we have in Context. This way, we don't need to break
    the stability of PojoRowAdapter while still having the ability to
    drop warnings that room fixes. This will also play nicer when we
    have different query re-writing options that can use more information
    about the query results.
   
    Bug: 153387066
    Bug: 140759491
    Test: existing tests pass
    Change-Id: I2ec967c763d33d7a3ff02c1a13c6953b460d1e5f

M       room/compiler/src/main/kotlin/androidx/room/log/RLog.kt
M       room/compiler/src/main/kotlin/androidx/room/processor/QueryMethodProcessor.kt
M       room/compiler/src/main/kotlin/androidx/room/solver/TypeAdapterStore.kt
M       room/compiler/src/main/kotlin/androidx/room/solver/query/result/PojoRowAdapter.kt

https://android-review.googlesource.com/1288456

hi there, i also encountering this issue while navigating through my fragment.
im using this function on onViewCreated https://pastebin.com/gxUCvdYE, when ever im navigating from history fragment to Home fragment i got error
here's my function to check if there is datastored in jetpack datastore https://pastebin.com/NqkV0zpe

Here's my code:

in App.kt class  fun getUserPreferences(): UserDataStorePreferences = UserDataStorePreferences(instance)
in Fragment :  
signInViewModel.saveToken(it.data.token)
signInViewModel.saveRefreshToken(it.data.refreshToken)

in Repository:
 CoroutineScope(Dispatchers.IO).launch {
            App.getUserPreferences().saveRefreshToken(refreshToken)
        }

ahd here's my datastore class:

package com.montymobile.sands.common

import android.content.Context
import androidx.datastore.DataStore

import androidx.datastore.preferences.*

import kotlinx.coroutines.flow.Flow
import kotlinx.coroutines.flow.catch
import kotlinx.coroutines.flow.map
import java.io.IOException

class UserDataStorePreferences(
    context: Context
) {


    private val applicationContext = context.applicationContext
    private val dataStore: DataStore<Preferences>

    init {
        dataStore = applicationContext.createDataStore(
            name = "sns_preferences"
        )
    }

    val getToken: Flow<String?>
        get() = dataStore.data.catch {
            if (it is IOException) {
                it.printStackTrace()
                emit(emptyPreferences())
            } else {
                throw it
            }
        }.map { preferences ->
            preferences[KEY_TOKEN]
        }

    suspend fun saveTokens(token: String, refreshToken: String) {
        dataStore.edit { preferences ->
            preferences[KEY_TOKEN] = token
            preferences[KEY_REFRESH_TOKEN] = refreshToken
        }
    }

    val getDeviceId: Flow<String?>
        get() = dataStore.data.catch {
            if (it is IOException) {
                it.printStackTrace()
                emit(emptyPreferences())
            } else {
                throw it
            }
        }.map { preferences ->
            preferences[KEY_DEVICE_ID]
        }

    suspend fun saveDeviceId(deviceId: String) {
        dataStore.edit { preferences ->
            preferences[KEY_DEVICE_ID] = deviceId
        }
    }

    val getAppVersion: Flow<String?>
        get() = dataStore.data.catch {
            if (it is IOException) {
                it.printStackTrace()
                emit(emptyPreferences())
            } else {
                throw it
            }
        }.map { preferences ->
            preferences[KEY_APP_VERSION]
        }

    suspend fun saveAppVersion(bookmark: String) {
        dataStore.edit { preferences ->
            preferences[KEY_APP_VERSION] = bookmark
        }
    }

    val getRefreshToken: Flow<String?>
        get() = dataStore.data.catch {
            if (it is IOException) {
                it.printStackTrace()
                emit(emptyPreferences())
            } else {
                throw it
            }
        }.map { preferences ->
            preferences[KEY_REFRESH_TOKEN]
        }

    suspend fun saveRefreshToken(refreshToken: String) {
        dataStore.edit { preferences ->
            preferences[KEY_REFRESH_TOKEN] = refreshToken
        }
    }

    val isLoggedIn: Flow<Boolean?>
        get() = dataStore.data
            .catch {
                if (it is IOException) {
                    it.printStackTrace()
                    emit(emptyPreferences())
                } else {
                    throw it
                }
            }.map { preferences ->
                preferences[KEY_LOGGED_IN]
            }

    suspend fun setLoggedIn(loggedIn: Boolean) {
        dataStore.edit { preferences ->
            preferences[KEY_LOGGED_IN] = loggedIn
        }
    }

    suspend fun clearTokens() {
       dataStore.edit { preferences ->
           preferences.remove(KEY_TOKEN)
           preferences.remove(KEY_REFRESH_TOKEN)
       }
    }


    companion object {

        val KEY_TOKEN = preferencesKey<String>("key_token")
        val KEY_DEVICE_ID = preferencesKey<String>("key_device_id")
        val KEY_APP_VERSION = preferencesKey<String>("key_app_version")
        val KEY_REFRESH_TOKEN = preferencesKey<String>("key_refresh_token")
        val KEY_LOGGED_IN = preferencesKey<Boolean>("key_logged_in")
    }
}

I had to replace

 suspend fun saveToken(token: String) {
        dataStore.edit { preferences ->
            preferences[KEY_TOKEN] = token
        }
    }

with

 suspend fun saveTokens(token: String, refreshToken: String) {
        dataStore.edit { preferences ->
            preferences[KEY_TOKEN] = token
            preferences[KEY_REFRESH_TOKEN] = refreshToken
        }
    }

Project: platform/frameworks/support
Branch: androidx-master-dev

commit ed6cbe16562eead7dd1a0042033d9386e686abfb
Author: rohitsat13 <rohitsat@google.com>
Date:   Tue Nov 24 11:57:06 2020

    Added a better exception and documentation so people ensure that there is only a single instance of DataStore per file.
   
    In b/173522155 there are a bunch of reports of seeing this exception. I think it's due to concurrent writes from different datastores on the same file. I think we should follow up with a more robust way of catching these issues (and possibly implementing singleton management ourselves as requested here: 173726702).
   
    Test: Added new test for concurrent writes from different DataStore.
    Bug: 173522155
    Relnote: Add a better documentation and exception around concurrent writes from datastores.
    Change-Id: Ia98a2c42d9a43bab2af0672f52b8786fe854cdfd

M       datastore/datastore-core/src/main/java/androidx/datastore/core/DataStoreFactory.kt
M       datastore/datastore-core/src/main/java/androidx/datastore/core/SingleProcessDataStore.kt
M       datastore/datastore-preferences-core/src/main/java/androidx/datastore/preferences/core/PreferenceDataStoreFactory.kt
M       datastore/datastore-preferences/src/main/java/androidx/datastore/preferences/PreferenceDataStoreFactory.kt
M       datastore/datastore/src/main/java/androidx/datastore/DataStoreFactory.kt

https://android-review.googlesource.com/1510256