Hey everyone I’d like to know if Paging3 is supported in Compose Multiplatform? From the latest Paging3 release, it says

paging-compose

has moved its code to

common

and ships an Android artifact, matching the multiplatform support of

androidx.compose

.

It is supported in alpha according to changelogs https://developer.android.com/jetpack/androidx/releases/paging#3.3.0-alpha02

But I am getting error when adding paging-compose dependency in commonMain

What error do you get?

@Vaibhav Jaiswal I faced the same issue, so I’ve just switched to using

app.cash.paging:paging-runtime-composeui

and it works fine.

@Fyodor Danilov error is

cannot resolve dependency

@Vaibhav Jaiswal I am using both libraries. https://kotlinlang.slack.com/archives/C3PQML5NU/p1695286753110549?thread_ts=1695267178.800409&cid=C3PQML5NU

Im doing the same, but getting Kotlin Compiler error

IrPropertyPublicSymbolImpl for androidx.paging/DEBUG|3092957818876675223[0] is bound ............

It seems I’ve encountered a different issue from yours. When I added the

androidx paging-compose

to the

commonMain

, I encountered the error:

"Could not resolve all dependencies for configuration ':shared:iosArm64CompileKlibraries'."

I face this too, then moved to app.cash.paging-compose-common, but then facing this error when building

How about trying

app.cash.paging:paging-runtime-composeui

instead?

will try that

Hopefully this'll clarify some things: 1. AndroidX Paging's

paging-common

is multiplatform. It supports the JVM (as before), iOS, macOS, and Linux. 2. AndroidX Paging's

paging-compose

is "multiplatform". I put it in quotes, because it uses KMP under the hood, but the only platform it targets is Android. Depending on AndroidX Paging's

paging-compose

in the

common

source set only makes sense if you're also just targeting Android only (which you're probably not doing). 3. Multiplatform Paging's

paging-compose

is also multiplatform, but supports a bunch more targets than just Android (which is probably what you want). 4. You can mix-and-match AndroidX Paging and Multiplatform Paging artifacts, but they both have to be using the same version. For example, the latest version of AndroidX Paging that Multiplatform Paging supports is

3.2.0-alpha05

. I'm planning on supporting the latest version (

3.3.0-alpha02

) in Multiplatform Paging within the coming days. Once I've tracked

3.3.0-alpha02

in Multiplatform Paging, you'll probably want to depend on Multiplatform Paging's

paging-compose

artifact. If you're explicitly depending on

paging-common

anywhere, you can either depend on AndroidX Paging's

paging-common

, or Multiplatform Paging's

paging-common

(which has a few more targets you may or may not care about). In the meantime, depending on

3.2.0-alpha05

is the safest option.

Thanks a lot, this clarified all my doubts

Just tracked

3.3.0-alpha02

in Multiplatform Paging (https://github.com/cashapp/multiplatform-paging/releases/tag/3.3.0-alpha02-0.4.0), so you should be able to upgrade to the latest AndroidX Paging release if you wish!

@veyndan I upgraded to 3.3.0-alpha02-0.4.0, and since then I’m getting this error when building iosApp

error: Could not find "co.touchlab:stately-isolate"

I had the same issue, once I added stately dependencies to my project it's resolved

stately = "2.0.4"

stately-isolate = { module = "co.touchlab:stately-isolate", version.ref = "stately" }
stately-iso-collections = { module = "co.touchlab:stately-iso-collections", version.ref = "stately" }

implementation(libs.stately.isolate)
implementation(libs.stately.iso.collections)

I'm on vacation at the moment, but will have a look on Wednesday. What @sasikanth said is a good workaround for the time being though!

No issues, enjoy your vacation

@Vaibhav Jaiswal I'm just checking this now, and it surprises me! I ripped out Stately in the lastest version of Multiplatform Paging, so it's strange that it's complaining about it not existing. Do you mind checking what happens if you change your imports to the following?

implementation("app.cash.paging:paging-common:3.3.0-alpha02-0.4.0")
implementation("app.cash.paging:paging-compose-common:3.3.0-alpha02-0.4.0")

It still throws the same error

Hmm, weird…

I’ll try to replicate it in a sample app If I downgrade to the previous version it fixes,

The project I am working on is open source, with the same issue (although it's resolved after adding stately dependencies). I can share it in case you want to experiment it there

@sasikanth That's great — please do share!

Here you go: https://github.com/msasikanth/twine

@veyndan any update on this?

I kind've forgot about this tbh. I just tried pulling Twine and building it but I'm getting the following error after a `./gradlew build`:

> Task :resources:strings:kspCommonMainKotlinMetadata FAILED
e: java.lang.UnsupportedClassVersionError: cafe/adriel/lyricist/processor/internal/LyricistSymbolProcessorProvider has been compiled by a more recent version of the Java Runtime (class file version 63.0), this version of the Java Runtime only recognizes class file versions up to 61.0

Running

java --version

shows:

openjdk 20.0.2 2023-07-18
OpenJDK Runtime Environment Zulu20.32+11-CA (build 20.0.2+9)
OpenJDK 64-Bit Server VM Zulu20.32+11-CA (build 20.0.2+9, mixed mode, sharing)

@sasikanth Have you seen this error before?

Yes, I updated the Gradle toolchain version in the build files to 20 as well and that worked. I pushed those changes couple of days ago 🤔