Splunk Cloud app shows correct version but serves outdated JS from appserver/static

[tomapatan]

I’ve created a custom Splunk app (TA-custom_scripts) that contains JavaScript and CSS files located at:
etc/apps/TA-custom_scripts/appserver/static/

I packaged the app using Splunk Add-on Builder, downloaded the resulting .spl file, and uploaded it to Splunk Cloud.
The app installs successfully and Splunk Cloud shows the correct app version (v1.0.9), which matches my local development version.
However, the contents of a JS file I modified are not reflected in Splunk Cloud:

Opening the JS file directly in the browser shows an older version of the file
The app version reported in Splunk Web is correct (v1.0.9)
The file path and filename are unchanged
The updated JS works correctly in my local Splunk instance

What I’ve Verified So Far

Confirmed the app version in Splunk Cloud is v1.0.9
Confirmed the JS file exists under appserver/static
Accessed the JS file directly via the browser-the content does not include my latest changes.

I did not restart Splunk Cloud.

Any guidance would be greatly appreciated.

[livehybrid]

Hi @tomapatan 

Did you increment the 'build' value in your app.conf/[install] stanza? This should trigger a refresh of the static assets.

See https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/9.4/configuration-file-referenc...

# app.conf
[install]

build = <integer>
* Required.
* Must be a positive integer.
* Increment this whenever you change files in <app_name>/static.
* Every release must change both 'version' and 'build' settings.
* Ensures browsers don't use cached copies of old static files
  in new versions of your app.
* 'build' is a single integer, unlike 'version' which can be a complex string,
  such as 1.5.18.

🌟 Did this answer help you? If so, please consider:

• Adding karma to show it was useful
• Marking it as the solution if it resolved your issue
• Commenting if you need any clarification

Your feedback encourages the volunteers in this community to continue contributing

[tomapatan]

Hi, I’ve bumped the version using the Add‑on Builder. I checked the two most recent versions, and it’s been done correctly - one shows an increment in the build number from the previous version.

[bowesmana]

If you can do a restart, I would recommend that - I found that after updating an app recently, all worked ok, but the new config UI page for the visualisation was not visible, it showed the old one. A restart was needed.

It's interesting that you can see the old js via the direct url though.

[tomapatan · Accepted solution]

Will try a restart next week - in the meantime I fixed it by creating a new app and copied the files from my previous app - packaged it and deployed it.

[kknairr]

@tomapatan Do you see any internal warnings or errors related to your custom TA or app? If yes, please share that to understand the potential issue better.

Additionally, you can try disabling and re-enabling the app once to see if the app loads the full context? Please try this from an incognito window to make sure you don't have cache issues. 

>>

If this post addressed your question, you can:

• Give it karma to show appreciation 👍
• Mark it as the solution if it solved your issue ✔️
• Add a comment if you’d like more details ✏️

Acknowledging helpful answers keeps the community strong and motivates contributors to continue sharing their expertise.

>>

[tomapatan]

Hi, I can see the contents of the .js file and it does not include my latest changes - so not a caching issue.
Can`t see any obvious errors giving more context.