Cannot get currentApplication on Android 15

[Lynnette177]

OP591BL1:/data/local/tmp # ./frida-server-17.1.4-android-arm64 {"type":"error","description":"TypeError: n.currentApplication is not a function","stack":"TypeError: n.currentApplication is not a function\n at /internal-agent.js:1811:7001\n at we.perform (/internal-agent.js:1:25866)\n at kr._performPendingVmOpsWhenReady (/internal-agent.js:1811:6921)\n at kr.perform (/internal-agent.js:1811:6623)\n at /internal-agent.js:1811:16327","fileName":"/internal-agent.js","lineNumber":1811,"columnNumber":7001}

And, this comes from here.

Maybe it failed to get ActivityThread or something related to java is wrong.

[Matchman33]

same issue, the activityThread.currentApplication prop is undefined

[pimterry]

I'm pretty sure this is a symptom of much more general frida-java-bridge bug, that will break a lot of JVM use cases (cc @oleavr).

Using frida-tools 14.1.1 with Frida server 17.2.4 on Android, for example:

-> Java.use('java.lang.System').getProperty('java.vm.version')
"2.1.0"

Meanwhile, with frida-tools 14.1.2 or later:

-> Java.use('java.lang.System').getProperty('java.vm.version')
TypeError: not a function
    at <eval> (<input>:1)

It seems impossible to access any static methods via the Java bridge. Notably frida-tools updates frida-java-bridge from 7.0.1 to 7.0.3, so presumably that's where this broke.

In the meantime @Lynnette177 @Matchman33, I've found that downgrading to frida-tools 14.1.1 or older works perfectly.

[pimterry]

Pretty sure this was fixed in 7.0.4 and this can be closed now