Fix Google Auth for app

@AhteshamAK

Hello! I’d be excited to help you fix the Google Auth issue in your Lovable‑built Android app. The error you’re seeing, “Google sign‑in failed: [16] Account reauth failed,” typically points to a configuration mismatch between Google Play Console, OAuth settings, or signing keys. I can diagnose and resolve this so your sign‑in flow completes smoothly, returning the correct user profile without fallback to guest mode. I’ll ensure compatibility across all modern Android versions and work with you through a quick TestTrack update so you can verify everything before going live. I’ll keep explanations clear and patient, matching your comfort level throughout the process. Best regards, Ahtesham

@WebTechDesignBG

Woah Hello, It looks like you're dealing with an annoying issue with Google authentication in your Android app. You need a fix for the "Google sign-in failed: [16] Account reauth failed" error so users can log in smoothly and access their profiles. I get that it's frustrating, especially when technical skills aren't your strong suit. With 7+ years of experience in mobile app development and API integration, I've tackled similar issues before. I would start by diagnosing the authentication flow to identify the root cause of the error. Then, I'll implement a solution that ensures compatibility with all current Android versions. After fixing it, we can do a quick TestTrack update to verify everything works as expected before going live. Looking forward to helping you resolve this issue! Best regards, Ivan Mandinski

@GintarasZelvys

Hi. As an Android Expert, I can fix Google sign-in. I am very familiar with Lovable and Google sign-in. I have mobile and backend skills with 8+ years. I wish to work for you. Thanks for attention.

@waqaswebmaster

Hi There I can help diagnose and fix your Google Sign-In issue and make sure the login flow completes properly inside your Android test build without errors or guest fallback. I understand these problems usually come from OAuth, SHA certificate, Play test config, or Firebase setup mismatches, and I can work through them carefully with you in a simple way so testing stays stress-free. I’m comfortable handling TestTrack updates and verifying the fix before production so you know everything works correctly on real Android devices. Are you using Firebase Authentication for Google login, or a custom backend setup behind Lovable? Best Regards Waqas Ahmad

@arbu1499

Hi, I can help you fix the Google Sign-In error in your Lovable Android app so that users can log in smoothly without any fallback to guest mode. I have experience diagnosing authentication issues across Android versions and can walk you step by step to ensure the login flow returns the full user profile as expected. We can test the fixes together on TestTrack before pushing to production to make sure everything works perfectly. Looking forward for your positive response in the chatbox. Best Regards, Arbaz T

@FizzaNadeemK

Hi, I can help you resolve the Google Sign-In issue by diagnosing and fixing the "Google sign-in failed: [16] Account reauth failed" error. I’ll ensure the login flow completes successfully on all Android versions without falling back to guest mode. I’m happy to guide you through a quick TestTrack update so you can verify the fix before pushing to production. When would be a good time for us to start troubleshooting together? Best Regards, Fizza

@mutahrar

Hello, I am an experienced Android developer familiar with Lovable and Google Sign-In integration, and I can resolve the "Google sign-in failed: [16] Account reauth failed" error for your closed test app. This error almost always occurs because of a SHA-1 fingerprint mismatch after Google Play re-signs your app with its own app signing key when users download from the Play Store . The fix requires updating your Google Cloud Console OAuth client with the correct SHA-1 certificate from Google Play Console. I will guide you through obtaining the App Signing Key SHA-1 from your Play Console's "App Integrity" section, then add it to your existing Android OAuth client credentials. After updating, I will also ensure your Lovable app's configuration includes both the Android client ID and the server client ID (web client) for proper authentication . We can then test the fix through a TestTrack update so you can verify the login flow works perfectly before any production release.

@ayesha86664

Hi there! I see your Android app’s Google sign-in is failing with the “[16] Account reauth failed” error, which stops users from logging in. The main goal is a smooth login flow returning the user profile correctly on all devices. I have experience fixing Google Sign-In issues in Android apps built with Lovable and other frameworks, integrating OAuth properly, and debugging authentication flows. I’ve resolved similar errors by checking SHA keys, API credentials, and Android client configurations to ensure reliable login. My approach will diagnose the error, update the Google API configuration if needed, and test the sign-in flow across current Android versions. I’ll also guide you patiently through verifying the fix in your TestTrack environment before production release. check our work https://www.freelancer.com/u/ayesha86664 Could you share whether the app is using the default OAuth credentials from Lovable or a custom Google API project? Let me know if you’re interested & we can discuss it. Best Regards Ayesha

@seandinwiddie

Hi, I’ve reviewed your project details. I understand that you need the Google Sign-In in your Lovable Android app to work smoothly so users can log in without errors or fallback to guest mode. In my brief, carefully diagnosing the “16 Account reauth failed” error and fixing the 404 or configuration issues would ensure the login flow completes reliably and returns the correct user profile. I’ve got experience with Google authentication, OAuth integration, and Android debugging, so I can pinpoint the problem efficiently and guide you through each step in simple terms. Let me help your project with my passion, and I’ll do my best to make the sign-in flow seamless and fully functional. Sean

@mahads31

Hi, I took the time to review your project and it’s clear that this is completely doable with the right development approach. I have strong expertise in API Integration, JavaScript, Mobile App Development, App Development, Android App Development, Android SDK, Android Studio, Android, PHP and Mobile Development and specialize in building efficient, modern, and scalable web solutions. My work focuses on clean development, responsive design, optimized speed, and a user-friendly interface to ensure everything runs smoothly and professionally. I’m confident I can deliver a high-quality result that meets your expectations. Best regards. Mahad Sheikh

@ahmetTC

Hope you are doing well! Lets start! The issue described usually occurs due to OAuth configuration mismatches, incorrect SHA-1 fingerprints, misconfigured Google Cloud credentials, or Play Console test-track authentication restrictions that cause the “[16] Account reauth failed” error during Google Sign-In. Extensive experience resolving Google authentication problems in Android apps published on Google Play, including apps running closed testing tracks and using Firebase or Google Identity services. In previous projects, sign-in failures appeared because the production SHA-1 from the Play App Signing certificate was missing in Google Cloud Console, which was resolved by properly linking OAuth credentials and updating the configuration to match the Play signing keys. Another common issue involved redirect URI or client ID mismatches that caused authentication errors across different Android versions, fixed by reconfiguring the OAuth client, updating the app configuration, and validating the sign-in flow across test devices. Support also included guiding non-technical clients through TestTrack updates and verifying login success before production release to ensure smooth deployment. I know what do I build for you, can complete it to your full satisfaction within your timeline. I am ready for you and waiting here. Thank you.

@johnedwardl

Hi, I will diagnose and resolve the "Google sign-in failed: [16] Account reauth failed" error in your Android app. With my extensive experience in Android development and authentication integrations, I’ll ensure the sign-in flow completes successfully across all current Android versions. I have previously tackled similar issues, streamlining authentication processes and eliminating error messages. My approach will involve reviewing your current implementation, checking the configuration in the Google Developer Console, and ensuring your app's dependencies are aligned with the latest standards. This will allow for a seamless user experience without fallback to guest mode. To expedite the process, I suggest we set up a quick TestTrack update for you to verify the fix before deployment. Let’s get this resolved swiftly so your users can access their profiles without issues. Thank you.

@qadeerDev

Hi there, I can resolve your Google Sign-In error [16] in less than 24 hours. As an experienced mobile app developer, I have dealt with this specific authentication issue many times—it usually stems from mismatched SHA-1 app signing certificates between your Google Play Console, Firebase/Google Cloud, and your Lovable build. Since you mentioned your technical skills are limited, please do not worry; I will patiently guide you through exactly where we need to grab those keys, or I can handle the configuration entirely for you. I will properly align your OAuth client IDs so the sign-in flow completes successfully without returning a 404 or forcing guest mode. I completely agree with your workflow and will push the update to your closed TestTrack first, ensuring you can personally verify the fix on current Android versions before we touch production. Let's connect and get your authentication working flawlessly today!

@nguyenphuclam06

Hi there, I’m Lâm, and I’ll diagnose and fix the Google Sign-In flow for your Lovable Android app so users never hit the Account reauth failed error. I’ve worked on Android authentication, OAuth integration, and Play Console test tracks, and I know how to align SHA-1/2 keys, package names, and OAuth client IDs so sign-in returns a user profile every time, across modern Android versions. What I’ll deliver ✔ - Targeted diagnosis of the 404 sign-in issue across current devices and Android versions. - A robust sign-in flow that completes without errors and never falls back to guest mode. - A test-friendly patch you can push to a TestTrack branch for quick verification before production. - Clear, minimal changes with full in-code comments and step-by-step rollback options if needed. Why me? I match the project’s tech stack (Android Studio, Java/Kotlin, API integration) and communicate clearly with non-tech stakeholders while keeping you informed at every milestone. I’ll be available for quick chats to review results and adjust as needed. What is your current Google OAuth client ID setup and SHA-1/2 configuration, and can you share the exact error stack trace from the TestTrack run? Best regards, Lâm

@sadam61

Hi, I understand the urgency of fixing the Google authentication issue for your Android app built with Lovable. With over 9 years of experience in mobile development, particularly with API integrations, I am confident in diagnosing and resolving the Google Sign-In error you are encountering. I've successfully tackled similar login issues in the past, ensuring smooth sign-in flows for users across various Android versions. My approach will involve debugging the current implementation to identify the root cause and implementing effective fixes to ensure the login process completes without errors. I can start immediately and will keep you informed throughout the process. We can conduct a quick TestTrack update after implementing the fixes, allowing you to verify everything before pushing it live. Best regards, Sadam

@oleksandrp60

Hi there Do you have access to the Google Cloud Console project where the OAuth credentials are set up, and do you know which Google account owns it? Was the app signed with a debug keystore or a release keystore when uploaded to Google Play, and do you have the signing key file available? Error 16 is almost always a SHA-1 fingerprint mismatch between what Google expects and what the app is signed with. Once I confirm the correct fingerprint I can update the OAuth client in your Google Cloud Console and the sign-in flow should work immediately. Happy to walk you through each step patiently. Best Oleksandr

@dorofiip

Hello there What is causing the persistent Google sign-in error 16 and how have you configured OAuth credentials for your app in Google Cloud Console? Are there any specific Android versions or device models where the sign-in fails differently? Google authentication errors often stem from OAuth misconfiguration or token validation issues. Handling the sign-in flow properly across Android versions requires careful API integration with Google SDK. I will carefully review and fix the Google sign-in implementation ensuring it returns user profiles as expected without fallback. We can proceed with test updates on TestTrack for you to confirm fixes before production rollout. Best regards. Dorofii

@Ramanov6

⭐⭐⭐⭐Hi, I am a Full Stack Developer with strong experience in Android app development and backend integrations. I can diagnose and fix the Google Sign-In error so that users can log in seamlessly on all current Android versions. Could you confirm if the app uses Firebase for authentication, or is it purely through Google API? I will ensure the login flow returns full user profiles without errors, and we can test it together on TestTrack before production. All code and configurations will be carefully handled for stability and security. I am confident I can resolve this issue and make the sign-in work perfectly. Best,

@matheussilva114

Hi, I have checked the details. I am a senior engineer with over 7 year of experience on PHP, JavaScript, Mobile App Development, Android, Mobile Development, Android App Development, App Development, Android SDK, Android Studio, API Integration. Please visit my profile to view my latest projects, certificates, and work history. Let's connect in chat to discuss more. Thank you, Matheus