Issue exchanging session token, for access Token android devices

[Shooksie]

Describe the bug?

I recently started helping a client of mine with a mobile application, and they have the Okta SDK implemented.
We are noticing a weird behavior with the SDK, on Android a lot of users can't login, this behavior is not consistent. Sometimes they are able to login, but a lot of times they are not.

After enabling more logs, we are noticing the issue mainly stems from exchanging the session token for an access token, with the android devices only.

On ios this issue does not occur on android it does pretty frequently, since this app is in production we are seeing this behavior with thousands of android users. We have currently, switched to the token api for android only, so we can allow those users to login, but we would like to understand what could be happening here, as the SDK has better error handling and simplifies token management.

I have checked everything from configuration to logs, and can't figure out the specific android issue. My specific java knowledge is mediocre, I only have enough knowledge to wire up a module. I am not able to capture the android logs as the users are in production but I can provide the JS error logged. Any help or support or similar reports on this issue that were addressed would greatly help me solve this problem for the client and the thousands of users who are facing this issue.

What is expected to happen?

When getting a session token is successful getting an access token shouldn't error out

What is the actual behavior?

Android users get the session token successfully. But upon generating the access_token it completely fails.

Reproduction Steps?

Login with the android sdk on a later model samsung or android device, and try generate a token. I can provide the scopes requested if needed

Additional Information?

No response

SDK Version

2.8.0

Build Information

No response