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
No uri registered to handle redirect or multiple applications registered #100
Comments
In your org settings you can remove "https://" from the URIs config = OIDCConfig.Builder()
.clientId(“id here”)
.redirectUri(“domain.okta.com/login/callback”)
.endSessionRedirectUri(“domain.okta.com/login/callback”)
.scopes(“openid”, “profile”, “offline_access”)
.discoveryUri(“https://domain.okta.com”)
.create() and android.defaultConfig.manifestPlaceholders = [
“appAuthRedirectScheme”: “domain.okta.com”
] |
Unfortunately, It doesn't help me. I get the same error: My current config:
and
|
Heres a config of my sample: config = OIDCConfig.Builder()
.clientId("CLIENT_ID")
.redirectUri("com.first.sample:/callback")
.endSessionRedirectUri("com.first.sample:/logout")
.scopes("openid", "profile", "offline_access")
.discoveryUri("https://com.first.sample")
.create() android.defaultConfig.manifestPlaceholders = [
"appAuthRedirectScheme": "com.first.sample"
] Since you have the scope Also check that you don't have multiple apps with the same redirect scheme: #adb shell dumpsys package | grep com.first.sample
adb shell dumpsys package | grep manifestScheme |
I had removed the "https://" from my code and from OKTA Admin Panel and it helped me. Thanks! |
hello , { |
@yahmi can you make sure you have added redirect scheme to build.gradle and have no apps currently installed with same redirect sheme, please |
@NikitaAvraimov-okta yes i did all these steps but not working |
@NikitaAvraimov-okta @JayNewstrom |
@yahmi could you look at the comment from this similar issue: #233 (comment) If you can provide more information, I'd be happy to help. |
@JayNewstrom fixed with @NikitaAvraimov-okta thanks a lot |
Hi, I'm also getting the same error, please review my configuration & let me know, what am I doing wrong here: Build Gradle Configuration File `package sample.okta.android internal object Configuration { Build Method
|
* Fixes react native java imports * fix: Adds Swift version to podspec OKTA-371911 <<<Jenkins Check-In of Tested SHA: 81087ea49008251e1cdedd78559ae7f124f2f72c for eng_productivity_ci_bot_okta@okta.com>>> Artifact: okta-react-native * fix: Adds types/index.d.ts into files array OKTA-371431 <<<Jenkins Check-In of Tested SHA: 7b7c2e3b1aa447829c87731df5fb355ae44122ba for eng_productivity_ci_bot_okta@okta.com>>> Artifact: okta-react-native * 1.9.1 changelog (#83) * 1.9.1 changelog * 1.9.1 Update Changelog * 1.9.1 Update Changelog Co-authored-by: Oleg Gnidets <oleg.gnidets@okta.com> * bump package version: 1.9.1 * fix: Fixes "types" parameter in package.json Note for the future: To check whether a file is visible in a package, make `yarn pack` and then `yarn add {path-to-archive}`. OKTA-371431 <<<Jenkins Check-In of Tested SHA: 7420307c4c434bc14c7b83ac12c5575bfcf2f212 for eng_productivity_ci_bot_okta@okta.com>>> Artifact: okta-react-native * chore: Bump package version - 1.9.2 (#92) * fix: Fixes a script to add support of file copying The `build.js` script doesn't preserve file' folder. For example, `types/index.d.ts` is copied into `dist/index.d.ts`. Now it copies into `dist/types/index.d.ts` OKTA-375765 <<<Jenkins Check-In of Tested SHA: 8b66da956f7860891bef5e2b6c3a8b2441d01491 for eng_productivity_ci_bot_okta@okta.com>>> Artifact: okta-react-native * chore: Updates changelog for 1.9.3 (#99) Co-authored-by: Nikita <nikita.avraimov@okta.com> Co-authored-by: NikitaAvraimov-okta <76003913+NikitaAvraimov-okta@users.noreply.github.com> Co-authored-by: Aaron Granick <aaron.granick@okta.com>
How to deal with the error:
E/SyncWebAuthClientImpl:No uri registered to handle redirect or multiple applications registered
I've set config:
and
Data was taken from there:
http://prntscr.com/p7nz29
I stuck with this, please help.
The text was updated successfully, but these errors were encountered: