I have a crm developed using studio. Everything was working great but since 2-3 days, if I publish the last 30% of version, menus are not updating. Even if I create new menu, it is not getting updated. It is not cache because if I roll back to old version, they get published. I have worked a lot after that version. Any help in this? really in need of it.
Go to code view and run “npm run build” in the terminal. Copy and paste the error message into the AI agent on prototype view. Be sure to end with “explain. Don’t make changes”, so the AI doesn’t go crazy making changes immediately.
dstudio-7971778011:~/studio{main}$ npm run build
nextn@0.1.0 build
NODE_ENV=production next build
Invalid next.config.ts options detected:
Unrecognized key(s) in object: ‘serverActions’
See more info here: Invalid `next.config.js` | Next.js
▲ Next.js 15.3.3
- Environments: .env.local
Creating an optimized production build …
Invalid next.config.ts options detected:
Unrecognized key(s) in object: ‘serverActions’
See more info here: Invalid `next.config.js` | Next.js ✓ Compiled successfully in 102s
Skipping validation of types
Skipping linting
unhandledRejection [Error [PageNotFoundError]: Cannot find module for page: /_document] {
type: ‘PageNotFoundError’,
code: ‘ENOENT’
}
studio-7971778011:~/studio{main}$ npm run build
nextn@0.1.0 build
NODE_ENV=production next build
▲ Next.js 15.3.3
- Environments: .env.local
Creating an optimized production build …
✓ Compiled successfully in 25.0s
Skipping validation of types
Skipping linting
✓ Collecting page data
Automatic initialization failed. Falling back to firebase config object. Error [FirebaseError]: Firebase: Need to provide options, when not being deployed to hosting via source. (app/no-options).
at Q (.next/server/chunks/3280.js:5:32933)
at D (.next/server/chunks/5713.js:2:1074)
at (.next/server/chunks/5713.js:1:8312)
at x (.next/server/chunks/5713.js:1:8307) {
code: ‘app/no-options’,
customData: {}
}
✓ Generating static pages (35/35)
✓ Collecting build traces
✓ Finalizing page optimization
Route (app) Size First Load JS
┌ ○ / 3.07 kB 270 kB
├ ○ /_not-found 992 B 103 kB
├ ○ /about 190 B 105 kB
├ ƒ /api/razorpay 152 B 102 kB
├ ƒ /api/verify-payment 152 B 102 kB
├ ƒ /api/whatsapp-send-test 152 B 102 kB
├ ƒ /api/whatsapp-templates 152 B 102 kB
├ ○ /contact 190 B 105 kB
├ ○ /dashboard 9.82 kB 410 kB
├ ○ /dashboard/attendance/client 7.5 kB 552 kB
├ ○ /dashboard/attendance/trainer 9.61 kB 551 kB
├ ○ /dashboard/dues 2.29 kB 104 kB
├ ○ /dashboard/fitness 9.46 kB 582 kB
├ ○ /dashboard/gym-owners 4.55 kB 314 kB
├ ƒ /dashboard/gyms/[id] 10.8 kB 265 kB
├ ƒ /dashboard/gyms/[id]/members 2.86 kB 588 kB
├ ƒ /dashboard/gyms/[id]/members/[memberId] 8.49 kB 269 kB
├ ƒ /dashboard/gyms/[id]/trainers 2.22 kB 348 kB
├ ○ /dashboard/invoices 1.38 kB 103 kB
├ ○ /dashboard/leads 5.72 kB 326 kB
├ ○ /dashboard/members 2.93 kB 588 kB
├ ○ /dashboard/packages 10 kB 323 kB
├ ○ /dashboard/profile 3.98 kB 255 kB
├ ○ /dashboard/renewals 2.29 kB 104 kB
├ ○ /dashboard/revenue 5.12 kB 414 kB
├ ○ /dashboard/schedule 10.8 kB 343 kB
├ ○ /dashboard/settings 5.25 kB 293 kB
├ ○ /dashboard/subscription 11.5 kB 272 kB
├ ○ /dashboard/trainers 1.87 kB 347 kB
├ ○ /dashboard/whatsapp 9.48 kB 292 kB
├ ○ /fitness-report 53.2 kB 542 kB
├ ○ /login 4.55 kB 280 kB
├ ○ /pricing 8.37 kB 122 kB
├ ○ /privacy-policy 190 B 105 kB
├ ○ /refund-policy 190 B 105 kB
└ ○ /terms-and-conditions 190 B 105 kB
- First Load JS shared by all 102 kB
├ chunks/1684-38c448647b7c2509.js 45.9 kB
├ chunks/4bd1b696-3e0313f6b750e89d.js 53.2 kB
└ other shared chunks (total) 2.51 kB
○ (Static) prerendered as static content
ƒ (Dynamic) server-rendered on demand
Thank you for your response sir.
I got the above error and got it corrected by AI. Now it is building but issue still persist.
What is the specific issue?
After my project was messed once, I learned to make small changes, publish and test, and then continue. If something didn’t work, I’d revert the changes and try again.
I also create a separate branch to avoid messing up my main app.
1 Like
I have built a CRM. I have a sidebar menu in the left side. In my recent version, I have updated that menu. While working on environment, it shows proper new menu but after publishing, in the live url, it is stubborn and displays one old menu. If I roll back to 50% back, it published properly. I have worked a lot after that version. If menu issue is fixed, everything will be solved.
Okay.
Try describing the problem to the AI. Tell it the app behavior before and after. Always end the prompt with “explain. Don’t make changes.”
Also, ask it which files control how the menu is displayed. Then copy the code of that file and paste with an explanation into Grok/Gemini/ChatGPT to see what they say. They might give you some code, which you can paste into the firebase studio AI. Again, always end with “explain. Don’t make changes”
1 Like
Everytime i work on new functions, I ask “don’t work on code, just discuss” before approving the logics. And code part I asked many times where it is wrong, it gives answers but once I ask it to work, it persists again and again.
I’ve found that the Firebase AI can lose context or understanding of all code, so it might correct things that don’t actually need to be fixed.
Try telling it to review all relevant files, and explain what could cause your error.
If that doesn’t work, try copy/pasting all of the relevant files (check the list it provides when it makes changes) into Gemini or Grok. They’re pretty could at coding.
1 Like