Seriously, this platform works against you by any mean. A storage service should connect to the app in maximum 30 sec. of work. I’m trying to connect my app to the storage for 3 days! 3 days, without results. the ai make you go in circles at a loss for advice, appologies ziollion time for more and more repeating errors and the damn thing is just rfuses to connect. I wonder what google wll do when masses of new comers will come to the platform and got clashed into this storage wall. Why even developers make 90’ tier solutions in 2025? seriously using power shell? this thing could connected faster with 2 cans and a wire. If google will not find a solution for that, it will loose the entire point of selling integrated services. Anything you would expect from a firm with that size. A dinosaur.
sometimes the ai do complication to himself without even recognize he did this , in my case i keep asking the ai questions and questions about the reasons of any problem and ask him not to change any code without my confirmation , the most important thing you should do and this is what i do , i duplicate the project and download a backup of the entire files every while and before i give him a complicated coding implementation or feature . then simply if a problem occurs i inform the ai that i have a back up and ask him which files of the app you may require to solve the issue , he tells me which files and i copy it to him in a folder i create in the root then he takes what he need for the fix , and guess what most of the times it works fine .
I ended up hosting my app on Vercel because firebase hosting was a headache with the yaml file and such. I don’t use backend storage, so I don’t have that trouble. Google needs to figure something out to simplify it.
I also ran into an issue trying to connect my app to storage, with the AI trying fix after fix. Eventually I realised that storage had to be enabled in Firebase Console, which in turn enables the cloud platform APIs. The AI then helped me write rules for the storage in Firebase console, and we got it working. I think one of the issues is that the prototyper AI does not have knowledge of the some of Firebase console setup and configuration, so can spiral into endless loops of incorrect fixes.
The AI basically doesn’t know a lot about Google’s own Firebase Storage and Rules and Policies. It does not even know that when it create a .rule file, it doesn’t tell you that you have to copy that to the Firebase database rules. It assumes you know it which is a huge disconnect if you aren’t familiar with how Firebase work.
after i finished my project which i worked on for 1 month and this is a long period for vibe coding suddenly the project stuck and i cant even get the error to track i do nt know where is the problem
At first i got the same error , then i tell ai to give up , then i wait 30 mins and tell ai to try again and it works