Saved changes not taking effect - ever.

[James Barker]

I've done a search on this issue and seen a few posts, but no real resolutions. I'm new to Appery and am really just testing at this point. After making changes to my app, deleting, adding or updating components, etc. and saving the edits the changes often do NOT take effect when previewing the app. I can dig through the html, css, or js code and make the changes there manually and that helps - IF I can locate the issue in the code. I'm testing in latest builds of Chrome and Firefox. I've cleared cache, logged out, all the past suggestions but with no luck. This appears to be a bug with the Save action you provide.
I need to make a recommendation to my company on which app dev solution we should invest in. I can't in good faith recommend Appery if the service doesn't work as advertised with something as simple as saving changes and the changes not taking effect without digging through code to manually make the updates - which contradict what the UI is telling me. I understand bugs are a part of it all (and many times it's simply my error) but the consistent lack of proper updating after something as simple as clicking Save has me doubting how successful my development process would be once the app creation process becomes more involved/complicated down the road.

Please advise and thanks for time!

[Illya Stepanov]

Hello James,

If you are editing code in the Source tab of your project, please note that this changes will not be shown in the web preview.
We recommend to make changes in the Source tab only in the end point of a production process.

::http://docs.appery.io/tutorials/sourc...
(Notes after point 10 in this section)

[James Barker]

Hi Illya,

Thanks for the quick reply. I would MUCH rather use the Design interface and usually do but making changes through the design interface often doesn't "push through" the changes to the actual code and the changes are not reflected when I preview the app. As I've said, I've used both Chrome and Firefox (latest builds), cleared cache, logged out of Appery and back in and the Saved changes made in your design interface do not take effect - because saving my edits do not change the code. This mainly happens when I edit existing components in some way.
Often I can make edits, click Save, then go look at the code and there are NO changes at all. For example, if I delete a grid, Save, run preview the grid is still there. If I check the code the grid is still there. If I check the design interface, there is no grid. Why doesn't the Save button update the code as it should?

Thanks again.

[Maryna Brodina]

Hello!
[quote:]not taking effect without digging through code to manually make the updates[/quote] Once you edit source on Source tab (even if you just add a space in any file) you won't see changes you do after that through editor. After you edit any file on Source tab this file has higher priority and no changes from editor won't be shown in preview. If you want to see changes you've made you have to delete edited (blue colored files) and Undo all source changes on in folder with these files.

[James Barker]

Hi Maryna,

Thanks for the tip. I'll definitely keep that in mind. Unfortunately, that still doesn't address the central issue which is; Why doesn't the save button push these changes across through all of the code? If the save button worked as it should I wouldn't need to be tampering with the code at all. I'm referring to something as simple as deleting a component through the design tab, clicking save - but that component still existing in the code. I can understand if there's something more advanced that could only be accomplished through manual coding since there may not be an element or component to do it from the Design tab but I've done nothing advance to this point.

Thanks again for the reply.

[Maryna Brodina]

Save function works. Let's do next... first delete all blue colored files and click "Undo all source changes" for each folder where you've had these files. After that just for test add any component on screen and test on preview. Let me know result.

[James Barker]

Hi Maryna,

Thanks again for the feedback. I've deleted the app and started from scratch since it was a simple two screen test. I'll keep your tips in mind as I work through my next test app.

Again, thanks for your help!

[Maryna Brodina]

Thank you for update! Let us know in case you need help.