One quick way to fix this though is to delete the app and reinstall, since that would wipe out the entire thing altogether, but this works only when you're debugging and wouldn't work for users since they can't just delete the app and redownload everytime this happens.
So to actually solve this problem we need an actual replicable code we can test, as @maks mentioned. Otherwise there's not much i can do for you. Please try to write a public test case in JSON and share it so that we can isolate the problem and be sure that it IS indeed buggy in the way you think it is. From my experience, when you try to write such a minimal isolated test case you find that the problem is somewhere else.
Having a minimal test case helps in the future because we can always come back to the test case whenever there's an update and make sure it passes the test as well. Without a test case we will never have a way to make sure this doesn't break in future updates, which is bad for everyone.
In terms of technical details:
- The views shouldn't cache JSON unless told to.
- Also setting
"offline": "false" is actually the same as setting
"offline": "true" or whatever else you set it to. The way it works is, Jasonette only looks at the existence of the
"offline" key to determine whether the feature should be on or off, so if you want it to be off, you should exclude it altogether (which is the default)