Google Login works with WordPress users but does NOT create Firebase Auth users (critical issue)

App Login
1

Hello AppMySite Team,

I’m facing a critical issue with the login system, and I need a clear technical explanation and solution.

Here is my setup and problem in detail:

  • I am using AppMySite mainly as a wrapper / framework to publish a mobile app.

  • The app loads a mobile-only WebView page from my WordPress site.

  • Google Login popup appears correctly (account chooser screen).

  • After selecting a Google account, the user is successfully registered/logged in inside WordPress (wp_users).

  • However, no user is created in Firebase Authentication.

Important points:

  • Firebase project is fully configured.

  • SHA1 & SHA256 fingerprints are added.

  • Google Sign-In is enabled in Firebase Authentication.

  • Service accounts are configured.

  • Firebase Cloud Messaging is already working.

  • The app is correctly linked to Firebase.

Despite all of this:

  • Firebase Authentication → Users remains empty.

  • Login events are not reflected in Firebase at all.

  • Firebase cannot recognize authenticated users, which breaks:

    • User-based notifications

    • Future subscriptions

    • Premium/free user logic

From my understanding:

  • AppMySite Google Login authenticates users directly with WordPress, not via Firebase SDK.

  • This means Firebase is never notified that a login occurred.

My questions:

  1. Does AppMySite Google Login use Firebase Authentication internally, or is it completely separate?

  2. If it does NOT use Firebase Auth, is there any supported way to:

    • Sync authenticated users with Firebase?

    • Or trigger Firebase Auth after successful login?

  3. Is it possible to fully disable AppMySite’s login and use a custom Firebase-based login instead (Google / Apple / Phone OTP) without breaking the app?

  4. Are there plans to support Firebase-first authentication flows?

This issue blocks my entire roadmap, because I need:

  • Firebase as the single source of truth for authentication

  • WordPress users to be created after Firebase login, not the opposite

I would really appreciate a clear technical answer, not a generic setup guide, because all standard configurations are already done.

Looking forward to your response.

Best regards,

and i have paid for max service and support team did not solve or contact me

2

Hey There!

Thank you for sharing the detailed explanation of your setup and concerns. We understand how important this functionality is for your app roadmap.

We checked your case and can confirm that your concern was already escalated to our technical team for a deeper review. Based on their analysis, here is the clarification regarding the behavior you are observing.

Currently, in AppMySite:

  • Firebase Authentication is used only for social login when Native Login is enabled (for example, Google login through the native authentication flow).

  • Manual login via WebView or WordPress login forms is authenticated directly through WordPress, not through Firebase.

Since your app is currently using WebView-based login and native login is not enabled, the authentication happens entirely on the WordPress side. Because of this, Firebase does not receive or record these login events, and therefore users will not appear in Firebase Authentication → Users.

Root Cause
Firebase records users only when social login is performed through the native login flow. Manual login through WordPress or WebView does not create or register users in Firebase Authentication.

Recommended Approach

  • Enable Native Login in your app.

  • Use Social Login (e.g., Google) through the native authentication flow so that users are authenticated via Firebase and recorded there.

  • If you continue using WordPress manual login through WebView, Firebase user tracking will not occur, as the authentication is handled entirely by WordPress.

If you are still facing any issues or need help configuring this setup, please feel free to reach out to our support team directly by raising a support ticket. Our team will be happy to review your configuration and guide you further to resolve the issue.