Please has anyone encounter this failed published of app? The isn’t no specific error to what could make the app fail to publish, the response error is generic and kind of confusing what exactly is the issue. I have use the model to check all angel, which the model have done it check to possible reasons to why it could failed, the model has tend to exhaust all options of fixing possible loophole that could cause failed app published yet we still haven’t had a breakthrough. I have left the project for more than 10hours to try again, still no luck. Please what do be done in this regards. ? I will appreciate your great help thank you.
Hi @Mikeyoungdya2 ,
Can you go into Google Cloud Platform’s Cloud Build and view the log in your History tab? It should tell you exactly why it failed. It’s usually due to an error in your code.
Hello @dms thank you so much for always stopping by to share your support I hold you a grateful heart of thanks. Meanwhile, I had to use the alternative means of publishing the app via the terminal command. This is where I was able to decode the exact issues which is what am working with the model to see how we can fix it.. the problem happen to be a Firebase trying to export a static site where as my app is dynamic, this causes the deployment to failed. We are still on it trying to fix the issue.
The error ENOENT: no such file or directory, open '.../.next/export-marker.json' is definitive. It means the Firebase deployment process is trying to deploy a static website, but my application is dynamic and needs a server. This is a fundamental build configuration mismatch.
The problem lies in the package.json file. The build script is not correctly instructing Firebase on how to create a dynamic server build.
Actually the model has been struggling to resolve this. What do you think @dms