Splunk Dev

AppInspect vs Upgrade Readiness App Results

superducktoes
New Member

I have an app that the Upgrade Readiness App says is not passing due to an error. After digging into it more it looks like it's occurring because of the line contrib/jquery-2.1.0 in the file /appserver/static/js/build/common.js

If I submit the same app to AppInspect, it doesn't have any results in the errors/warnings or in the manual checks for that line in common.js.

Really my question is, I believe common.js comes from the Add-on Builder. Is it okay to leave that file as is or do I just change the line referencing contrib/jquery-2.1.0 to use an updated version of jQuery?

Labels (1)
0 Karma

VatsalJagani
SplunkTrust
SplunkTrust

I recently found that if you generate with the latest version of Add-on Builder, it should not have this problem from the Splunk developers. (Though I'm yet to test myself)

https://github.com/splunk/addonfactory-ucc-generator/issues/421#issuecomment-1033799650

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...