How to replicate the following error: Tried to overwrite existing file object

Bug reports
1

Hi,

I have caught this error from a user of our offline mobile app.

However, I can’t seem to figure out how the user was able to generate this error and have tried to replicate it manually on a dummy class by for instance deleting the row in the database and then persisting the same updated row into the database again or tampering with the file content.
It was unsuccessful. I have seen the error before also in other contexts.

Can anybody in the Appfarm dev team shed some light on how technically the error can occur?

Kind regards
Torgeir

2

Hi,

This error should be thrown if you attempt to persist an already persisted fileObject. Upload Complete on your fileObject must be true for the error to be thrown.

// Erik

1 Like
3

Could I call you later today? Need like 5 min for some questions about this.

4

Hi,

I’m not available for a call at the moment, but you can reach out to us at support@appfarm.com :smile:

// Erik

1 Like
5

Noted. Thanks for the help and the quick reply :wink:

6

Lars BH and I could not reproduce the error.
We added a string property and persisted an already persisted file object. Which is the same as we have in our apps and this has been working. Its a string for commenting and an ENUM for the photo location. Works fine, but a few selected users have been able to create this error. Most likely then due to something related to offline apps / the row has been deleted before user tries to persist an already persisted file object or something like that.
Ill contact support for help whit reproducing this error.
Thanks