We have a table called Events. I delete a property in console called “user” (string) and changed a class in my code to add the field again, but this time as a relation. Now I get the above error when trying to access the Event class.
Internal server error means there is a problem on their server, it’s not something on your side. They said they worked on the server to make it faster and stuff like that…Yesterday it worked, now it has moments when it’s working and moments when it doesn’t, giving Request Timeout error or other server-related error. Personally, I am getting enough of this.
Then we’re in the same boat. My client is extremely unhappy. Thankfully Backendless has pretty good support and are quite responsive to requests. I just hope stability can be attained and maintained when our application goes into production.
I’m trying to stay positive but I just got a “backend server is at capacity”, so it’s going down hill on the positivity. I know they can’t guarantee anything in the clouded version, but we can’t even get a 1-user app in development to function properly. So we are never getting to the point where a jump to their managed solution makes sense. Anyway, best of luck with your app. I hope you catch up and keep the client.
If you didn’t know, the managed service starts at $ 2,500 / month for 50 API calls (or at least that’s what I’ve been told). Who will pay that amount of money without having a MVP (minimum viable product) first?
@Matt That’s what I’m getting now, those codes, I don’t really know when to expect it to work and when to just wait for a solution.
@Cristian For me those errors appear randomly so also don’t know when to expect it to work. Waiting for a solution seems like a bad idea - I’ve opened a few tickets more than month ago and they are still not closed. I’m using only REST API even I’m creating an Android app and managed to set up things up and working without continuous errors after few (probably 3 different) database structure implementations.
My current approach is to have data tables without any relations (loading data with relations is slow and cause errors) and cache as much as possible. This way I need to make more requests when creating data and also part of the data is duplicated but I have less GET requests.
Less requests = less error responses.
@Matt Thanks for your advice. For my app, updates need to be made on a particular object and the rest of the users has to see that object updated, so I have objects that needs to change their properties based on the action of a user, and I really need these requests to work. These problems leads to inconsistency in my case. But I’m glad that you found a workaround.
Philip - from my experience - if you run the app directly on the device, make sure you use a Dev push notification certificate. If you run it from Test Flight, you will ned a Distribution one. One more thing I noticed - put a password on your certificate; I don’t know why, sometimes for me it didn’t work if I had a certificate without a password.