iOS is crashing when SnizzorsUIViewController is used in a non-app module

[kostakttipay]

When used directly from app module - works fine, however when the composable is extracted to a different module of the project, which is an implementation in app module - the iOS app crashes as soon as the composable tries to draw the component. No crash stacktrace for ios, obviously

[EricKuck]

What would you like us to do with this bug report? We've seen no such crash and without a stack trace there's not anything I can do to help you debug either.

[kostakttipay]

Thanks for the quick response!

If you have any known gotchas (e.g., module not exported to the iOS target, missing symbols, or presentation context issues), I’ll double-check those first. I’ll follow up with some logs this report can help others who hit the same issue.

[EricKuck]

Unfortunately no, I'm not aware of any potential footguns here. Do you get the same crash if you use UIKitView in place of the snizzors version?

[kostakttipay]

Yeah, works well with the default UiKitViewController fun.

I’m hitting Kotlin compiler errors on the iOS target. The build fails with missing property accessor for typedInteropView in both SnizzorsInteropViewHolder and SnizzorsInteropViewControllerHolder. I've attached the building logs I got. Snizzors-ios-build-logs.rtf

I dug into the error and it seems to choke on the custom getter for typedInteropView on the iOS target (likely a K2/Kotlin 2.x symbol resolution quirk around generic getter).

Thanks. Let me know if I can provide anything else.

[suchiz]

Hello, just had some conflict too. Happened that the Snizzors CMP version was too high compared to mine (1.7.x).
Got it working with:

compose-plugin = "1.9.3"
snizzors = "1.0.0"

Watch out for compatibility with android-lifecycle/navigation and everything else and you should be good.
We might add a compatibility map in the readme, idk if it is worth