Skip to content

AppleButton doesn't show on iOS 12.5.5 #248

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

Closed
auliakbarh opened this issue Nov 25, 2021 · 7 comments
Closed

AppleButton doesn't show on iOS 12.5.5 #248

auliakbarh opened this issue Nov 25, 2021 · 7 comments

Comments

@auliakbarh
Copy link

I have an iPhone 5s device with iOS 12.5.5, and the AppleButton is not showing in my React Native app. But on the simulator, it runs fine. Is there a minimal version of the iOS device to use Apple Sign-In?

@auliakbarh
Copy link
Author

I've read the following issues:
#138

Is there a way to implement Apple Sign-In on iOS version 12?

@Romick2005
Copy link

Have you checked #166? Can you please give it a try if it works for you?

@mikehardy
Copy link
Collaborator

Yeah, at that point, the iOS device is just a "web capable computer", so the Web way is the way to go.

@auliakbarh
Copy link
Author

I've checked #166 and still doesn't work.

How can I implement the web way?

@Romick2005
Copy link

To check if this works, you need to install forked version until it is merged into the main module.
package.json
"@invertase/react-native-apple-authentication": "git+https://github.com/Romick2005/react-native-apple-authentication.git",
And then read how to use here

@mikehardy
Copy link
Collaborator

@Romick2005 is right and as current slightly overburdened maintainer 👋 just want to apologize it hasn't gotten the attention it deserves yet. From the time I spent on examining it previously my take was "this looks like the right way to go..." so normally going off on a fork would be risky but in this case I expect that PR or something very close to it (based off the PR, just with minor fixups perhaps - typical PR process) will be merged, so shouldn't be as risky

@mikehardy
Copy link
Collaborator

Happy to take PRs to resolve issues / extend functionality / clarify documentation but as current maintainer the library currently handles my use cases, which means I do not have an interest in volunteering unpaid labor myself for use cases I don't need.

Happy to take those PRs and merge them though if anyone paying attention to this issue is motivated to develop them.

In the meantime closing this as stale

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants