-
Notifications
You must be signed in to change notification settings - Fork 3
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
Invalid authentication #4
Comments
Hi Hydreliox, Does you Super Soco bike use the old application (Super Soco) or the new one (Vmoto Soco)? I'm asking because, as of current date, this integration is only compatible with the old application, which is my case (TCmax 2021). I would need access to a new application's user account in order to reverse engineer its API calls and add compatibility. If that's not the case and you're using the old application, you can see the error logs in Settings > System > Logs. They look similar to this one: If you wish you can also enable full debug logs by adding these lines into your
After that, they should be visible by clicking the "Show full logs" button located at the bottom of the Logs section. |
Thank you for your time. I'm using the old app. I will provide logs as soon as possible. |
"The only difference is that I can't put a 0 at the begining of the phone number." <- This got me thinking. The phone number field is currently an integer, perhaps it should be a string so it accepts leading zeroes. Honestly, it didn't occur to me that phone numbers could begin with a zero. 😓 I'll try to push a fix as soon as I can. |
Done, this should be fixed in 1.0.0-beta.5. Please let me know if the issue persists. |
Ok now I can put a 0 on the front of phone number and it solves the authentication issue. Thank you very much! |
Hello,
I don't know where to find log, please point at me where I can find it to provide them here.
Anyway I can log into the app and not into the integration using the same credentials. The only difference is that I can't put a 0 at the begining of the phone number. I suppose this is the problem maybe...
Excuse me for my poor English as it's not my naative language.
Thank you for your work.
The text was updated successfully, but these errors were encountered: