apple-auth | Sign in with Apple for Node.js | Runtime Evironment library

It seems native-base searches "react-dom": "*" and could not find it so somehow uses "react-dom": "17.0.2" and it in turn looks for "react": "17.0.2" which conflicts with expo's "react": "17.0.1".

So adding "react-dom": "17.0.1" as dependency solved the problem. By this way "react-dom": "*" finds "react-dom": "17.0.1" which is dependent to Expo's version "react": "17.0.1". (Please let me know if this conclusion is wrong.)

Following are the ones related with native-base and these versions should be used otherwise the npm install fails for Expo 44:

1) First off Firebase/MLVisionTextModel is deprecated (FirebaseMLVisionTextModel has been deprecated in favor of MLKitTextRecognition). You can read the migration guide here (https://developers.google.com/ml-kit/migration)

2) If you ever have errors like was resolved to x.x.x, which depends on Firebase/CoreOnly (= x.x.x) A lot of times you can fix this by adding this below at the very top of your PodFile to specify what version to use.

Check the library @react-navigation/drawer compatibility with IOS and Android respectively , link it manually sometimes autolinking doesn't work. Ensure you are running correct project , clean build and install pod and check it out.

We are not able to get the user details if we signed in before using the apple account until we are not removing the account access from apple settings.

So at the first time when we signing the user using an apple account, we have to store the user details somewhere like the backend or firebase database so we can get it back whenever we want.

Update: Actually the issue is that if your clustered map is animation enabled using the animationEnabled prop here, any following UI change is animated on iOS, see here.

I now reverted my original change (see below) and simply set the animationEnabled prop to false.

Initial answer:

Alright, found it (my fault :)) As you can see from the attached package.json file I'm using react-native-maps and react-navigation. As the screen rendering the map was not dismissed by react-navigationwhen navigating to the settings shown in the screenshots and changing the settings affects which map is rendered, changing the settings and the following update to the redux store trigger the hooks of my map component, thus re-rendering the screen and slowing down the app.

I addressed this issue now by using react-navigation event listeners and unmounting the map screen whenever it loses focus.

First, You need to decode identityToken using JWT decoder to verify the payload and signature.

And then, you should get a access token using authorizationCode and client_secret from Apple REST API.

client_secret is a JWT that you have to create to request a access token, and it needs your app's private key issued by apple developer configuration.

You'll need to do a few things

1. If you don't already have a .babelrc, create one and add the following

Apple Sign In only sends user info on the first sign in (sign up). After that, it's up to you to store those and reuse them when the user logs in again.

Thank you all for the support, after multiple efforts of solving this, I found the solution was related to my network making IPV6 requests instead of IPV4, I don't filly understand this but this is how I solved:

System Preferences > Network > Advanced > TCP/IP > Configure IPv6: Link-local only

Source