Skip to content

Handle additional sslpinning varieties #475

@thgoebel

Description

@thgoebel

Is your feature request related to a problem? Please describe.
To make android sslpinning disable work for this app I had to change this line:

const CertificatePinnerCheckOkHttp = certificatePinner.check$okhttp.overload("java.lang.String", "u15");

to:

const CertificatePinnerCheckOkHttp = certificatePinner.check$okhttp.overload("java.lang.String", "kotlin.jvm.functions.Function0");

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.

Additional context
n/a

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions