Hi Phil,
the user should actually never stay on the callback page but be redirected page to your website.
How exactly do you get to that page?
Regards,
Hello,
I have tried to login on Chrome on all of the websites that you have mentionned, but it worked everywhere.
Do you still have the issue? Could you please tell me the exact version of your Chrome?
Regards,
The callback URI can be any URL that you can enter in your browser. Our API redirects the user to this URL (there you can then extract the user's details and do you processing login/registration ...)
So it needs to be a fully qualified URL.
Hi Brett,
what you could do is replace the OneAll subdomain by your own sub-domain. So this purpose we have the "API Alias" feature. It however requires Silver plan and you need to update your social network apps to use the alias.
Best Regards,
Hi Ryan,
we have been able to reproduce the issue, but we unfortunately haven't released a bugfix yet.
One of our developers is however already working on it!
Best Regards,