search

okta / okta-oidc-android

OIDC SDK for Android
https://github.com/okta/okta-oidc-android
Other
59 stars 45 forks source link

Okta Sign-in page not launching #258

Closed syangatkonrad closed 3 years ago

syangatkonrad commented 3 years ago

Hi, we have had 3 separate incidents of the sign-in page not launching from client's Android phones.

These are the reported devices:

We unfortunate was not able to reproduce this issue, and was not provided with their Android version or which default browser they have installed.

Just wondering if you have any information or possible leads on this issue, thank you.

JayNewstrom commented 3 years ago

Hi, sorry to hear you're running into issues.

Are you using the latest version of the SDK (right now it's 1.0.20)?

We have heard some similar reports, but it's either come down to something like an Android for work profile blocking access to chrome, or devices that don't have the play store/chrome installed.

If you're able to reproduce this, I'd love to hear about it, and we can work on a fix.

syangatkonrad commented 3 years ago

We are using 1.0.17, are there any changes that may affect / fix this going from this version to the latest?

Also just want to confirm the supported browsers are Chrome and Firefox?

JayNewstrom commented 3 years ago

There are a few fixes that may fix this issue. But it's hard to know without logs/being able to reproduce the issue.

Chrome and Firefox both support chrome custom tabs, which is what we need for the SDK to work, that being said though, I mostly test with Chrome, so I expect that will work better.

gyasistory commented 3 years ago

I am having this same issue but I have been able to resolve it by making the targetSdkVersion 29. When I change it to 30 or higher and run it on a device running 30 or higher the okta sign-in doesn't open, but it does open on lower versions.

JayNewstrom commented 3 years ago

@gyasistory can you recreate this with the latest release of the SDK? 1.0.20, we've made some fixes for target sdk changes.

gyasistory commented 3 years ago

@JayNewstrom Thanks, that was the problem. I was using this from another internal repository. So I had to upgrade that call to get the latest version of this. And that fixed my issue thanks for the suggestion.

JayNewstrom commented 3 years ago

@syangatkonrad Can I close this issue now? Sounds like updating helped others on this issue.

syangatkonrad commented 3 years ago

Yes @JayNewstrom, thank you for your help.