how to integrate google login without firebase in bare Expo App - react-native

I want to implement Google login in my ejected expo App as per doc it requires google-services.json file from firebase which I don't have. I already implement whole backend logic on my server so i just need successful token after login.
I also check expo-google-auth but after installation, it giving me an error that emulator not found(lib issue).
so how can I implement google login without Firebase.

Related

React Native Expo AuthSession; Google Authentication

I’m trying to setup the Google authentication using AuthSession in Expo documentation (without Firebase)
https://docs.expo.dev/guides/authentication/#google
The first problem is, that the slack example doesn’t work: on the devices and simulators nothing happen after pushing the button, and in web mode it returns an error
Error 401: invalid_client
The OAuth client was not found.
What I’ve done using steps in documentation:
I’m not sure if it’s necessary, but I’ve installed yarn add expo-application
I’ve registered in Credentials page (Google Cloud Platform)
Logged in using expo login, in the terminal where I was starting expo start
Created a new Google Client ID that will be used with expoClientId
(Image) New Google Client ID setting image
( I'm not allowed to input images now )
(Don’t know if it’s necessary) I’ve created a project in https://expo.dev/ and then published the project using dashboard of expo start
(Image) Setting for "publish" in expo start dashboard
Where:
“expo”: {
“name”: “rn-my-project”,
“slug”: “rn-my-project”,
“version”: “1.0.0”,
“orientation”: “portrait”,
…
}
Using the code in the example, provided in documentation for Google, I receive null as response.
As I understand, this should be enough to test the Google Authentication using AuthSession in Expo Go app. I also made iosClientId, androidClientId and webClientId, but I’m not sure if I made everything correct.
Will be glad for any help, because I couldn’t find any person with the problem as mine.
Yours sincerely.
P.S. I've successfully set up logInAsync for Google using this documentation, but it's written, that it is deprecated.

Error Logging into this app with facebook is not available at this time

today i get into this error using react native with expo managed workflow, i try with facebook sdk, expo-auth-session, webview url, so them i give up because every method give me the same error, i end when i eject from expo to react native bare with react-native-fbsdk-next, after config all the environment with Android studio, i fall at the same error point D:
Please if someone know, if i missing some configurations, i follow all the steps in expo, react-native-fbsdk-next, expo-auth-session and expo-facebook D:
Error Logging into this app with facebook is not available at this time
UPDATE: i created a new React Native project again from scratch, follow react-native-fbsdk-next and Facebook Android start guide for login, still getting the same error. I reach that the error occour when i need to type my account and password in the facebook app, if i was already loggued in and did not ask for new permissions, i can login sucessfully, but if i log out from facebook app or ask for 1 new permission, it force me to log in and the bug occurs again, also i reach this report at facebook page, if someone is getting the same error, please help comment:
error logging facebook is not available at this time

FCM: Mismatched Sender Id when trying to send notification to Expo app

I have a backend that send fcm to web app and expo apps. Double checked all the credentials. But still unable to get it work. Both of the credentials are under same project. Backend is using firebase admin, with service account. Front end is using google-services.json. Anyone encountered this?
Found out that the device token from expo-notification can only be used on standalone build. But not in expo-client during development.
https://forums.expo.io/t/using-fcm-as-push-notification-with-expo-client/42402/2?u=cyee
This is the copy paste comment by expo team.
Hi! If you want to send notifications directly through FCM, and not
through the Expo notifications service, you’ll have to test in a
standalone app (as in, an app you built with expo build:android). This
is because you don’t have the push credentials for the Expo client
app, only we do :slight_smile:
If you want to test in the Expo client app, then you can do that with
Expo’s notifications, which you can read more about here-
https://docs.expo.io/push-notifications/overview/

Is there a way to implement server side verification in google admob using react-native/expo and not android only?

I'm developing a expo/react-native app.
I want to use google admob inside my app (rewarded ads, videos), and verify in my server (node.js) if the user did finish the ad.
I saw in the website of google admob that there is a way to verify this in android. This is the link: https://developers.google.com/admob/android/rewarded-video-ssv
But I could not find anywhere, a way to verify it in react-native/expo app. (with node.js server).
I want to know if this is possible, and if so what is the best way to do it.

Migrating a native app to a RN/Expo app: keep user authenticated

I want to migrate an existing Android+iOS native app to a react-native Expo app.
In current native app, we store an auth token. I'd like this auth token to be available through ReactNative AsyncStorage api out of the box, without requiring RN native code (ie, ejecting Expo).
Is this possible, in current native app, to start writing to the same place as AsyncStorage will read after the migration?
We aim for the smoothest transition from native app to RN app, and user should stay authenticated after the upgrade.
Depends on what you're current app is using for storage. I recently used this library (https://github.com/kevinresol/react-native-default-preference) to get the data from user defaults then move it into async storage. I only migrate the refresh token and auth token.
If they are using core data, then you'll need to setup the same models etc - https://github.com/realm/realm-js/issues/584
The other storage mechanisms you can easily find a native package to get the data.
if the app is under same app name scheme you may be able to access after upgrade i guess.