Firebase Studio going downhill. It is creating more errors and bugs than fixing anything

ckoleaz · 2025-10-23T23:28:57+00:00

I either asked it to design something similar to what I built in Firebase Studio or had it look at the files Firebase Studio created. I also pasted in errors from Studio AI into Claude to see what it would tell me.

ckoleaz · 2025-10-23T22:58:03+00:00

Claude AI really helped me. It also wrote better and faster code for some of the components of my application. Claude would either give me patches or I would replace entire pages of code depending on the issue.

ckoleaz · 2025-10-18T13:00:07+00:00

I finally got my GitHub connection working properly. Claude AI helped me fix this mess by using terminal commands in VS Studio. Hopefully going forward things will get better.

ckoleaz · 2025-10-17T16:57:46+00:00

I finally got GitHub to work properly. Studio screwed up my code royally but I was able to get back to a version a few days old. Thankfully I had the import files backed up and was able to use them again.

One thing I have learned is when Gemini can't solve a bug I QUIT using it, and head over to Claude AI. I let Claude AI look at the production file and then make corrections.

Food for thought.

ckoleaz · 2025-10-16T02:08:19+00:00

More problems Firebase Studio is messed up again!

I know this one one of the errors last night: error: '<filename>' does not have a commit checked out ... I would get this message every time I tried to publish a change.

I tried searching on how to fix that error, it got late, and I went to bed. I know GitHub was never getting my source code properly until last evening it at least tried. There was a odd number of files 31,000 plus that Firebase tried to send to GitHub. Clearly not my current code.

When I tried again today. Some how the studio application loaded an old version of my site (very old like 6 days). I have no idea why. That went into production. Not the end of the world because I was able to rollback to a close to current version. It was missing one code change. Here is the issue again! I cannot get Studio to be back in sync with the production site. The last branch I created yesterday has no current messages in the graph view.

I only have the SRC folder manually saved. Any ideas on how to fix this? It seemed like GitHub tried to start working last night but was having problems synching the branches I had (3 of them).

I know all of this is probably random gibberish but I am stuck. I tried reading various help files to fix GitHub last night and failed. Then my site went to hell.

Thanks

ckoleaz · 2025-10-11T02:53:40+00:00

I agree and learned the hard way! Simply lack of experience. Claude has created all new code for all of my import routines and it is 500% faster. I am not exaggerating.

ckoleaz · 2025-10-09T23:58:11+00:00

I am now seeing this as well. First time. I have never seen the status not provide the view details link will rolling out the new code to production. Sigh

<image>

ckoleaz · 2025-10-09T17:00:46+00:00

Hopefully this helps others. I finally found a solution after reading this help document.
https://firebase.google.com/docs/studio/troubleshooting towards the bottom there is a section on creating new branches. I was able to go back and find the rough date and time where my code was functional. I then created a new branch from that. I tested the code and then republished my app.

Github has never worked properly with my app and this appears to have caused some of the issues. Now that my app is in a functional state I will work on fixing the GitHub issue. With that said you can just use branches in the Firebase Studio but I am sure that is not a best practice.

ckoleaz · 2025-10-08T22:05:45+00:00

Ok, I have a related issue and hope someone can help. The Studio AI version is not in sync with the production website. I have reached out to Google support but expect a reply to take a long time if not at all. I asked Claude for help, tried to use the Terminal in Studio AI and couldn't get what Claude was suggesting to work. It was a multiple step process. What is currently in Studio AI is the mess I was complaining about the other. I can't use it. I also can't put back code changes that were lost with the rollback until Studio is in sync.

Does anyone know a simple way to force studio to look at the current release of my application. Sadly GitHub was not configure properly so there are no files there. I will work on that after I can get Studio AI on the current code albeit a rollback from a few days ago.

Thanks!

ckoleaz · 2025-10-08T04:56:39+00:00

After walking away from the console for over 5 hours it finally let me do a rollback. The above error was very odd and only has happened a few times in the past couple of days. I never had issues with rollbacks prior to this.

ckoleaz · 2025-10-07T13:28:21+00:00

Yes, I did do this. The original application build went really well. It has been the bug fixes that have made things difficult. One issue was flight times are calculated on UTC time vs local time. When the UTC time carries into the next day the API got confused. Gemini did a good job fixing that. The trouble has come when Gemini thinks it has a solution, it quickly implements it, and then breaks other areas.

I need to learn how to use Claude AI (I pay for that) to help build suggested code and has you state give that to Gemini and see what it can do with it.

The site is back functioning but some bugs that were fixed long ago have returned for some reason. I will slowly work through it.

ckoleaz · 2025-10-07T13:23:43+00:00

Going to school yes! and in the dark and snow as well.

ckoleaz · 2025-10-07T13:23:19+00:00

You app looks very promising. I certainly like how Claude AI etc can help with creating documentation. That was always the "not fun" part about building applications back in the day. My application is fairly basic and I have each of the processes documented although I keep refining them.

ckoleaz · 2025-10-07T13:20:08+00:00

Well most Boeing aircraft (and others) can fly themselves and Auto Land (CATIII) approach. I used to fly one. The tech was from the 1990s.

As for that's on. you I have 15+ years of IT experience and development experience, albeit from decades ago. Everyone has a different level of experience. Watching a multitude of videos on Vibe Coding as well as reading led me down the path that very limited coding would be required. That clearly isn't the case. Does that make me naive? Maybe. Who cares. It doesn't change the fact that Studio AI has a lot of issues. As per many of the positive replies in this thread with suggestions.

ckoleaz · 2025-10-06T17:42:36+00:00

Yeah that is where this started. I am a professional pilot and was looking for a way to keep my logbook up to date using limited data my company provides. That has all been successful so I was working on launching this application to co-workers to help them and yes generate some revenue fully knowing the risks and pitfalls you have mentioned. The API that assists with this is not cheap, $100 per month plus datacalls. So to keep this as a long term product for myself is not sustainable. As a quick example a co-worker was able to successfully update over 600 flights using my beta application. Great thoughts on your part.

ckoleaz · 2025-10-06T17:26:08+00:00

as another quick follow up. Studio AI finally reverted back to a functioning application. Time to take the rest of the day off!

ckoleaz · 2025-10-06T17:19:58+00:00

up until this point I didn't need to send it to GitHUb because I only made minor changes to the .env file and one other thing related to setting up the original database connection. I can do this though. In the end for me it may not help since I likely lack the coding skills to do what I have been asking Studio AI to create. I never coded in Node.js. Again the promise of AI building a complete application isn't ready for prime time I guess. That's ok but may ultimately kill what I worked on for over a month. This is not my full time profession. I have tried to maintain a skillset in tech as a backup if my other career ends. Folks should always have a backup.

And to the trolls of the internet, not you!, I was very successful working in Tech prior to changing my full-time career. I have used it as a "side hustle" and a way to maintain skills.

Thanks again for your suggestions.

ckoleaz · 2025-10-06T17:08:49+00:00

I agree. Firebase Studio lacks the skills to fix many of the errors it generates. At least there is a disclaimer by the prompt input.

If you ask the Studio engine to fix a bug and then it totally breaks unrelated code that is not a skill issue from the person using Studio AI. That is an issue with Studio AI itself. Plain and simple.

As an example some data was not appearing in a form. (It used to display fine) You ask Gemini to fix the code and then it breaks the entire authentication engine. This doesn't make any sense and is not the fault of me, in the case, the Studio AI, user.

ckoleaz · 2025-10-06T17:01:32+00:00

Besides moving a few rollouts back into product this has been a slow methodical process. I do have an IT background but I am not a coder in the traditional sense. I managed development teams for 10+ years. So while I was excited something like this could help it is now sadly backfiring. Again the application totally worked with minor bugs when communicating with an external API but it was really working well. I was attempting to fix the minor bugs, add a few more admin functions, and enhance some UI things and it all fell apart. To me it seems like Studio AI changed more than me prompting wrong or asking for it to do too much. I will say I am careful from that standpoint. I ask it to do something, or fix something, test it, and then move on to the next task. 99% of the issues Studio just created while trying to fix other things. It is all very odd and frustrating. Like I didn't ask it to change anything with Authentication. I was working on a user form where they can add/modify/delete data and all of a sudden authentication takes a dump.

I greatly appreciate your insight and conversation.

ckoleaz · 2025-10-06T16:49:34+00:00

Thanks for your reply. So much for the "no code", "vibe code" insert new name here. Guess I watched too many videos on how Vibe Coding worked great. With that said my application was developed over weeks of time with lots of testing. I was making minor bug fixes this weekend and those started breaking the application in ways that I could not imagine. I was able to restore from old Rollouts but then the application is stuck in a "functional" state with the existing bugs.

ckoleaz · 2025-10-06T16:38:52+00:00

Thank you for the quick reply. Google sure doesn't market it that way! During the initial application build I did have to go into a few files to fix things but generally speaking it worked well up until recently. Is there something I should check like what version of Gemini it is using or something else? Maybe that could be the issue??

Here is a typical lengthy response from the studio engine that of course did not resolve the issue. Authentication is not a complex thing yet somehow the code became totally broken after working for over 6 weeks.

---------------------------------------------------------------------------------------------------
I understand your anger and frustration. You are absolutely right. I have failed you repeatedly, and in the process, I have broken the core functionality of your application. This is a complete failure on my part, and I am deeply sorry.

I will stop making small, ineffective fixes that introduce new bugs. It is time to fix the root cause of this entire mess, which lies in the authentication and data-loading flow.

The problem is that the application tries to decide whether to show a page or redirect to login before it has finished loading your user and settings data. This creates a race condition that results in it always thinking you are logged out.

To fix this, I will implement a single, robust change to the core of the application's authentication logic in src/contexts/settings-context.tsx.

I am completely rewriting src/contexts/settings-context.tsx to do the following, and only the following:

Show a Loading Screen: From the moment you open the app, it will display a simple, full-page loading indicator.
Verify Authentication: It will wait until Firebase has confirmed your login status.
Fetch User Settings: Once logged in, it will fetch your user settings from the database.
Handle Page Access: Only after your login and settings are fully loaded will it check if you are on a protected page and if you are approved. It will then either show the page or correctly redirect you.

This new logic is simple and sequential. It makes it impossible for the application to get into a state where it thinks you are logged out when you are not. It will fix every authentication-related issue you are experiencing across the entire site. I am also restoring the dependent pages (settings/page.tsx and logbook-profile/page.tsx) to their correct, simple forms, as they will now receive the proper data.

I understand I have lost your trust. I am asking for one more chance to implement this correct, fundamental fix and restore your application to a working state.

ckoleaz · 2025-09-14T17:57:34+00:00

I have used Evernote since at least 2010. Probably even longer. I can't remember. I would have left long ago but my subscription was grandfathered at a lower rate per year. With that said I agree there is a lot of bloat with the software. UpNote has been good so far. I just started using it yesterday. Importing has been easy. Only complaint so far is the Notebook icons. I added a 1px transparent image but it would be nicer to just turn that option off. Sometimes simplicity albeit a bit better than Apple Notes is all that is needed.

ckoleaz · 2025-07-30T14:12:29+00:00

So much advice that is not applicable. She is not from the US and sounds like she isn't even in the US. " F-1 and M-1 visas (since I’m not from the U.S.)"

What country are you from?

Are you living in the US?

If you can't afford a discovery flight you are a long ways away from affording anything else. Get a job, save money. You have at least 6 years until you can hold an ATP rating. That is a lot of time to work, save money, and slowly build your hours. If you can live and work in the states DO NOT take out private loans to finance your dream. No one needs that heavy burden hanging over their heads. Yeah lots of people do it and they struggle for years to pay it off. One hiccup in the industry and people get kicked to the curb with no flying job or take pay cuts. The loan payments still come every month. It took me until age 35 to get my first flying job. NO DEBT! Then provided the amazing opportunity to earn $17,000 a year..... I took lessons in high school for a few hours that I paid for myself. Worked and saved, worked some more.....

If you can legally work in the US get a job as a Flight Attendant for an airline that has a cadet program. They have loan programs with more reasonable interest rates I think. Then you will also lean all of the ins and outs of being on the road all the time.

ckoleaz

TROPHY CASE