You can see the image, "Build archive was not created", even though build ran fine
Hey <@257295349314486273>, here is the thread
<@287294735054274560> can you take a look at this and see if it's something on our end or something?
heyy <@1077084035274248282> π Most commonly I see this error coupled with crash, and exit code hinting over-usage of memory. Let's try that, as initial solution. Please try to increase specs in settings to highest memory, and redpeloy. See if that works. If yes, you can try to pin-point which specs is enough, while still costing as little as possible
(dont worry, only 1 build will be charged at max specs, so usage should be barely affected)
But I am on free plan π
Interestiiing π€ Ill see if raising limits could make sense. Out of curiousity, would you say your website is small / medium / large?
the codebase size is around 2mb and with public assets it extends to 7mb. so you can say small-medium
I will be making quick patch to enforce slightly higher memory limit for builds, until we get better understanding of how we want to solve this long-term. This is good news for you - builds will start to work, and you can remain on free plan.
Recommended threads
- GB Hours IS NOT resetting
Hi, I was checking my usage and noticed that all of my usage quotas were reset on August 20, 2026, when my billing cycle renewed. Everything else appears to ha...
- Confused about Appwrite Pro pricing
Hi. I've been subscribed to the $25 Appwrite Pro plan, but I've been getting charged $40. I have two projects on my account. I was wondering where exactly the e...
- Custom domain for Google Auth
Hello! I connected my custom domain to my Appwrite project, but I can't get the Google login/consent screen to show my domain instead of the Appwrite domain. I...