Not working on Android 9.0

[waozixyz]

I made a testapp using dioxus cli, the most basic one to debug an issue on an older device, and noticed that it does not work. The app immediately crashes.

Using adb logcat i could find this:

FATAL EXCEPTION: Thread-2
Process: com.example.Testapp, PID: 30573
java.lang.NoSuchMethodError: no non-static method "Landroid/view/WindowManagerImpl;.getCurrentWindowMetrics()Landroid/view/WindowMetrics;"

Get current window metrics is not available for Android 9.0 (API 28), it was introduced in API 30

Full log:

12-18 22:45:52.577 30573 30597 E AndroidRuntime: FATAL EXCEPTION: Thread-2
12-18 22:45:52.577 30573 30597 E AndroidRuntime: Process: com.example.Testapp, PID: 30573
12-18 22:45:52.577 30573 30597 E AndroidRuntime: java.lang.NoSuchMethodError: no non-static method "Landroid/view/WindowManagerImpl;.getCurrentWindowMetrics()Landroid/view/WindowMetrics;"
12-18 22:45:52.580   966  7781 W ActivityManager:   Force finishing activity com.example.Testapp/dev.dioxus.main.MainActivity
12-18 22:45:52.585   966  7781 I PowerWrap: PowerHal_Wrap_mtkPowerHint
12-18 22:45:52.598   966   986 I ActivityManager: Showing crash dialog for package com.example.Testapp u0
12-18 22:45:52.585   966  7781 I PowerWrap: PowerHal_Wrap_mtkPowerHint
12-18 22:45:52.618 30347 30347 D BoundBrokerSvc: onUnbind: Intent { act=com.google.android.mobstore.service.START pkg=com.google.android.gms }
12-18 22:45:52.631   966 30607 W DropBoxManagerService: Dropping: data_app_crash (319 > 0 bytes)
12-18 22:45:52.633   966 30607 W AES     : Exception Log handling...
12-18 22:45:52.633   966 30607 W AES     : Skipped - do not care third party apk
12-18 22:45:52.635   966   985 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
12-18 22:45:52.640   966   986 D ViewRootImpl[Testapp]: hardware acceleration = true , fakeHwAccelerated = false, sRendererDisabled = false, forceHwAccelerated = false, sSystemRendererDisabled = false
12-18 22:45:52.649   966   986 V WindowManager: Changing focus from null to Window{90a0cf5 u0 Application Error: com.example.Testapp} Callers=com.android.server.wm.WindowManagerService.addWindow:1519 com.android.server.wm.Session.addToDisplay:205 android.view.ViewRootImpl.setView:783 android.view.WindowManagerGlobal.addView:356
12-18 22:45:52.649   966   986 D WindowManager: Input focus has changed to Window{90a0cf5 u0 Application Error: com.example.Testapp}
12-18 22:45:52.650   966   993 I WindowManager: Focus moving from null to Window{90a0cf5 u0 Application Error: com.example.Testapp}
12-18 22:45:52.657   487   927 I BufferQueue: [unnamed-487-2936](this:0xb0b20000,id:2936,api:0,p:-1,c:-1) BufferQueue core=(487:/system/bin/surfaceflinger)
12-18 22:45:52.657   487   927 I BufferQueueConsumer: [unnamed-487-2936](this:0xb0b20000,id:2936,api:0,p:-1,c:487) connect(C): consumer=(487:/system/bin/surfaceflinger) controlledByApp=false
12-18 22:45:52.657   487   927 I BufferQueueConsumer: [unnamed-487-2936](this:0xb0b20000,id:2936,api:0,p:-1,c:487) setConsumerName: unnamed-487-2936
12-18 22:45:52.657   487   927 I BufferQueueConsumer: [Application Error: com.example.Testapp#0](this:0xb0b20000,id:2936,api:0,p:-1,c:487) setConsumerName: Application Error: com.example.Testapp#0
12-18 22:45:52.657   487   927 I BufferQueueConsumer: [Application Error: com.example.Testapp#0](this:0xb0b20000,id:2936,api:0,p:-1,c:487) setDefaultBufferSize: width=795 height=455
12-18 22:45:52.659   966   986 D Surface : Surface::allocateBuffers(this=0x7deff800)
12-18 22:45:52.659   966  9116 I OpenGLRenderer: Initialized EGL, version 1.4
12-18 22:45:52.659   966  9116 D OpenGLRenderer: Swap behavior 2
12-18 22:45:52.676 17795 30610 E DropBoxUtil: [AppErrors] null InputStream [CONTEXT service_id=254 ]
12-18 22:45:52.676 17795 30610 E DropBoxUtil: java.io.IOException: null InputStream
12-18 22:45:52.676 17795 30610 E DropBoxUtil: 	at 

[waozixyz]

So from my understanding, the issue could be that dioxus is directly using the api, without support of the Backport implementation?

[waozixyz]

I guess this is not a dioxus issue but a tao issue that is used underneath, I found the function in the tao source code if this is really the cause of the constant crash of any dioxus app attempting to run on an older model

[waozixyz]

It does seem to be dioxus related, whatever is causing the crash.

I started a fresh tauri v2 app with rust vanilla frontend, with my assumption that if it is an issue with tao it would affect the tauri apps as well. but to my surprise the app launched without any issue (using the dioxus frontend failed again, but i think the dioxus frontend in tauri is more experimential? i did not analyze it further.

Does anyone know what i should do to analyze the issue further?

The phone i'm testing is a moto e6 play with Android 9. Another phone with a later version does not experience any issues.

[jkelleyrtp]

Android 9 is quite old...

Final security update
The final security update for Android 9 was released on January 4, 2022.

We might need to upgrade our version of tao - maybe tauri updated tao to not crash?

Can you try tao out but with the same version Dioxus uses? There's also a chance we enable features that shoudn't be enabled and/or are hitting a codepath that tauri doesn't.

[DogeDark]

@jkelleyrtp I use Android 9 and didn't have this issue before the release. The WindowMetric API call in Tao hasn't been changed in two years.

[waozixyz]

@DogeDark you are right its not the windowmetric causing the issue, AndroidX is enabled so the backport shouldn't be an issue, something else is causing the crash...

[waozixyz]

@jkelleyrtp that was also my next thought, i'll try it out

[jkelleyrtp]

There's a chance we need to enable some compat flag somewhere that got "lost in translation" from our android rig to production. I thought androidx was that, but I vaugely remember another.

[waozixyz]

I cloned dioxus and changed the version of tao to 0.30.8, which was the version which worked fine with tauri, and i also tried version 0.31.0 of tao. So i don't think the issue is the tao version itself.

the only difference i can tell in the tao dependency that tauri uses is:
default_features = false

tao = { version = "0.31.0", default-features = false, features = ["rwh_06"] }

[waozixyz]

But the error is the adb logcat is different!

Using tao 0.30.0 current dioxus default:

12-20 11:38:00.870 16116 16185 I RustStdoutStderr: thread '<unnamed>' panicked at /home/wao/.cargo/registry/src/index.crates.io-6f17d22bba15001f/tao-0.30.0/src/platform_impl/android/mod.rs:788:10:
12-20 11:38:00.870 16116 16185 I RustStdoutStderr: called `Result::unwrap()` on an `Err` value: JavaException
12-20 11:38:00.870 16116 16185 I RustStdoutStderr: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
12-20 11:38:00.872 16116 16186 E AndroidRuntime: FATAL EXCEPTION: Thread-2
12-20 11:38:00.872 16116 16186 E AndroidRuntime: Process: com.example.Testing, PID: 16116
12-20 11:38:00.872 16116 16186 E AndroidRuntime: java.lang.NoSuchMethodError: no non-static method "Landroid/view/WindowManagerImpl;.getCurrentWindowMetrics()Landroid/view/WindowMetrics;"
12-20 11:38:00.876   966  1076 W ActivityManager:   Force finishing activity com.example.Testing/dev.dioxus.main.MainActivity

Using Tao 0.31.0 && tao 0.30.8 with dioxus:

12-20 11:51:57.803 17664 17664 D Surface : Surface::allocateBuffers(this=0x81313000)
12-20 11:51:57.803 17664 17719 D Surface : Surface::connect(this=0x81313000,api=1)
12-20 11:51:57.803   487  1063 I BufferQueueProducer: [bitpit.launcher/bitpit.launcher.ui.HomeActivity#0](this:0xb0b6b000,id:4083,api:1,p:17664,c:487) connect(P): api=1 producer=(17664:bitpit.launcher) producerControlledByApp=true
12-20 11:51:57.805   487   487 I BufferQueueConsumer: [Splash Screen com.example.Testapp#0](this:0xaec99000,id:4103,api:2,p:-1,c:-1) disconnect(C)
12-20 11:51:57.806   487   487 I BufferQueue: [Splash Screen com.example.Testapp#0](this:0xaec99000,id:4103,api:2,p:-1,c:-1) ~BufferQueueCore
12-20 11:51:57.816   487   536 I BufferQueueProducer: [NavigationBar#0](this:0xb292e000,id:4079,api:1,p:1142,c:487) queueBuffer: fps=34.19 dur=1316.13 max=561.34 min=10.34
12-20 11:51:57.822   487   536 I BufferQueueProducer: [StatusBar#0](this:0xb0143000,id:4,api:1,p:1142,c:487) queueBuffer: fps=0.76 dur=1314.45 max=1314.45 min=1314.45
12-20 11:51:57.824   966  1214 I WindowManager: Relayout Window{ec79086 u0 com.example.Testapp/dev.dioxus.main.MainActivity}: oldVis=4 newVis=0 focusMayChange = true
12-20 11:51:57.830 17664 17664 V PhoneWindow: DecorView setVisiblity: visibility = 0, Parent = android.view.ViewRootImpl@bb8860f, this = DecorView@28af370[HomeActivity]
12-20 11:51:57.854   466   493 I vendor.mediatek.hardware.power@2.0-impl: powerHintAsync hint:8, data:0
12-20 11:51:57.861   487   534 I BufferQueueProducer: [bitpit.launcher/bitpit.launcher.ui.HomeActivity#0](this:0xb0b6b000,id:4083,api:1,p:17664,c:487) queueBuffer: fps=0.09 dur=22745.56 max=22630.21 min=115.34
12-20 11:51:57.861   966   979 I PowerWrap: PowerHal_Wrap_mtkPowerHint
12-20 11:51:57.861   966   979 I PowerWrap: PowerHal_Wrap_querySysInfo
12-20 11:51:57.864   966   979 E PowerHalWrapper: <amsBoostStop> duration: 6000ms
12-20 11:51:57.864   966   979 I PowerWrap: PowerHal_Wrap_mtkPowerHint
12-20 11:51:57.864   966   979 I PowerWrap: PowerHal_Wrap_mtkPowerHint
12-20 11:51:57.874 24122 24122 V PhoneWindow: DecorView setVisiblity: visibility = 4, Parent = android.view.ViewRootImpl@278a7b3, this = DecorView@7ea2170[MainActivity]
12-20 11:51:57.882 24122 24160 I RustStdoutStderr: thread 'main' panicked at /rustc/eeb90cda1969383f56a2637cbd3037bdf598841c/library/core/src/cell.rs:1272:14:
12-20 11:51:57.882 24122 24160 I RustStdoutStderr: already borrowed: BorrowMutError
12-20 11:51:57.882 24122 24160 I RustStdoutStderr: thread 'main' panicked at library/core/src/panicking.rs:221:5:
12-20 11:51:57.882 24122 24160 I RustStdoutStderr: panic in a function that cannot unwind
12-20 11:51:57.882 24122 24160 I RustStdoutStderr: stack backtrace:
12-20 11:51:57.882 24122 24160 I RustStdoutStderr:    0: 0x87458cf8 - <unknown>
12-20 11:51:57.883 24122 24160 I RustStdoutStderr:    1: 0x874766f6 - <unknown>
12-20 11:51:57.883 24122 24160 I RustStdoutStderr:    2: 0x874511f0 - <unknown>
12-20 11:51:57.883 24122 24160 I RustStdoutStderr:    3: 0x8745a6d4 - <unknown>
12-20 11:51:57.883 24122 24160 I RustStdoutStderr:    4: 0x8745a35a - <unknown>
12-20 11:51:57.883 24122 24160 I RustStdoutStderr:    5: 0x8745b06c - <unknown>
12-20 11:51:57.883 24122 24160 I RustStdoutStderr:    6: 0x8745ae48 - <unknown>
12-20 11:51:57.883 24122 24160 I RustStdoutStderr:    7: 0x8745904c - <unknown>
12-20 11:51:57.883 24122 24160 I RustStdoutStderr:    8: 0x8745ac2e - <unknown>
12-20 11:51:57.883 24122 24160 I RustStdoutStderr:    9: 0x87473b74 - <unknown>
12-20 11:51:57.883 24122 24160 I RustStdoutStderr:   10: 0x87473bce - <unknown>

the ruststdout errer goes on forvere until i press the "close app" button in the "Testapp keeps stopping" window

[waozixyz]

@jkelleyrtp regarding your suggestion to try running tauri with the older version of tao that dioxus uses.

i did that as well. forked all the tao tauri projects, changed the dependency to the version in question 0.30.0, and made sure cargo.lock is using that version.

running it works fine as always, so seems be some kind of difference between how tauri and dioxus leverage tao?

what else can I try to analyze/ debug?