Forum | Appery.io

hi There, this is a minor issue but I hv noticed since recently that when clicking on the "cancel" button of the mapping tab either beforeSend or onSuccess or any of them, it takes very long to shut the tab. i mean much longer than when clicking on "save".
as you can guess it takes long enough to motivate me to drop a line about it to you looking forward to having it back to speed of light !

Hi Eric -

Is this happening with some particular app or in every app even in new one?

If this only in particular app, please share it and tell us its name.

Hi Illya,
I'm only working on the same app the one currently on share.
o2o4pw
no rush on that, I rather like you guys to find where googleMap code has gone ?

thks

I'm seeing the same thing on all apps. Delay time seems to be based on App complexity.
Processor usage spikes to 23% for 5 seconds then the screen updates.
clicking save instead as it is instant.

Hi Neil, true that clicking "save" is immediate, but it's not "safe"
if you hv been facing same thing, our great people at Appery will find the way to fix it.
enjoy your wknd !
Eric

Hi, just wanted to mention that I'm now working with Illia via email support on what may be a related issue. But in my case the result is more serious - I actually lose my custom JS code on success mapping. In my case, the problem can be replicated by:

1. go to existing map code
2. then cancel, then cancel again, and then save and close the project
3. when the project is reopened that code is gone.

Yes, behavior is pretty much the same as Robert mentioned, on step 2 when performing second cancel on Data page there is a delay.

I will report this issue also.

Hi Illya, in fact it's not a minor issue any longer.
when clicking on Cancel, it keeps Killing the appery session.
tell us when you got news.
thks
Eric

Tested this in the NEW builder again. Problem is corrected.
Tested all save, cancel scenarios. Delay gone, processor spike gone, changes saved.

Thank you for the update here.