You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a project writing to Firestore. Didn't work in production mode, but initially worked in Test mode. It created a seed script to create some collections and I could read/write to them. Then I tried to add more collections, and Bolt has been running in circles never able to fix the seed script as now it never manages to connect to firebase. Keeps on trying .ts then.js then admin and starts again... Weird because it once worked...
Appreciate the feedback! At times, there are programming challenges that are too difficult for the LLM to solve and manual intervention is required. More information on using Bolt most effectively can be found here.
I understand, but weirdly I had the most problems with things that should be relatively standard : seed, read/write to firebase, and firebase authentication. Flutterflow is way less cool to automate writing code, but setting up firebase and easily creating a full UX and workflow for authentication is a breeze. That would be a huge + with Bolt... I wasted all my Pro tokens in a few hours just on this...
Describe the bug
I created a project writing to Firestore. Didn't work in production mode, but initially worked in Test mode. It created a seed script to create some collections and I could read/write to them. Then I tried to add more collections, and Bolt has been running in circles never able to fix the seed script as now it never manages to connect to firebase. Keeps on trying .ts then.js then admin and starts again... Weird because it once worked...
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-jerfnt
Steps to reproduce
npm run seed
Expected behavior
I can read/write to firestore, but expect the seed.ts script to create a new collection which always fails connecting to firestore...
Screen Recording / Screenshot
No response
Platform
MacOS
Additional context
none
The text was updated successfully, but these errors were encountered: