Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

1K
Views
¿Por qué se crean varios almacenes de datos?

java.lang.IllegalStateException: hay varios almacenes de datos activos para el mismo archivo: /data/user/0/com.firstgoalkeeper.firstgoalkeeper/files/datastore/player_pref.preferences_pb. Debe mantener su DataStore como un singleton o confirmar que no hay dos DataStore activos en el mismo archivo (confirmando que el alcance está cancelado).

 class Constants { companion object{ const val PLAYER_PREFERENCE = "player_pref" val PLAYER_SELECTION_KEY = intPreferencesKey("player_selection") } } abstract class PrefsDataStore(context: Context, fileName: String) { private val Context.dataStore: DataStore<Preferences> by preferencesDataStore( fileName ) val mdataStore: DataStore<Preferences> = context.dataStore } class PlayerSelectionDataStore(context: Context) : PrefsDataStore(context, PLAYER_PREFERENCE) { suspend fun storeIndex(index: Int) { mdataStore.edit { it[PLAYER_SELECTION_KEY] = index } } val userSelectionFlow: Flow<Int> = mdataStore.data.map { it[PLAYER_SELECTION_KEY] ?: 4 } } @Composable fun PlayerSelection() { val context = LocalContext.current val playerSelectionDataStore = PlayerSelectionDataStore(context) var index by remember { mutableStateOf(4) } Log.d("index", "PlayerSelection: we are at index ${index} ") Log.d("index", "PlayerSelection: we select ${allTeamsLists[index].name} ") Row( verticalAlignment = Alignment.CenterVertically, modifier = Modifier .fillMaxSize() .background(color = goalkeeperBackground) ) { // ... Box( modifier = Modifier .clickable { GlobalScope.launch { playerSelectionDataStore.storeIndex(index) } Toast .makeText( context, "${allTeamsLists[index].name} player is Selected ", Toast.LENGTH_SHORT ) .show() } ... ) {...}

Lo que hice mal y sugiero las mejores prácticas.

over 4 years ago · Santiago Trujillo
1 answers
Answer question

0

No, estás creando un nuevo objeto PlayerSelectionDataStore en cada recomposición.

Lo menos que puedes hacer es envolverlo con remember :

 val playerSelectionDataStore = remember(context) { PlayerSelectionDataStore(context) }

Una solución más general:

 @Composable fun <T> rememberPreference( key: Preferences.Key<T>, defaultValue: T, ): MutableState<T> { val coroutineScope = rememberCoroutineScope() val context = LocalContext.current val state = remember { context.dataStore.data .map { it[key] ?: defaultValue } }.collectAsState(initial = defaultValue) return remember { object : MutableState<T> { override var value: T get() = state.value set(value) { coroutineScope.launch { context.dataStore.edit { it[key] = value } } } override fun component1() = value override fun component2(): (T) -> Unit = { value = it } } } } private val Context.dataStore: DataStore<Preferences> by preferencesDataStore(name = "preferences")

Uso:

 var text by rememberPreference(stringPreferencesKey("key_text"), defaultValue = "World") TextField(value = text, onValueChange = { text = it })
over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!