R.T. comments

Results 13 comments of


                                            R.T.

HttpTransportClient doesn't support proxy

You can use your own HttpTransportClient, with proxy.

Error: Unable to determine ClassLinker field offsets

Same as https://github.com/frida/frida/issues/2176

java.Lang.RuntimeException on setDataSource (status = 0xFFFFFFFF)

Please, see https://github.com/wseemann/FFmpegMediaMetadataRetriever/issues/59 That helped me.

Error: Unable to determine ClassLinker field offsets

Pixel 6 Android 12 Frida Server Version: 15.2.2 Same for me

Error: Unable to determine ClassLinker field offsets

@ridafkih I found that pixel 6 flashed with earliest stock ROM does not have this issue initially, but breaks after some time. I guess, I could help

Error: Unable to determine ClassLinker field offsets

> make build/frida-android-arm64/lib/pkgconfig/frida-core-1.0.pc Still having same issue. Do I need to replace only server, or use patched client as well?

frida-gadget error while frida-server works fine: Check failed: old_state_and_flags.GetState() != ThreadState::kRunnable

Getting same issue with frida-server on talkatone app

frida-gadget error while frida-server works fine: Check failed: old_state_and_flags.GetState() != ThreadState::kRunnable

$ pm uninstall com.google.android.art 32bit apps still not working. Pixel 6

[Play Integrity API] Binding to the service in the play store failed . This is due to having an old play store version installed on the device

From my investigation Play Integrity is binding specifically to com.android.vending So Play Integrity implementation can't be a part of GmsCore anymore ```java package com.google.android.play.core.integrity; import android.content.Intent; /* loaded from: classes2.dex...

[Play Integrity API] Binding to the service in the play store failed . This is due to having an old play store version installed on the device

> > [Play Integrity API Checker](https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck) report success on my phone. > > It is possible that the problem is not microG. > > I'm not completely sure but I...