Project appears to be dead #1015
Comments
|
Hi @bojeil-google you've been very helpful on a few issues I've raised on this repository in the past, I realise you've probably moved on to a different project at Google now but wondering if you know if this library is still being maintained? |
|
Also, the warning in the google documentation that says that this plugin is not compatible with the v9 modular SDK and not plans to migrate, make me think that Google does not care about this. Maybe is better to archive it. Pretty sure that there are voluntaries open to take it. |
|
Is there any open or commercial alternative to this project that provides a firebase web ui which is compatible with the v9 style? |
|
It feels awkward that the first section in Firebase Auth documentation is "Sign in with a pre-built UI", which is positioned even before "Get started", as if that was the best way to go in 2023. It seems kind of disheartening (as a paid Blaze plan user) to go through wanting to follow Google's recommendation and use a "drop-in" solution, only to read it's currently compatible with v9 only via a compat layer, and later finding out through the community and github that the project isn't receiving any attention anymore and serious issues are left unanswered. |
|
The project is inactive for years. The firebaseui can be a great reference while migrating your work. I am amazed by the details it take care of. It is a great pity the project is dead. |
|
Hi @kroikie any update here? |
Not to pile on here but I think it would really be helpful if whoever is maintaining the docs site could just edit that side nav menu as this comment mentions: 
I understand that later on the UI page ("Sign in with a pre-built UI") you have this: 
But it's not really clear what that means at first, and given the nature of Firebase and the fact that "Sign in with a pre-built UI" was first in the list (above "Get Started") it's easy to just ignore that and start diving into getting Firebase UI to work, before realizing that isn't really tenable. I hit numerous issues that are already mentioned yet unresolved in this repo, as others here have mentioned. Furthermore it took me a while to find this issue, previously I just thought I was making error after error especially because there exists in the community answers like this : https://stackoverflow.com/questions/51311067/firebase-auth-ui-not-working-in-web - which lead one to believe (in concert with your docs that endorse this repo as the first step in setting up Firebase Auth on the web) that Firebase UI is the way to go. I finally almost got it to work before hitting another error re "updateUser" or whatever and then finally found issues that made it clear this ui repo is not being maintained in line with the main firebase version/repo. I just hope you can remove it or reorg from the docs because it makes people waste a lot of time in nearly end of 2023 now if it's no longer really supported you would save people needless pain and also clarify the situation by cleaning up the docs. Thanks! |
|
Dead project here? Honestly curious to know so I can stop using it and migrate to something else. They need to get the documentation for this off the web since it doesn't work and will waste many hours of people's time if they try to integrate it. It's really a mess too since the requirements of all the login providers change from time to time, making it a constant game of Whac-A-Mole. Not recommended to use it if people don't need it. A simple login with email is probably least likely to cause issues for smaller projects. Here is the documentation for this UI still up, although it appears to be broken: https://firebase.google.com/docs/auth/web/firebaseui?hl=en Is it dead or not? I guess if we don't receive answers we should just assume yes, but then what is that documentation doing up? Just trying to save people some time here ... |
|
Im hoping that because Google continues to allow firebaseui to be linked to
from all the official firebase auth pages, that this means Google has plans
to reinvest into this project in some way that gives us all a path forward.
We need that path forward too, because we’re using firebaseui in
production. It is working well but we don’t want to have to spend
significant resources to migrate away.
Tim Carr
Founder, *Solodigitalis*
M: 289-237-1935
W: solodigitalis.com
A: 270 Sherman Ave N, Hamilton, ON L8L 6N4
…On Sun, Jan 28, 2024 at 1:29 PM Casey10110 ***@***.***> wrote:
Dead project here? Honestly curious to know so I can stop using it and
migrate to something else. They need to get the documentation for this off
the web since it doesn't work and will waste many hours of people's time if
they try to integrate it. It's really a mess too since the requirements of
all the login providers change from time to time, making it a constant game
of Whac-A-Mole. Not recommended to use it if people don't need it. A simple
login with email is probably least likely to cause issues for smaller
projects. Here is the documentation for this UI still up, although it
appears to be broken:
https://firebase.google.com/docs/auth/web/firebaseui?hl=en <http://url>
Is it dead or not? I guess if we don't receive answers we should just
assume yes, but then what is that documentation doing up? Just trying to
save people some time here ...
—
Reply to this email directly, view it on GitHub
<#1015 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA4Z6LW55XSIE7DIC7X6M5DYQ2KJZAVCNFSM6AAAAAAWE23XNWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGY4DGNRTGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
I recently received an email from Firebase with the subject: [Action Advised] Enable email enumeration protection on all of your Firebase projects It details...
Issue 1 and 2 are #1040 and #1041 on this repo. So again Firebase is maintaining public documentation and sending out communications as if this project is supported, but it still appears dead. @jhuleatt you've made some helpful comments on those issues, are you able to comment on the future plans for this project? Thanks in advance. |
Various issues triaged as bugs have languished for nearly a year, the only code commits in the last year are dependency updates.
Is this project actually dead?
The text was updated successfully, but these errors were encountered: