-
Notifications
You must be signed in to change notification settings - Fork 66
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
Error: "SignInWithApple.authorize()" is not implemented on android #107
Comments
Current Android code is just a Capacitor plugin placeholder (that hasn't been updated since Capacitor v3: #105). This may be fixed either by:
|
Thanks very much for your reply. |
@Wallfacer005CN At this moment I'm not showing Sign in with Apple only on iOS platform like this: import { isPlatform } from '@ionic/react'
const authenticationServices: JSX.Element[] =
isPlatform('ios') && isPlatform('capacitor')
? [<AppleSignIn />, <GoogleLogin />]
: [<GoogleLogin />]
// .. render available authentication services |
Thank you very much. |
Same Issue No Solution for Android atm? |
Hello, although not in this plugin, I implemented Apple login on Android here: https://github.com/Cap-go/capacitor-social-login You can find the docs for it: here |
You mean that https://github.com/Cap-go/capacitor-social-login is not just an Apple login plugin for capacitor, but a plugin that handles login for multiple providers (Google, Apple, Facebook) ? |
Correct, but you don't have to use other providers. Capgo Social Login handles both Apple and Google with excellent documentation. As for Facebook, it was added my by coworker and is currently undocumented, but from what I know it should work |
Describe the bug
Error: "SignInWithApple.authorize()" is not implemented on android
Although the readme document states that Android is not supported, I noticed that there is Android code in the repository, and the update log shows that Android has been supported from a certain version. However, when I tested it on an Android device, I encountered an error indicating that it is not supported.
The text was updated successfully, but these errors were encountered: