https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hiring-french
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
k

Kevin Worth

02/28/2023, 3:08 PM
Given the use of
StateFlow
via
stateIn(…)
how would one “restart” the subscription after an exception is caught?
val searchQuery = MutableStateFlow("")
    val scope = viewModelScope
    val uiState: StateFlow<ItemUiState> = searchQuery
        .flatMapLatest { query ->
            when {
                query.isBlank() -> itemRepository.items
                else -> itemRepository.search(query, scope)
            }
        }
        .map<List<String>, ItemUiState> {
            Success(it)
        }
//        This "works" but it loops indefinitely
//        .retryWhen { cause: Throwable, attempt: Long ->
//            emit(Error(cause))
//            true 
//        }
        .catch {
            emit(Error(it))
        }
        .stateIn(
            scope,
            SharingStarted.WhileSubscribed(5000),
            Loading)
This comes from slightly altering this project https://github.com/android/architecture-templates/tree/base where
uiState
starts out simply defined as (see MyModelViewModel.kt):
val uiState: StateFlow<MyModelUiState> = myModelRepository
        .myModels.map(::Success)
        .catch { Error(it) }
        .stateIn(viewModelScope, SharingStarted.WhileSubscribed(5000), Loading)
So, we want to use
flatMapLatest
to continually react to updates on the searchQuery (after user types in a new query and hits the search button).
But after hitting the
catch
, it stops listening to changes to the searchQuery because, the
catch
cancelled everything, right? So, how to clear it out and start over?
At the moment I’ve given up on using
.stateIn
so that I can keep hold of a
Job
from
launchIn
. Then on certain events I check to see if the
Job
is cancelled, and restart it when necessary. Shouldn’t there be a way to get it to work with
stateIn
?
Any ideas from anyone?
w

wasyl

03/07/2023, 2:51 PM
You pretty much just shouldn't throw and have a need for a catch in the first place, and instead use a wrapper like
Result
k

Kevin Worth

03/07/2023, 2:54 PM
I think I’m doing that, if I’m understanding you correctly. My
Success
and
Error
classes are extended classes of the sealed
ItemUiState
class. So, my
ItemUiState
is analogous to your
Result
, yes?
w

wasyl

03/07/2023, 2:55 PM
Yes but as far I see you still throw in the flow? Not sure which call exactly here throws exceptions
k

Kevin Worth

03/07/2023, 2:57 PM
There are two flows which are the most likely culprits •
itemRepository.items
itemRepository.search(query, scope)
w

wasyl

03/07/2023, 2:58 PM
Then both would need to return wrapper classes instead of throwing, or I think if you not let the error out of flatMap it would be OK too - you'd catch and cancel the inner flows, but outer one would still be active
k

Kevin Worth

03/07/2023, 3:02 PM
Forcing the repo to return a wrapper around the data doesn’t feel right. That would be leaking implementation details from one layer to the next, no?
I really appreciate your time @wasyl and I wonder if you could drop in a very short sample to convey your meaning on not letting the error out of flatMap…?
w

wasyl

03/07/2023, 3:16 PM
I mean to have a
catch
inside the
flatMapLatest
— so the map below is
.map<Result<List<String>>, ItemUiState>
I'm not 100% sure but I believe that way if repository fails then it will
Result.failure
and nothing else, but if
searchQuery
receives another emission then code inside
flatMapLatest
will be called again
k

Kevin Worth

03/07/2023, 3:20 PM
Hmmm, maybe I can throw that together quickly…
Just to prove it out, here’s what was easiest to do quickly:
...
query.isBlank() -> itemRepository.items
    .catch {
        println("boom: $it")
        emit(emptyList())
    }
else -> itemRepository.searchByTitle(query, viewModelScope)
    .catch {
        println("pow: $it")
        emit(emptyList())
    }
...
And sure enough, that did keep things listening. Now I just need to decide how to get this actually functional (since emitting an empty list was only for debugging).
Thanks again @wasyl for the idea. It might just work. We’ll see.
w

wasyl

03/07/2023, 4:01 PM
👍 good luck
In general the principle is that once a flow throws, it's done 🤷 At the same time `flatMap`s (and other operators that return inner flows) are kind of detached from the outer flow, so as long as you catch the error, you would only cancel the inner flow. In your first snippet, you didn't catch the error within
flatMap
so it propagated to the outer flow and canceled it too
And yes it's kind of annoying to have to wrap items but that's how it is. Even established libraries are moving towards no exceptions within flow approach (e.g. https://github.com/apollographql/apollo-kotlin/issues/4711)
k

Kevin Worth

03/07/2023, 4:03 PM
Interesting, will take a look at that
For those playing along at home, here’s what I ended up with which I don’t think is too bad (but I’ll take any suggestions):
val uiState: StateFlow<ItemUiState> = searchQuery
        .flatMapLatest { query ->
            when {
                query.isBlank() -> itemRepository.items
                    .map<List<String>, ItemUiState> { Success(it) }
                    .catch { emit(Error(it)) }
                else -> itemRepository.search(query, scope)
                    .map<List<String>, ItemUiState> { Success(it) }
                    .catch { emit(Error(it)) }
            }
        }
        .catch {
            emit(Error(RuntimeException("Uncaught exception in ViewModel", it)))
        }
        .stateIn(
            scope,
            SharingStarted.WhileSubscribed(5000),
            Loading)
Now, for the outer
catch
which we really don’t expect to hit, there will need to be some extra handling to recover, since that will still cancel. But for the typical, expected network errors, etc. they are handled in the inner `catch`es and things keep trucking nicely.