Issues with (Sign out user (Firebase Auth)) and Suggestions for Firebase Integration Improvements

By /

Issue Description

Hello, SAP Build Apps team and community,

I’ve been experiencing some challenges with the (Sign out user (Firebase Auth)) component and would like to report the issues while also suggesting a few functionalities that could improve Firebase integration in SAP Build Apps.

  1. Problem with navigation after Firebase Auth Sign Out:
    • When the (Sign out user (Firebase Auth)) component is triggered, the user is successfully signed out (confirmed on the Firebase backend). However, the app does not automatically navigate to the login page as expected.
    • On the web preview, navigation to the login page works as intended, but on Android, after the sign-out, the navigation component does not redirect to the desired page.
    • This forced us to improvise by redirecting the user to a blocking page instead of the login page.

Question: Is there any official configuration or workaround to resolve this issue on Android? If not, could this functionality be revisited in future updates?

Suggestions for Improvements

  1. Enable Firebase SDK on the client-side (JavaScript):
    • While we understand SAP Build Apps already has Firebase integration, allowing developers to use the Firebase SDK directly on the client-side (via JavaScript) would open up many possibilities:
      • Implementing custom authentication logic.
      • Accessing advanced functionalities such as onAuthStateChanged or dynamic Firestore rules.
      • Simplifying the use of libraries like firebase-admin or firebase/auth to address specific issues not currently supported by the native integration.
    • Since SAP Build Apps already supports JavaScript in other areas, integrating the Firebase SDK directly may not be overly complex.

Question: Are there any plans to enable Firebase SDK support on the client side? If not, could this functionality be considered for the roadmap?

  1. Expand support for Firebase Auth persistence on mobile devices:
    • Currently, the (Set auth state persistence (Firebase Auth)) component only works on the web. On mobile devices (Android/iOS), it’s not possible to manage authentication state persistence.
    • This limitation complicates scenarios where we need to log out users or validate sessions dynamically.

Question: Is there any possibility of adding support for Firebase Auth state persistence on mobile devices?

Summary of Suggestions:

  • Review the behavior of the (Sign out user (Firebase Auth)) component on Android to ensure proper post-logout navigation.
  • Consider enabling Firebase SDK support on the client side, allowing for greater flexibility.
  • Add support for Firebase Auth state persistence on mobile platforms.

I would like to know if other developers have encountered these issues and if the SAP Build Apps team has any suggestions for overcoming these challenges or plans to implement these functionalities in the future.

Thank you for your attention and for the excellent work on the platform!

Scroll to Top