Forum | Appery.io

Hi Joseph,

Thanks for this detailed description.

we will check it and let you know about results here.

Regards.

Hello Joseph,

We reported your issue as a bug and ill get back to you with the update.

Any news? It happened again. Another transaction spontaneously added a field which corrupted my database. It's been 22 days since I've heard something.

Hi Joseph,

As i can see - your issue currently is in unresolved state.

We will update you here as soon as possible.

Thanks for your patience.

Regards.

Well, it's three months past, and the issue has now reached a great status. I have a field which is automatically set to true in my production environment, and still no status, no relevant answer, and defective software from Appery. It still stems from your upgrade last year, and still has not been answered.

Is anyone working on it? Looking at it?

Hello Joseph,

I'm really sorry for radio silence here.

In issue state I can see that it is not reproducible for us.
Let me check this with developers.

Hello Joseph,

We are very sorry for delay. Could you please clarify do you still have a possibility to reproduce it?

Yes, of course. I just deleted my entire body for call to update, manually created all the details of the record for the call, and it exhibits worse behavior.

I set ONE SINGLE FIELD to true, and the application assigns nine different fields to values scattered throughout my application in other updates.

and here is the outcome network traffic

I can't depend on a call to my database for an update to erase, change or modify any particular field, boolean or text.

It's trivial to reproduce. Each time I use a new instance of an Update for this particular collection, I get random results from your application.

Hello Joseph,

It works on our environment.

Please share (http://devcenter.appery.io/documentat...) your app with a href="mailto:support@appery.io" rel="nofollow"support@appery.io/a and provide us with the following information:

1) App name
2) Test credentials if login functionality is implemented in your app
3) Detailed steps to reproduce the issue

eventRated"": ""true""