When you update the resource files for customized basic apps or fully custom apps, testing in the App Editor shows the update. However, users may still report problems or see old content because browsers use cached versions of the resource until the cache expires or users manually clear their browser cache. Having users manually clear their browser cache is generally not an acceptable solution.

You can manage browser caching to ensure that they retrieve updated resources for customized or fully custom apps by using the version attribute in the <require> statement in the App Specification.

The MashZone NextGen App framework uses this metadata to append a unique string to the URL used to retrieve that resource for a custom app. Setting this attribute or updating it each time you update a resource ensures that the URL is unique so that browsers always retrieve the updated file.

For this initial example:

If you update the JavaScript class for this custom app, you simply also change the App Spec to this:

To ensure your changes are visible to all appropriate users in MashZone NextGen Hub. You may also need to publish the app to the AppDepot to make your changes visible to users in the AppDepot or the MashZone NextGen Mobile apps.