Seems like someone behind the sence has closed most of its “brains”. It fails to perform most easy tasks and repeats same errors over and over agian. I’ve counted the number of successful attempts for today and it’s stands on avarage 1 success every 40 and some attempts. I thought that as the time passes by, those bots will become better and better, but right now, this is the paltform’s weakest side. Very poor coding skills and context skills.
2 Likes
I thought the same until I started watching what it was doing in the console and databases. It will tell you and show the code it used for the backend but when you look at the console nothing will be changed. I have had to manually enable things or change things in the console and the problems resolve.
1 Like
I can confirm. Regression is 80%, 20% crap code
.I’m sorry to hear you’re experiencing those issues. While Firebase Studio (formerly Project IDX) is designed to streamline development, synchronization issues where backend code changes aren’t immediately reflected in the console are a known problem for some users. This can be caused by various factors, including caching, browser settings, or temporary service disruptions.
Troubleshooting Synchronization Issues
* Hard Restart: If Firebase Studio isn’t refreshing properly after a significant code or configuration change, try a hard restart. You can do this by opening the command palette (Cmd+Shift+P on Mac or Ctrl+Shift+P on other operating systems) and running the Hard Restart command. You can also find a “Restart” option in the “More” menu (three horizontal dots).
* Check Browser Settings: Firebase Studio relies on third-party cookies for secure cross-origin communication. Make sure your browser’s settings are not blocking third-party cookies, as this can interfere with how the studio communicates with your backend.
* Check the Firebase Status Dashboard: Before spending a lot of time troubleshooting, check the Firebase Status Dashboard for any reported service disruptions. There might be a temporary issue with Firebase Studio or a specific product, like the Firestore database, that is causing the problem.
* Review Logs and Errors: The console and logs within Firebase Studio are your best tools for debugging. If your backend isn’t starting or is failing, the logs will often provide clues as to why. Look for specific error messages that can guide you to the root of the problem.
* Use the Command Line: If the Firebase Studio interface is not working as expected, you can often achieve the same results by using the Firebase CLI directly in the integrated terminal. The CLI is a powerful tool for deploying functions, managing databases, and more, and it can help bypass any UI-related synchronization issues you may be facing.
This video, Google Firebase Studio In 23 Minutes, provides a comprehensive overview of how Firebase Studio works, including the code editor and troubleshooting, which may help you resolve your issue.
YouTube video views will be stored in your YouTube History, and your data will be stored and used by YouTube according to its Terms of Service
right now you tell it “do not code” a very clear insructions and it decides to just skip that rule. but is very quick to appologise when you point to the issue. i know it is free but this is very bad.
Switch to code environment and you have an option to choose between “Ask”, “Agent”, “Agent Auto-run” so you can choose “Ask” and discuss your next steps before doing anything that will break your app.