I find that web deploys are much quicker now. Usually within 1 to 2 hours. I have noticed that if you do more than one build on the same day the second (or later) build takes 24 hours before it appears.
Ahhhh. Yeah, reproduced that now, we’ll get to fixing that next week hopefully. Thank you for letting us know!
@Mevi Hi, I have started a web build 5-6 hours ago and it seems to be still in queue? Is there some ongoing error?
@Mevi there seems to be so error with the build system - 16 hours later the build status is still queued…
Hi! Not sure what went wrong with your build, but I marked them as errored now. I queued another build, let’s see if this one goes through, but I’ll have someone have a look if it doesn’t.
The previous 2 have failed
I have started a new one.
Yep, I failed the previous two manually. We are investigating the issue, sorry for the trouble and that I can’t do anything further for you until we find out what’s going on
That is a bit of a snag indeed… I was very excited to test the new build. Anything I can fix or debug?
We’re continuing to look into this, there are some things we are testing as fixes and rolling out as soon as we can confirm they work. This isn’t a widespread problem, but there’s something specific about your app which is encountering a problem when it’s built – without knowing your app more, it’s hard to say what exactly it is Hopefully this’ll get sorted today, I’m sorry it’s such a hassle and you’re having to wait. You can continue working on your app using the Preview, if there’s still more you’d like to do.
@Mevi if this is something that I have broken inside the app it would be great to know what, so that I can fix it. It doesn’t make sense for me to be changing anything in the app now , if I don’t know if this is going to make problem worse.
Previously your build errors were having some log attached, I don’t see it anymore?
Yep, that’s correct, but currently your errors are only me manually setting the status of the build to errored, as they don’t, in fact, fail, but instead get stuck.
Even if it is something inside the app that has broken the build, there shouldn’t be anything that an user of ours can do that would break building the app, so it’s definitely something we have to fix on our end.
Some progress: your build is not stale anymore, but it errors. We’re looking into this, but if you’d like to try and help, check any images you have in your app, one of their URLs may have problems (loading slowly or not at all).
OK. Previously when I had issue with builds throwing error - there was an issue with links to Instagram photos, but saved in …REST API schema…(where it shows preview of values…)
Yeah the build fails if it can’t download all the assets required Please check all the images in your app just in case, if there’s a problematic url somewhere still. Upload any static images in Composer.
So inside of my REST API there were some test images that I have picked up from Instagram (and a few of them I forgot to move to my own storage). I have cleaned up the data in my database (that is accessed via REST), I have rebuilt the schema so the old links do not show up in the schema as examples.
Still I think looking at the error log ( I think now you added again the log to the email? ) there is somewhere one link to old photo… This must be saved somewhere in schemas or in some meta data - as none of the images on my app is hard linked directly to any image …
I keep digging…
One of API connections had in schema example value of an URL link to image that was not loading:
I was not even using this part of API in the app - it was just sitting there as a sample value in schema… FYI
BTW - It seems now that the Web app build is updating the Appgyver hosted app immediately.
No it does not, I think the first new build got immediatly replace, second one seems to be taking a couple of hours already…
Thanks for letting us know! I made a ticket about this to be fixed at some point, as having the build fail because of an example image url is harmful.
The web build cache fix is still under investigation due to other higher priority issues rising in the meantime…
Hi I’m facing a similar issue. Is this fixed now?