-
Notifications
You must be signed in to change notification settings - Fork 120
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
A system issue occured #68
Comments
I am also having this error on react-native 0.41.2 |
Ok, do you have any extra info (logs, screenshots) that could help to fix it? |
The problem is occurring if I am disabled the client access token flow in account kit dashboard. By their documentation, it should work and the response should contain short-lived access token. Instead, it shows the error above. Adb logcat is not showing anything. |
It is working when i change require App secret to no in developer dashboard |
EDIT: Found an issue with Info.plist (messed up fbappid and acountkit token). Working fine |
@dp-singh the integration seems to be ok, since the view you're seeing is provided by the Account Kit SDK. Apparently it's an internal issue, probably retrieved by the Account Kit service. |
@dp-singh I have the same problem and it was because YES was set in Enable the client access token flow in account kit dashboard, but in the library configurations, responseType was the default one - token. It should be set to code if you want to get the authorization code on the client.
|
Thanks @nikolay-radkov! It's something could be added to the documentation? |
hi, (thanks for this library!) for me it works on iOS but not on Android, I am facing the same situation - the fix by @nikolay-radkov doesn't yet seem to work for me. I will keep seeing if I can figure out anything, but would appreciate hearing from anybody else on Android. |
@jslz I was facing this issue as well. I made a mistake of using AccountKit app secret as ak_client_token. Perhaps check that once to be sure. |
I'm on Android, [email protected] and [email protected]. Just dropping a quick note here to help anyone who may have made the same dumb mistake that I made. I solved my "A system issue occurred" problem by defining the correct value for my Account Kit Client Token in strings.xml. The problem wasn't with the library or the Account Kit infrastructure... the problem often lies somewhere between the keyboard and the chair. :-/ |
I am using php. same problem. What can I do now? |
In AccountKit dashboard find "Enable Client Access Token Flow" and set it ON. |
Add Product-> Account Kit-> Advanced Settings -> Configure Keys |
Thanks @nikolay-radkov your solution solved the problem.. Saved my day |
Thanks @nikolay-radkov |
Thanks @nikolay-radkov your solution works and after i changed it back to the .TOKEN it still work though at first initialization it have to be set to .CODE |
Do you think that is really necessary publish the app. I think that in dev mode should works. Can someone confirm? |
I did try to publish and the errors still appearing |
I'm using the latest version 0.40, I have searched existing issues, also googled could not find the error
I followed the guidelines mentioned in this package, i'm able to get the login interface for mobile when i give next after mobile number gets prefilled, i'm getting the following error.
"A system issue occured, Please try again"
The text was updated successfully, but these errors were encountered: