This problem is very situation specific and cannot be reproduced per se. I am currently not having problems with it. But when it started to create this problem I searched google for it and came across this and found the same behavior was happening to someone else. I replaced the backendless.jar several times since then and it seems it disappeared for me.
Thanks!
I don’t actually know how, but the problem went away. So I guess this is not an issue.
I am not sure if it had anything to do, but I reset the user’s table from the console.
I am going to start another thread, about a question I have due to some strange to me behavior after doing some tests on setting meta data on a geopoint.
Regards,
George
Hello, I’m still facing the same issue.
The first time I open the app it works, maybe I can save an object 1 or 3 times, but then, I get the same error. It works randomically. For example, I have a list of items that can be ordered. After ordered, I’ve implemented a recursive function to save them due to I cannot save all objects at the same time, and after saving the first or second object, the second or third fails with that error.
Is something that I can provide so you can help me? I’m using this version:‘com.backendless:backendless:3.0.25’
Thanks in advance!
Hi Juan,
Do you have auto-loads turned on for your objects?
Mark
Yes and no. I have this issue with 2 entities. Should I have them?
One entity have several relations, all of them with autoload
The other, all relations are not autoload.
Both entities have a User relation. I’m not sure if this helps, but maybe…
If you turn off auto-load, the error will go away. Otherwise, we’d need a sample which reproduces the problem. It does not have to be an Android sample - can be a plain Java program.
Mark
I tried that and still not working.
What I’ve deduced is that after saving an object that has an user as a relation, then if I want to save another object of the same entity and with the same user relation, I need first to update that user and then save the object. Is that correct?
I’m not sure why, but after debbuging, the only way I could make it work is getting the user from the returned object in the save callback, and if the next object has the same related user, update it and save it. This is quite complicated due to I might have to update list of 20 - 30 items with different user relations.
Can you send me your email so I can send the test project?
Thanks in advance!
Juan,
Please upload the project to either google drive or dropbox and send a link to download it to support@backendless.com (with a link to this topic as well). Make sure not to send the project as attachment.
Regards,
Mark
Hi Mark, thanks for the quick reply! I’ve sent the email some minutes ago. Do you have an ETA for an answer?
Thanks,
Juan
Juan,
As we communicated offline, the fix is in the github repository. Thank you for your assistance with getting this fixed.
Regards,
Mark