Видео

Hi, If you are looking for apple login, it's here: ruclips.net/video/ogpYfboojXc/видео.html&ab_channel=AndrewHeim-Dev

I would just console.log the user object and see if the name is attached to the account. Then you have access to it ... But if you already did that, and it's not there (which I remember it is not being accessible, but I could be wrong), then you would have to create an input name screen that let's them input their name so you can save it later.

Hmm not too sure. I would look around on the google play console and look for any way you can apply for production. Or see if you need to fill out any account information that could be missing. I found this stack overflow that might help you out: stackoverflow.com/questions/78112062/google-play-console-apply-for-access-to-production

I'm the opposite, I only built aab and can't install it on my phone

I’ve been running into this too. To my knowledge it’s because google sign in is not compatible with expo go. If you make an EAS build it will work but it won’t in expo go. Makes development a bit of a pain.

no problem! got you <3

I believe 6.9 iphone and 13 ipad are the only required ones. You might be able to get away with 6.5, but I'm not sure. I would just submit it, and before you can review the app it will give an error and let you know if you do need the 6.9 screenshot.

@@andrewheimdev oh, my app doesn't support ipad, is there any problem?

@@danhnhanchi6501 No shouldn't be a problem, just might have to deselect the ipad option in xcode. Not sure if there is a way to do it with expo. This thread I found explains a bit more: forums.developer.apple.com/forums/thread/701706

Thanks! Sorry not sure if I get your question. At 3:41 I'm re running the simulator. With "npx expo run ios".

Yes! Once you have a build on test flight, instead of making a new release, you can test it instead on test flight. So all the steps up until that point. Then you'l have to get testflight on your phone and add yourself

@@andrewheimdev thanks

Can you maybe give more details on the error code? When/Where you are getting the code. At what step?

Yeah the whole verification can be annoying when you don't have control over it. keytool -list -v -alias androiddebugkey -keystore ~/.android/debug.keystore -storepass android -keypass android Use this line to get the sha-1 and sha-256 fingerprint. I use this line though, just got to make sure the file path is correct: keytool -list -v -alias androiddebugkey -keystore android/debug.keystore -storepass android -keypass android

@@andrewheimdev thanks i managed to get it to work, i encountered the dev error 10 code but managed to fixed it with the discrepancy with my package name :)

@@wywlf6912 Nice! Glad you got it working.

No problem! And no dumb questions! This is free for the first 2 million invocations. Then it's $0.40/million after! And you can check out more specific pricing here: firebase.google.com/pricing

@@andrewheimdev great! Thank you for the quick reply

@@satyaviswapavanranga5915 no problem!

Depends on how backed up they are. This one only took about 24 hours, and I didn't have any issues where I had to resubmit. So it was relatively quick. Usually doesn't take longer than a few days though.

nevermind, I figured it out. just edit the scheme to release in xcode

@@sheehanmunim Nice glad you figured it out! For anyone else you basically just build, and submit to the app store all in xcode.

No problem! Thanks for watching!

If my problem is fix I will subscribe to your yt😅

​@@Unknown-h1i9x Glad you figured it out! Thanks for the subscribe!

@@Unknown-h1i9x you're probably using windows that's why

sure thing, I'll try and keep the pacing slower for these tutorials

Thanks a bunch! and thanks for watching! Me too :)

Yeah what do you mean by a real tutorial? Walking through each line of code, or typing everything instead of copy pasting it?

Hmmm you could use firestore for persistance, or you could use async storage so it's on the users device, and it just requires a few lines of code: stackoverflow.com/questions/71551192/best-way-to-persist-firebase-login-using-expo-go Here is stack overflow that explains it.

No problem! Thanks for watching and commenting!

Thanks!

Thanks Frank! I totally agree.

I believe you have to go to the facebook settings and change the settings so you can get more information to access than just the display name and the email. @ 1:57 in the video

@@andrewheimdev Thanks, but why is it only my account that can log in successfully? The other accounts have an error and the application doesn't work?

​@@danhnhanchi6501 I'm not sure. It may not log you out incorrectly, and so only you can log in. You might not have other people's passwords. Is there anything different about the other accounts that you are trying to log in? Might try a friends account instead.

@@andrewheimdev I had to give my friend developer rights before he could log in.

Yeah good question! My understanding is the web app sdk for firebase doesn't work with mobile apps for google login because you have to modify native code (in the ios/android folders). I tried using the google sign in from the web sdk, and kept on getting errors. There might be some work around that I don't know about though!

Thanks! Appreciate it!

Yeah no problem. Can you make sure you don't have your number as a test number? Something else to try is if you already have a google developer account. I would create an app, have google signing for your keys. And generate the sha1 and sha256 key, add it to the firebase google account. Redownload the google-services.json file and it to your app, and rebuild. Check if OTP is in spam as well. Check if your application ID matches with your package-name There could be a lot of things that is causing it, but from looking at some stack overflow, it sounds like a problem with the sha-1 key. And in the tutorial I only get the debug key.

yes, I was encountering SHA-1 issues, but I've already resolved that. now whenever I try, I keep getting an "auth/internal-error" with no additional error details.

@@Canon_gss Hmmm yeah not sure without more details, but make sure you are using a test number. You might be hitting your OTP limit for firebase

@@andrewheimdev yeah, i think so.

@@andrewheimdev I think so firebase stopped the phone authentication support on free accounts. I was using authentication functionality for past 2 years but now it's not working. It shows internal error....

Hi. Thanks for the comment. I'm not sure if it's the same error. But I linked the github thread that solved the problem when I had DEVELOPER_ERROR. I also copy and pasted the keytool line you can put in your terminal to get the sha1 deubg.keystore key in the description I have a feeling you might have gotten the sha-1 and sha-256 that was used for uploading to the android store and not from the debug.keystore. So try that first and see if it works. Also just make sure you have everything correctly configured in your app.json. Also when you get the sha1 key make sure to add it to firebase in your android project, and then redownload and replace your google-service.json file in your root directory

​@@andrewheimdev I wished I could subscribe 1000x, thanks buddy.

@@usmanghaniqureshi1934 No problem!

Thanks! USPS just sent my halo!

No you don't need to! You just need to modify the app.json to change the native code.

No problem! Thanks for watching :)

Sure thing I'll take a look into it!

stackoverflow.com/questions/78516645/warning-deprecationwarning-the-punycode-module-is-deprecated-please-use-a-u I looked into it a bit, and looks like it should eventually get fixed with newer updates, and it doesn't effect the functionality, so I would ignore it for now. But you can use: npm ls punycode to list out the dependencies that are causing the issue in your code.

Thanks! I don't use EXPO EAS Build, so I don't have the best knowledge. But to open it on xcode you would need an IOS folder generated in your local project. That being say you can run: npx expo prebuild --platform ios to generate that IOS folder.

@@andrewheimdev Got it. Thanks!

@@gibber1sh-c6w yeah no problem!

Thanks for the heads up! I forgot to push it up. I just pushed it so it's updated now!

@@andrewheimdev thanks

@@MosesHashim3 no problem!

@@andrewheimdev I’m confused about something. Is this way of login should create a user in my app? Or is there a unique id of each user for my app? I did something similar last week and was able to login, but no user was created in firebase authentication

@@MosesHashim3 Yes it should create a new user in the firebase -> authentication tab. If you want to add more info to the user you would have to setup a way to store it using a database. This setup just creates the authentication. You can check on the firebase console to see if a new user is created as well! And when you login, you can console.log the user data to confirm if they have actually logged in or not.

honestly not sure, if anyone else is reading this, maybe they can tell us

Expo APKs are large (around 60MB) because they include the entire Expo runtime, which bundles many native libraries and features to support a wide range of functionality, even if your app doesn't use them all. This simplifies development but increases the APK size.

@@Babycheeks-xd9mb Thanks!

Going to do apple auth next, and then I'll do a phone auth video

I just posted an otp phone auth video with firebase + expo! Let me know what you think of it!

I'll look into it! Thanks for the idea, might not get around to it soon

firebase.google.com/docs/dynamic-links I just looked into it, and it looks like Deep links (or dynamic links) is deprecated for firebase at least. So if you do use magic links, might have to use a different service!

@@andrewheimdev Yes, I know. That's why it's been so hard finding tutorials on how to implement this today. Thanks for looking into it though!

Oh I see! Thanks for the clarification! Yeah no problem!

Thanks! Appreciate your appreciation. What would you need to use useSession for?

@@andrewheimdev I want to wrap my auth session in my entire app, for example the user signs in then he/she will be able submit or post something on my app under the sign in email or credentials.

I see what you are saying. I don't use useSession. But for your use case I would just use auth().currentUser so something like this: import auth from '@react-native-firebase/auth'; useEffect(() => { console.log('auth', auth().currentUser) }, []) You then have access to all the user info provided. Also I found this stack overflow: stackoverflow.com/questions/57776847/how-to-manage-user-session-in-react-native if you want to manage userSession using a different storage method.