Thanks for the tips on that - I’ve been tracing through the code and poking at this more today, and it seems that warning is actually just a red herring and an ‘expected’ result from current kirigami (and its ongoing lack of integration with the Qt Quick Styles), not an indication of some remaining problem with the apk that I’d created or with what I was doing.
It’s quite possible I’m still missing something important here - but this all seems to be quite a mess. If I want to have an app that respects the user’s system-wide dark or light theme choice - it seems that I either need to commit to using breeze on all platforms, and use Kirigami.Theme.* in QML - or commit to using Material.theme: Material.System and Material.* for styling instead of Kirigami.Theme, and use the Material style on all platforms.
Since there’s no way to do the equivalent of #ifdef Q_OS_ANDROID conditional blocks in the QML, there doesn’t seem to be any sane way to use the (most closely) platform native style on each platform, I’d need to commit all the QML to using just one of them everywhere…
Which seems so absurdly crazy to me that my head is still spinning a bit at how much time I’ve just spent believing it could only be something that I was doing wrong which prevented this from Just Working - because all the documentation (with no actual complete working examples), so enthusiastically reassured me that this should be easy and painless and was guaranteed to be cross platform and work well on mobile… Which I really wish it hadn’t, and was a bit more up front about the current and very real limitations - because I would have much rather spent all that time, which I’ve just wasted on wild goose chases, actually working on fixes for known and disclosed problems to push upstream to fix some of these things. Instead I’ve spent it trying to reconcile the dozens of half-working examples which all do things differently and often incompatibly so, with what I’d tried to put together as a minimal working example - and wondering what kind of brain injury I must have suffered to not be able to see the mistakes in my own, otherwise very simple, code that were preventing it from working…
Anyway, I definitely don’t want to hijack this thread with my ranting (if anyone does want to follow up on that, let’s take it somewhere else and let this one get back to the oxygen integration) - I really just wanted to say thanks for the helpful replies and trying to make sense of that somewhat misleading warning, and tie all this back to We need your thoughts on Kirigami (which the ranty bit is more appropriate for : ).