Describe the solution you'd like
I suspect other non-obfuscated Kotlin apps will require a similar change.
However there are already two big function blocks just for okhttp, so adding a third one doesn't feel right.
So this issue is somewhat a meta question: to what extend to you want to include/support all these different function signatures? And how? By replicating a lot of code, or introducing another level of abstraction somewhere?
Describe alternatives you've considered
Add a third okHttp3CertificatePinnerCheckXYZ function.
Is your feature request related to a problem? Please describe. To make
android sslpinning disablework for this app I had to change this line: https://github.com/sensepost/objection/blob/c2121af4944b44220f56a56fd283334aff9f6b16/agent/src/android/pinning.ts#L144 to:Describe the solution you'd like I suspect other non-obfuscated Kotlin apps will require a similar change. However there are already two big function blocks just for okhttp, so adding a third one doesn't feel right.
So this issue is somewhat a meta question: to what extend to you want to include/support all these different function signatures? And how? By replicating a lot of code, or introducing another level of abstraction somewhere?
Describe alternatives you've considered Add a third
okHttp3CertificatePinnerCheckXYZfunction.Additional context n/a