<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/kotlin-weekly-538-d6xazzpet" -->

---
title: Kotlin Weekly #538 | daily.dev
description: This issue of Kotlin Weekly highlights a sponsored guide covering four Kotlin Flow bugs: a second collector triggering another network request, catch missing...
canonical: https://daily.dev/posts/kotlin-weekly-538-d6xazzpet
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Kotlin Weekly #538 | daily.dev
og:description: This issue of Kotlin Weekly highlights a sponsored guide covering four Kotlin Flow bugs: a second collector triggering another network request, catch missing...
og:url: https://daily.dev/posts/kotlin-weekly-538-d6xazzpet
og:image: https://api.daily.dev/og/posts/d6XAZzpET.png
og:image:alt: Kotlin Weekly #538
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Kotlin Weekly #538

**[Kotlin Weekly](https://daily.dev/sources/kotlinwkly)** · 2 min read · 0 upvotes · 0 comments

## Summary

This issue of Kotlin Weekly highlights a sponsored guide covering four Kotlin Flow bugs: a second collector triggering another network request, catch missing downstream exceptions, conflate() skipping expected values, and StateFlow never collecting upstream. It also links a Flow cheat sheet covering builders, operators, buffering and hot flows. The libraries section features Meniscus, a Jetpack Compose bottom nav bar using spring physics and an AGSL shader (Android 13+), AspectK for aspect oriented programming in Kotlin Multiplatform, Stipple for dithering Compose Multiplatform UI elements, and Prosa.kt, a declarative Kotlin source code generator.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://mailchi.mp/kotlinweekly/kotlin-weekly-538>

## Questions this post answers

### Why does my StateFlow never start collecting from the upstream flow?

StateFlow only begins collecting upstream when it has an active subscriber, since it relies on the same subscription based machinery as other Kotlin Flow operators. If nothing is actively collecting the StateFlow, the upstream producer never starts emitting, which is one of several Flow bugs that look correct at first glance but silently fail to trigger execution.

_Developers debugging StateFlow collection issues can find more Kotlin Flow write-ups on daily.dev._

### Why does catch not catch exceptions thrown downstream in a Kotlin Flow pipeline?

The catch operator in Kotlin Flow only intercepts exceptions thrown upstream of its position in the chain, not exceptions thrown by operators or collectors placed after it. This is a common source of unhandled crashes when developers assume catch guards the entire flow regardless of where it's placed.

_Those building resilient Flow pipelines can track more Kotlin error-handling patterns on daily.dev._

### Why does conflate() in Kotlin Flow cause me to miss values I expected to receive?

conflate() drops intermediate emissions when the collector is slower than the producer, keeping only the latest value at the time the collector is ready. Values emitted in between get skipped, so conflate() is unsuitable for pipelines where every intermediate value must be processed rather than just the most recent one.

_Developers tuning Flow backpressure behavior can follow more Kotlin concurrency coverage on daily.dev._

## Similar posts on daily.dev

- [Kotlin Weekly \#523](https://daily.dev/posts/kotlin-weekly-523-kmaj85ghy) · Kotlin Weekly · 0 upvotes · 0 comments
- [Kotlin Weekly \#514](https://daily.dev/posts/kotlin-weekly-514-iombm51vj) · Kotlin Weekly · 0 upvotes · 0 comments
- [Kotlin Flows in Android: A Clear Mental Model](https://daily.dev/posts/kotlin-flows-in-android-a-clear-mental-model-ln8rffwwm) · Medium · 0 upvotes · 0 comments
- [Kotlin Weekly \#508](https://daily.dev/posts/kotlin-weekly-508-4sz95vvti) · Kotlin Weekly · 1 upvotes · 0 comments
- [jetc.dev Newsletter Issue \#318](https://daily.dev/posts/jetc-dev-newsletter-issue-318-gxpobwlxa) · Jetpack Compose Newsletter · 1 upvotes · 0 comments

---

Tags: [#kotlin](https://daily.dev/tags/kotlin), [#jetpack-compose](https://daily.dev/tags/jetpack-compose)

[View this post on daily.dev](https://daily.dev/posts/kotlin-weekly-538-d6xazzpet)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Kotlin Weekly #538","url":"https://daily.dev/posts/kotlin-weekly-538-d6xazzpet","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/kotlin-weekly-538-d6xazzpet"},"datePublished":"2026-11-22T08:45:25.339Z","dateModified":"2026-11-22T08:45:52.049Z","description":"This issue of Kotlin Weekly highlights a sponsored guide covering four Kotlin Flow bugs: a second collector triggering another network request, catch missing...","image":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","thumbnailUrl":"https://media.daily.dev/image/upload/s--VDukGCjf--/f_auto/v1722860399/public/Placeholder%2002","isAccessibleForFree":true,"articleSection":"Kotlin Weekly","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Kotlin Weekly","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/e2df7a10e88541e2b6ebb4c10373b794","url":"https://daily.dev/sources/kotlinwkly"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/kotlin-weekly-538-d6xazzpet","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kotlin,jetpack-compose","timeRequired":"PT2M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Kotlin Weekly","item":"https://daily.dev/sources/kotlinwkly"},{"@type":"ListItem","position":3,"name":"Kotlin Weekly #538"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/kotlin-weekly-538-d6xazzpet#faq","mainEntity":[{"@type":"Question","name":"Why does my StateFlow never start collecting from the upstream flow?","acceptedAnswer":{"@type":"Answer","text":"StateFlow only begins collecting upstream when it has an active subscriber, since it relies on the same subscription based machinery as other Kotlin Flow operators. If nothing is actively collecting the StateFlow, the upstream producer never starts emitting, which is one of several Flow bugs that look correct at first glance but silently fail to trigger execution. Developers debugging StateFlow collection issues can find more Kotlin Flow write-ups on daily.dev."}},{"@type":"Question","name":"Why does catch not catch exceptions thrown downstream in a Kotlin Flow pipeline?","acceptedAnswer":{"@type":"Answer","text":"The catch operator in Kotlin Flow only intercepts exceptions thrown upstream of its position in the chain, not exceptions thrown by operators or collectors placed after it. This is a common source of unhandled crashes when developers assume catch guards the entire flow regardless of where it's placed. Those building resilient Flow pipelines can track more Kotlin error-handling patterns on daily.dev."}},{"@type":"Question","name":"Why does conflate() in Kotlin Flow cause me to miss values I expected to receive?","acceptedAnswer":{"@type":"Answer","text":"conflate() drops intermediate emissions when the collector is slower than the producer, keeping only the latest value at the time the collector is ready. Values emitted in between get skipped, so conflate() is unsuitable for pipelines where every intermediate value must be processed rather than just the most recent one. Developers tuning Flow backpressure behavior can follow more Kotlin concurrency coverage on daily.dev."}}]}
```

