android: fix bug where MayUseCollector is not available on some custom rom

[thinhbuzz]

fix Error: libart.so: unable to find export '_ZNK3art2gc4Heap15MayUseCollectorENS0_13CollectorTypeE
eg: frida/frida#2925
original change: #326

[poldenais]

hi @thinhbuzz is there a fix for this? I got a similar issue now running a script.

[QingShiLuoGu]

same issue,please merge it

[thinhbuzz]

@oleavr please check this

[Rycoh99]

I compiled a test version myself with this fix, but now I get the same error but with the export "_ZN3art2gc9collector17ConcurrentCopying12CopyingPhaseEv" from libart.so, am I the only one or does that change alone work for you?

[QingShiLuoGu]

@Rycoh99 I got same error:
unable to find export '_ZN3art2gc9collector17ConcurrentCopying12CopyingPhaseEv'"
environment: android 15, arm64
@thinhbuzz can ypu help analyze？

[JorySeverijnse]

Any expected date when this will be approved and when the next release comes with this fix? Having same issue btw

[Rycoh99]

Any expected date when this will be approved and when the next release comes with this fix? Having same issue btw

We still have to wait sadly...

[NgoHuy]

I create new PR, with this PR and mine, it should work on latest lineageos. #332

[Rycoh99]

I create new PR, with this PR and mine, it should work on latest lineageos. #332

I just tried it but it doesn't seem to work, still getting some errors complaining about _ZN3art2gc9collector17ConcurrentCopying12CopyingPhaseEv, maybe I compiled it wrong, but I don't know for sure, will try again

[thinhbuzz]

I create new PR, with this PR and mine, it should work on latest lineageos. #332

I just tried it but it doesn't seem to work, still getting some errors complaining about _ZN3art2gc9collector17ConcurrentCopying12CopyingPhaseEv, maybe I compiled it wrong, but I don't know for sure, will try again

please try again with the latest commit of this PR

[NgoHuy]

I create new PR, with this PR and mine, it should work on latest lineageos. #332

I just tried it but it doesn't seem to work, still getting some errors complaining about _ZN3art2gc9collector17ConcurrentCopying12CopyingPhaseEv, maybe I compiled it wrong, but I don't know for sure, will try again

You need edit manually file at directory build/subprojects/frida-gum/ which is under node_modules

[NgoHuy]

I create new PR, with this PR and mine, it should work on latest lineageos. #332

I just tried it but it doesn't seem to work, still getting some errors complaining about _ZN3art2gc9collector17ConcurrentCopying12CopyingPhaseEv, maybe I compiled it wrong, but I don't know for sure, will try again

please try again with the latest commit of this PR

I don't want to override your PR, then I created new PR, your new commit overrides my PR, it's not good fair.

[thinhbuzz]

You need edit manually file at directory build/subprojects/frida-gum/ which is under node_modules

we have different approaches, if you had the same approach as me I wouldn't have added it to my PR.

[Rycoh99]

I create new PR, with this PR and mine, it should work on latest lineageos. #332

I just tried it but it doesn't seem to work, still getting some errors complaining about _ZN3art2gc9collector17ConcurrentCopying12CopyingPhaseEv, maybe I compiled it wrong, but I don't know for sure, will try again

You need edit manually file at directory build/subprojects/frida-gum/ which is under node_modules

Yeah, that's what I did, seems to work now with the latest commit from thinhbuzz though, thanks!

[NgoHuy]

You need edit manually file at directory build/subprojects/frida-gum/ which is under node_modules

we have different approaches, if you had the same approach as me I wouldn't have added it to my PR.

What's approach? My PR is seperate from you, I see the problem after your patch and patched it, when user builds frida, they need to modify frida-java-bridge on their end. Don't include other PR if you didnot ask them before!

[thinhbuzz]

You need edit manually file at directory build/subprojects/frida-gum/ which is under node_modules

we have different approaches, if you had the same approach as me I wouldn't have added it to my PR.

What's approach? My PR is seperate from you, I see the problem after your patch and patched it, when user builds frida, they need to modify frida-java-bridge on their end. Don't include other PR if you didnot ask them before!

1. you use get and i use find, get can throw exception when not found
2. people report new bugs in my PR and you create new PR. when i update PR to fix the issue people update you say i did wrong?

Huh?

[NgoHuy]

You need edit manually file at directory build/subprojects/frida-gum/ which is under node_modules

we have different approaches, if you had the same approach as me I wouldn't have added it to my PR.

What's approach? My PR is seperate from you, I see the problem after your patch and patched it, when user builds frida, they need to modify frida-java-bridge on their end. Don't include other PR if you didnot ask them before!

1. you use get and i use find, get can throw exception when not found

2. people report new bugs in my PR and you create new PR. when i update PR to fix the issue people update you say i did wrong?

Huh?

Firstly, my PR is fix from original patch not from you, I respect your PR, it's the way opensource community runs. But you not!

2nd, I show that only my PR and your PR are merge, it would run.
3rd, you're right about getExportByName vs findExportByName, but in case you call it directly or include other function like attach, when you assign it to variable, it uses return of this function, in this case is NativePointer return, and it's null.

[oleavr]

Thanks! 🚀 Sorry it took me so long to get to this, I was out on vacation.

I refactored a tiny bit, but don't have a setup I can test this on at the minute. Could you take it for a quick spin just to check that I didn't break anything?

Note that this will result in method hooking stability issues on affected systems, so we should figure out a better solution someday. In the meantime this is obviously a lot better than failing completely, like we do currently, so I think we should merge this.

[oleavr]

Oops, updated with style fixes reported by the linter (probably my fault).

[sorasful]

Hey, I do have the same issue. Do we need something to merge this ? How can we help ?

[oleavr]

Thanks! 🙌

[esauvisky]

I am still encountering the following error :

Error: Unable to perform state transition; please file a bug
    at bt (frida/node_modules/frida-java-bridge/lib/android.js:578:1)
    at frida/node_modules/frida-java-bridge/lib/class-model.js:112:1
    at Function.build (frida/node_modules/frida-java-bridge/lib/class-model.js:7:1)
    at k._make (frida/node_modules/frida-java-bridge/lib/class-factory.js:168:1)
    at k.use (frida/node_modules/frida-java-bridge/lib/class-factory.js:62:1)
    at frida/node_modules/frida-java-bridge/index.js:216:1
    at c.perform (frida/node_modules/frida-java-bridge/lib/vm.js:12:1)
    at _.performNow (frida/node_modules/frida-java-bridge/index.js:213:1)
    at Object.1 (src/dev.js:8:6)
    at o (node_modules/browser-pack/_prelude.js:1:1)

This occurs even with the following minimal code:

Java.perform(function () {

});

ART runtime: com.google.android.art versionCode:350820460

[freerunners]

Hi! How can I fix the problem? I have the same issue

[Rycoh99]

Hi! How can I fix the problem? I have the same issue

Hi! As the fix is already implemented into the GitHub repositories from what I've seen, you just have to wait for the next build of frida-server on the main repo.