I’m happy to see that Weweb released a new update. However, I also have read many issues in this community regarding this update. So this makes me wonder: how significant are the reports of issues that have currently not been fixed yet?
Do you recommend all users to first thoroughly re-test their apps - for example by duplicating their webapp and deploy it to a Weweb subdomain for thorough testing first? Or something else?
Whatever the case may be, neither do I want to experience any bugs that you may already be aware of, nor do I want to spend unneccessary time testing if you’re confident that there are no bugs that this moment.
Please let us know your - perhaps ongoing - assessment/advise on this!
First, I’d check if the change in editor and preview URLs affects you and update your projects accordingly. All the info you need about this is here.
Then, before pushing changes of existing apps in production, I’d publish to a staging environment and test your app. If you don’t have a plan that allows you to publish to a staging environment, then yes, duplicating the project and publishing it on a free WeWeb subdomain could be a nice workaround but bear in mind that the URLs will be different for the duplicated projects so you may need to update your systems, documentation, or integrations for that project to work properly.
I hope this helps! Please don’t hesitate to reach out if you run into any issues. All the team is all-hands on fixing bugs and supporting you!
Hi @Joyce , thank you for confirming that testing is recommended.
To prevent sudden issues as much as possible, I think it would helps all users if that recommendation was/will be included in the general communication (email and pop-up in the app builder).
