-
Notifications
You must be signed in to change notification settings - Fork 17
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
Login: "App certificate does not match configurations" #5
Comments
|
redirectUrl == "${data.scheme}://${data.host}"
Should it not be "begins with"-logic and not |
Above message was hastily written. A few clarifications: The redirect URI is passed into the function by us. It's the full path, including scheme and domain, i.e. And when we wrote Bundle ID, we meant Android Package Name. Bundle ID is the iOS equivalent. |
Same problem. |
I have the same problem |
I have the same problem Do you know what's going on now? |
You can delete a SHA-256 and try it out. I saved my APK signature information and then logged in to use it. It may be a bug in the TikTok configuration. @FightLi1017 |
Can you elaborate on this? We can't delete the SHA-256 - we need it there. Do you mean adding a random SHA and removing it again? |
It works for me now using version 2.0.3. :) |
I have this issue because I have configured two SHA256, and after deleting one, I can log in and use it. Perhaps TikTok can only be configured with one. When I only configure SHA256 on Google Play and upload it for internal testing channels to test TikTok login, I can successfully log in. |
Alright. We changed nothing on the app console. Updating the SDK to 2.0.3 fixed it. |
same problem; v2.0.3 not working for me. |
same issue in V2.0.3. |
I'm using the TikTok SDK to sign in with TikTok.
I have added both the MD5 and SHA256 hashes in the TikTok console and followed the steps in this guide:
https://developers.tiktok.com/doc/login-kit-android-quickstart-v2/. I did this for both my local debug key and the production keystore used to sign our app. I tried building for production as well, but I see this error in all cases and I am unable to proceed with the integration.
We used the legacy version of the Android SDK before, which is still in production and still works!
I'm able to authorize with TikTok and open the TikTok app via this code:
My app then opens again with this TikTok intent:
https://my-domain-here.tld?error=invalid_client&errCode=10033&error_description=App%20certificate%20does%20not%20match%20configurations.
This intent is then handled by the TikTok SDK:
And the reponse is:
I don't know what the error means and I cannot find any documentation on error code 10033. It would appear that the SDK does not know what to do with this either, as it says
isSuccess: true
anderrorCode: 0
while having noauthCode
, which makes no sense.The text was updated successfully, but these errors were encountered: