Has anyone else has trouble publishing their app today? Wondering if this is specific to something in my app or a wider thing
Getting this error - CODEBUILD_FAILED. I was able to publish yesterday, but even previous builds from yesterday that were publish-able are failing now, so AFAIK it’s a newly developed incompatibility, and not from something that I added recently.
Also wondering, does anyone know how the WeWeb support tickets work? I have filed them in the past and noticed that they will appear in the queue (confirmed successfully created) and then disappear a bit later. Usually when they disappear, the issue has been fixed, but in this case, it disappeared and things are still broken.
Was wondering if the disappearing ticket means it has been assigned or even just opened by someone on the other end?
Interestingly, I am able to publish one of my other projects successfully. Having seen that, I iniitally thought I must have broke something in my failing project.
But now seeing your post, I took another look at the console. In the failing project, I see there are a couple errors about deprecated components.
In my other project that is publishing, I do not see these errors. Notably, this other project is brand new - I created it 2 days ago. So maybe these deprecated components in the older project is what’s causing it to fail?
The team is looking into this. Thanks for bringing it to our attention!
@khara, tickets should only disappear once they’ve been resolved or archived. They can be archived without being resolved if we asked for more information but didn’t receive an answer for a couple of weeks. There’s room for error though so it’s possible, a ticket is tagged as resolved or archived by mistake. Or, if one ticket is linked to another, there could be some confusion as well. We’re currently working on a v2 of the support app to make things easier to follow and more user-friendly.
We have resolved the issue, and you can now republish!
The problem originated from the rich text component, which relies on a library called Tiptap. A recent update introduced an error in the version we were using. We have upgraded to the latest version, and the component is now functioning correctly.
We apologize for any inconvenience this may have caused.
Thank you very much for your response. You are excused… I have been a programmer for 10 years and I know these situations happen. The important thing for us customers is to know that we have a Weweb team readily providing support for us.
I have been testing Weweb for less than a month and I am very excited about the results. Congratulations to the Weweb team.
Thank you so much @Joyce and @flo for the fast help! We appreciate you guys so much!! Thank you for always being responsive to your users
Re: support tickets - very useful to know! Guessing then that many of my tickets are probably getting labeled as duplicates of existing ones (widespread bugs)