hi here, I am having a companion object, that declares a method annotated with

JvmStatic

I want to write a junit/mockito test where I want to mock the method. Is there a way to do it? What if I remove

JvmStatic

? What are my options? I think it’s a part of the broader topic - how does the companion object relate to beans/singleton concepts of

Spring

, for example. Ideally, I would want no static methods at all. But instead having a singleton-y classes that I could mock or do whatever I can with the normal classes.

Is there a concept akin to webview in compose desktop?

I’m having problems using detekt in my project… (kotlin jvm project) I have different problems if I use 1.9.1 or 1.10.0 1.10.0

Execution failed for task ':foo:detekt'.
> Could not resolve all files for configuration ':foo:detekt'.
   > Could not find io.gitlab.arturbosch.detekt:detekt-cli:1.10.0.
     Searched in the following locations:
       - <https://repo.maven.apache.org/maven2/io/gitlab/arturbosch/detekt/detekt-cli/1.10.0/detekt-cli-1.10.0.pom>
     If the artifact you are trying to retrieve can be found in the repository but without metadata in 'Maven POM' format, you need to adjust the 'metadataSources { ... }' of the repository declaration.

I have seen someone mentioning in github issues that it seems that some artifacts weren’t published in all repositories If I try to use 1.9.1:

> Could not find org.jetbrains.kotlinx:kotlinx-html-jvm:0.7.1.
     Searched in the following locations:
       - <https://repo.maven.apache.org/maven2/org/jetbrains/kotlinx/kotlinx-html-jvm/0.7.1/kotlinx-html-jvm-0.7.1.pom>
     If the artifact you are trying to retrieve can be found in the repository but without metadata in 'Maven POM' format, you need to adjust the 'metadataSources { ... }' of the repository declaration.
     Required by:
         project :foo > io.gitlab.arturbosch.detekt:detekt-cli:1.9.1

I’ve tried all possible combinations of the instructions in the website and still haven’t got it to work. Can someone help?

How can i solve this exception with my navGraphs on orientation change? I do not get this error when top/starting navGraph.

java.lang.IllegalStateException: Restoring the Navigation back stack failed: destination -1666506032 cannot be found from the current destination Destination(0xcf551cdb) route=SettingsNavGraph

I’m having some issues with navigation in compose and I’m wondering if it’s expected behaviour… I have a bottom navigation bar with two top-level destinations (A and C) A is a nested navigation graph which also contains destination B. If I navigate A -> B, then click on the bottom nav item to go to C and then click on the first bottom nav item I’m back at B (as expected). But if I go back using the system navigation I return to A, but I expected to return to B (as that’s the current ‘active’ item in A’s graph). More info in thread

E: solved in thread, wasn't Koin specific.

org.koin.core.error.InstanceCreationException: Could not create instance for '[Factory:'com.example.SomethingViewModel']'

I've been getting this recently, but in a very peculiar context: only on a release build, regardless of minification being enabled. On debug — even minified — it works perfectly. I've cleared cache and what not, to no avail. The full error log doesn't reveal anything useful, just call sites. Why is Koin not able to "find" only this ViewModel? All the other ones work, which are very similar in terms of dependencies, what the code does, etc. Other ViewModels are being referenced both before and after this one (in Compose code), and they work without any runtime crashes. Nothing Koin-specific has changed in my code, so I have no idea how to narrow this down. Is there something else release-specific that could affect Koin's functionality here? It worked before; doesn't now. Koin 3.4.3, Compose 1.6.0-alpha04 (not using koin's compose libs though).

Seems HorizontalPager doesn’t dispose a composable, I have 3 pages with an event inside a

LaunchedEffect

using Unit as key in each page, but it gets called first time then anytime the page has been disposed by the Pager. Is there any way around that behavior? I just want when a user switches a page the previous page should be disposed.

I am trying to write a SqlDelight migration that adds a column to a table. I want to set a default value during migration but not on the fresh tables. I’ve tried this so far:

-- someTable.sq 0.sq
CREATE TABLE someTable(
	id TEXT NOT NULL PRIMARY KEY
)

-- someTable.sq 1.sq
CREATE TABLE someTable(
	id TEXT NOT NULL PRIMARY KEY,
	value INT NOT NULL
)

-- 1.sqm
ALTER TABLE someTable ADD COLUMN value INT NOT NULL DEFAULT 42;

This doesn’t pass SqlDelight tests because

someTable.sq

schema does not define default value, which I don’t want…Is it possible to make

ADD COLUMN

work here without forcing original schema to define default value, or is my best bet here to do manual table re-creation (create new table with new schema, move values there, delete old table, rename new table)?

Is it possible to write a data class in a Kotlin Multiplatform library that, when built for macOS, conforms to Equatable (or better yet, Identifiable) out of the box?

Any way to implement

deinit

in Kotlin on iOS? I guess not but you never know