sign-in-with-apple | Sign in With Apple for React Native and Web | Frontend Framework library
kandi X-RAY | sign-in-with-apple Summary
kandi X-RAY | sign-in-with-apple Summary
Sign in with Apple for React Native .
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of sign-in-with-apple
sign-in-with-apple Key Features
sign-in-with-apple Examples and Code Snippets
- 🔨 Xcode 11 Beta
- 📱 Real iOS device or simulator running iOS 13 (Sign in with Apple is available for iOS 13 and newer)
- ✅ Sign in with Apple enabled application & app ID (Follow this [link](https://help.apple.com/developer-account/#/devde676
npm install sign-in-with-apple --save
yarn add sign-in-with-apple
pod 'SignInWithApple', :podspec => '../node_modules/sign-in-with-apple/SignInWithApple.podspec'
Community Discussions
Trending Discussions on sign-in-with-apple
QUESTION
I have a React native front end where I use invertase/react-native-apple-authentication to handle Apple Authentication.
Then I have a NodeJS back end, where I use A-Tokyo/apple-signin-auth to handle Apple authenticated users and let them access routes.
I made this authentication based on this article.
I want the users to be able use the app without logging in again without a time limit.
Therefore I save the identity token, which I get when the user does the first sign up in Async Storage in the front-end. Every time the user tries to access routes the user will be checked if he/she has a identityToken in the Header in my isAuth
middleware in the NodeJS backend for the respective request.
I can see in my logs not sometimes requests get the following error the backend in my isAuth
middleware:
JsonWebTokenError: error in secret or public key callback: input error: Invalid id token public key id at /app/node_modules/jsonwebtoken/verify.js:96:19 at _getIdTokenApplePublicKey (/app/node_modules/apple-signin-auth/lib/index.js:1:5730) at runMicrotasks () at processTicksAndRejections (internal/process/task_queues.js:95:5)
The error is thrown in the apple-signin-auth
library when executing this code:
ANSWER
Answered 2022-Mar-29 at 08:04As far as I understand the workflow, you verify the identity token in the backend only once when the user has authenticated themselves using "Sign in with Apple" on the device.
If verifying the identity token in the backend was successful, you receive a refresh token in the response. You are then supposed to save this refresh token in your backend and verify the refresh token once a day to check if the user is still logged in with Apple. What does that mean? For example a user could revoke access to your app. Or a different user could log in on the Apple device.
By the way, if you verify the refresh token on every request (read multiple times a day), you risk Apple throttling these requests.
Bear in mind that this doesn't free your system from rolling its own session management meaning that your system sends its own session ids back and forth between the backend and front-end. Once a day, you check the refresh token associated with a session to see if the user is still logged in.
Disclaimer: This is how I understood the docs of Sign in with Apple. In other works, I have no experience implementing it. Hope it helps nonetheless.
QUESTION
I'm trying to migrate my mobile app (developed with Cordova and AngularJS for Android and iOS platforms) and I have some issues from API 29 to API 30. In my app I download from a REST service a JSON catalogue with separated pictures (JPG format) that I store in Data Directory (cordova.file.dataDirectory). With the app build with API set to 29 the app works fine, downloading pictures and displaying them in an HTML page (updated with AngularJS). But if I try to build it with API set to 30, the app continues to work (it download correctly the json and the jpg files in Data Directory) but without displaying the pictures stored in that directory. I also tried to create a new simple mobile app using all the updated component (Cordova 10.0.0, Android platform 10.0.0, plugins, etc.) but I obtain the same behaviour and I cannot resolve this issue. Could you help me or have you an idea how to resolve it?
Info App build with API 29Cordova v8.1.2
Android Platform v8.0.0
Cordova v10.0.0
Android Platform v10.0.0
cordova-plugin-android-permissions 1.0.2 "Permissions"
cordova-plugin-camera 4.1.0 "Camera"
cordova-plugin-compat 1.2.0 "Compat"
cordova-plugin-datepicker 0.9.3 "DatePicker"
cordova-plugin-device 2.0.3 "Device"
cordova-plugin-dialogs 2.0.2 "Notification"
cordova-plugin-file 6.0.2 "File"
cordova-plugin-file-hash 0.4.1 "FileHash"
cordova-plugin-filepath 1.5.8 "cordova-plugin-filepath"
cordova-plugin-geolocation 4.0.2 "Geolocation"
cordova-plugin-globalization 1.11.0 "Globalization"
cordova-plugin-inappbrowser 3.2.0 "InAppBrowser"
cordova-plugin-network-information 2.0.2 "Network Information"
cordova-plugin-sign-in-with-apple 0.1.2 "cordova-plugin-sign-in-with-apple"
cordova-plugin-splashscreen 5.0.3 "Splashscreen"
cordova-plugin-statusbar 2.4.3 "StatusBar"
cordova-plugin-whitelist 1.3.4 "Whitelist"
cordova-plugin-wkwebview-engine 1.2.1 "Cordova WKWebView Engine"
cordova-plugin-wkwebview-file-xhr 2.1.4 "Cordova WKWebView File XHR Plugin"
cordova-sqlite-storage 5.0.0 "Cordova sqlite storage plugin - cordova-sqlite-storage plugin version"
ionic-plugin-keyboard 2.2.1 "Keyboard"
phonegap-plugin-mobile-accessibility 1.0.5-dev "Mobile Accessibility"
ANSWER
Answered 2021-Oct-07 at 14:14Try adding to you config
QUESTION
I have setup "Login with Apple" in my .Net Core Razor Pages app (.Net 5) which is using Microsoft Identity Framework for user management.
I followed this tutorial of Scott which helped me as far as the Apple Login page.
But after the successful login when the Call-Back endpoint is called, I am getting null
in the _signInManager.GetExternalLoginInfoAsync()
method call.
My initial research suggested that the ID Token may not contain required data.
Which is correct because the ID Token returned by the Apple does not contain email
or name
even though it is requested in the scope
.
Sample request:https://appleid.apple.com/auth/authorize?client_id=net.demo.client&redirect_uri=https%3A%2F%2Fdemo.website.net%2Fsignin-apple&response_type=code%20id_token&scope=email%20name&response_mode=form_post&nonce=637679-omitted
Here's the Authentication setup called from Startup.ConfigureServices()
method:
ANSWER
Answered 2021-Sep-23 at 11:40Is ASP.Net Identity configured to use the "cookie" scheme for external logins?
By default it will use IdentityConstants.ExternalScheme
. Try using:
QUESTION
I am getting an error using Apple Sign In with Firebase Auth: "MISSING_OR_INVALID_NONCE : Nonce is missing in the request."
The only other case I've been able to find is similar to the following question, however their solution of updating the pod file does not work.
Cause of error setting up Sign in with Apple for Firebase in Swift on iOS 13?
Error:
...ANSWER
Answered 2021-Sep-18 at 00:16You are not providing the rawNonce
- you are using the method with accessToken
instead.
Fix it by doing the following:
QUESTION
I have an ionic 1 app that builds successfully for ios but fails for android.
If I remove the cordova-plugin-facebook-connect
it builds successfully for android too so I assume the plugin is causing the failure.
Also, this problem only began after I upgraded the android-minSdkVersion
from 19 to 28 - which Google Play demanded.
I have already installed both cordova-plugin-androidx
and cordova-plugin-androidx-adapter
.
Here is the message I get when I run ionic cordova run android
.
ANSWER
Answered 2021-Sep-04 at 16:01You're running into the issue described on https://android-developers.googleblog.com/2020/07/preparing-your-build-for-package-visibility-in-android-11.html. In https://github.com/cordova-plugin-facebook-connect/cordova-plugin-facebook-connect/issues/81, cordova-plugin-facebook-connect
was updated to support Android 11 package visibility. That requires a more recent version of Gradle. If you update to cordova-android
9 or higher, that should fix this.
QUESTION
I took a look at few apps which use Sign in with Apple and noticed when user makes sign in for the first time, they show the "view" with name and email (share/hide):
And after I Sign in with Apple and delete the app and install it again from App Store, it will show a "reduced" view with just a continue button:
I have been following this tutorial https://www.raywenderlich.com/4875322-sign-in-with-apple-using-swiftui and what I get after unistalling the app and installing again is the "big" view with name and email. Any idea how to show the "reduced" view if user already signed in the past ?
...ANSWER
Answered 2021-Mar-29 at 07:51(after problem resolved in comments below)
The simulator does not always work properly - use actual (physical) device running iOS 13 or later.
Sorry for asking in answer - don't have enough reputation to comment on your question.
Is your sign-in (via Sign in with Apple) into app successful (can you read a name and email of the user)? If not, you should investigate why is the sign-in process failing and fix it.
It's a choise of operating system (OS) which view will appear ("big" or "reduced"). You cannot force OS to show the one you want ("big" or "reduced").
Expected behaviorYour observation of apps from AppStore is correct - the "big" view will appear only at first sign-in into Your App. Next sign-in in same App will be done via "reduced" view, unless you revoke the access to AppleID for that App (on your device go to Settings -> Your Apple ID Name -> Password & Security -> Apps using Apple ID -> Your App name -> Stop using Apple ID).
Your behaviorSo the behaviour - you're seeing again and again (after reinstalling app) a "big" view is indeed unexpected.
Check-listAs first step I would recommend you to look into (your device's) Settings for the list of Apps using your Apple ID (see path into Settings above):
- Is your App there after you sign-in with Apple into App?
- Is your App there after you delete your App from device?
- Is your App there after you reinstal your App?
If your App is not listed there at stage 1) than the sign-in is most likely not successful and you should investigate it.
If your App is listed there at all stages (1 - 3) I would just revoke the permission&restart, delete an app and restart the device.
QUESTION
I started out by following this tutorial to set up 'Sign in with apple' using Firebase:
However, even when I follow this tutorial:
https://www.iosapptemplates.com/blog/ios-development/sign-in-with-apple-swift#comment-37591
Without any reference to Firebase, I can't get past 'Sign up not completed' in the apple Sign in modal, after the facial recognition 'Signing in' spinner runs.
I've added the capability in XCode & in the identifier, tried adding the Key and without the Key as some tutorials don't mention it. I can't seem to find what I'm missing.
Code taken from tutorials above:
...ANSWER
Answered 2021-Mar-12 at 10:12It was an issue Apple-side, I tried everything yesterday it didn't work and now it's working today. :)
QUESTION
I am implementing Sign In with Apple on my iOS app (SwiftUI).
In SwiftUI, I can use the 'SignInWithAppleButton' (https://morioh.com/p/524e0408008c), this button displays the Apple logo and a text that can be "Sign In with Apple", "Sign Up with Apple" or "Continue with Apple" depending on the button type chosen (ASAuthorizationAppleIDButton.ButtonType).
However, I would like the button to be sized 120x60 (WxH). If I just resize this button, the text is still visible and displayed very small, the Apple icon is also resized and cannot be seen, so it is not useable. I want to show only the Apple icon. It seems allowed by the design guidelines (https://developer.apple.com/design/human-interface-guidelines/sign-in-with-apple/overview/buttons/)
How can I do this in SwiftUI? I could not find examples of custom Sign in with Apple buttons implementations.
Thanks for the advice!
...ANSWER
Answered 2021-Jan-20 at 16:50You will only find sample code for the basic parts of programming.
If you want to customize behavior/looks you will have to create your own. I suggest you start with the init()
for SignInWithAppleButton
QUESTION
I want to integrate the Sign in with apple button using storyboard because its hard to programmatically do it because I have an existing User Interface for login form. with facebook google etc buttons, as I searched, i stumbled with this:
https://medium.com/takeaway-tech/sign-in-with-apple-storyboard-version-698c650956e7, it tells in the step
that "In your storyboard, add a view object, and set the control’s class value to ASAuthorizationAppleIDButton in Xcode’s Identity Inspector" can someone show a step in image on how to implement this? sorry i'm fairly new in coding swift iOS. much appreciated if someone can demonstrate how this control class value works, thank you.
...ANSWER
Answered 2020-Oct-21 at 01:12QUESTION
I have setup an OpenID Connect provider using Azure B2C to enable my iOS users to sign in my application using Sign-in with Apple
.
I followed the instructions and it is working great.
I have to update the token regularly and I am trying to automate it.
I have set up an Azure Function that will be triggered on a schedule and it generates a new token.
Now I do not know how to update the client secret from the Azure Function itself. I am not sure which API to use...
Question
How can I update the client secret field of the external provider I have set up?
Update
The graph API seems to be what I need but I do not know how to reconcile a user and the configuration of an Azure AD B2C service ...
...ANSWER
Answered 2020-Sep-16 at 06:57You could update the client secret with Graph API. See the code sample about calling the Microsoft Graph API.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install sign-in-with-apple
First, you need to install NPM package using npm or yarn.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page