Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to pass own OkHttpClient to DefaultUnleash #84

Closed
vassilisimon opened this issue Sep 1, 2024 · 2 comments · Fixed by #89
Closed

Add ability to pass own OkHttpClient to DefaultUnleash #84

vassilisimon opened this issue Sep 1, 2024 · 2 comments · Fixed by #89
Assignees
Labels
enhancement New feature or request

Comments

@vassilisimon
Copy link

vassilisimon commented Sep 1, 2024

Describe the feature request

Hello,

in the old unleash-proxy-sdk it was possible to pass a OkHttpClient to the UnleashClient.
This isn't possible anymore with the new sdk. It would be nice to have this ability again, as we need it so support devices with api < 23 with custom certificates.

Background

No response

Solution suggestions

No response

@vassilisimon vassilisimon added the enhancement New feature or request label Sep 1, 2024
@chriswk chriswk self-assigned this Sep 3, 2024
@chriswk
Copy link
Member

chriswk commented Sep 3, 2024

Hi @vassilisimon. Thanks for reporting this, we've added it to our todo list

@chriswk
Copy link
Member

chriswk commented Sep 18, 2024

@gastonfournier - let's have a spar on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants