Illya, any progress? (just a thought...) We have a Russian translator on staff if speaking directly on the phone will help. We really want this working again as I am sure you do. Let me know if that would help at all.
Illya, any progress? (just a thought...) We have a Russian translator on staff if speaking directly on the phone will help. We really want this working again as I am sure you do. Let me know if that would help at all.
James, in our build logs we don't have any errors messages.
Now we are researching your app with testing in the builder.
The issue is persisting.... how can we help diagnose the problem? This is very concerning to us given that we need to present an app for a $1M competition in a few days. I see many other users posting about similar issues on the forum.... if this can not be resolved quickly we will have to revert to our previous posture with a competitor.
We are sorry James, as we can now say most probably your project is broken.
To restore your project it will require time.
I can see your app here: http://saassay.app.appery.io/startScr.... But you are still not able to publish?
Correct! We can access the app on the URL as well. BUT when we try and publish we always get the 500 error, AND when we are inside the UI Builder and select the TEST option we also get the 500 error.
We are unable to publish recent changes or test them. We are dead in the water until a solution on your end fixes the issue.
Sometimes when I load the Account Dashboard for the app, it says that the app is in a status of building even though the last time I ran the publish process was a while ago.... maybe something is stuck in publishing state and needs to be flushed on your end????
We are looking into this right now.. very sorry about this problem.
We fixed it... looks like a mapping error into a grid... when we are unable to Test the application or publish it like the issue we experienced, is there a way to see an error log on our end?
Glad it's working. Do you have a backup of the project when it was not working so we can test why it happened?