Splunk Cloud App Vetting Failure -Possible resolutions for check_hotlinking_splunk_web_libraries?

[arielpconsolaci]

Hi Fellow Splunkers,

Good day. I am currently migrating some applications from On-Prem to Splunk Cloud. From app vetting, would anyone be able to suggest of possible fixes/resolutions for this  check_hotlinking_splunk_web_libraries check?

The errors points to JS files that works well in On-Prem and are in their correct location in packaging an application (appserver/static)

Name: check_hotlinking_splunk_web_libraries
Description: Check that the app files are not importing files directly from the search head.
Details: Embed all your app's front-end JS dependencies in the /appserver directory. If you import files from Splunk Web, your app might fail when Splunk Web updates in the future. Bad imports: ['vizapi/SplunkVisualizationBase', 'vizapi/SplunkVisualizationUtils'] File: /tmp/tmp4bxeox7h/splunk_app/appserver/static/visualizations/VUmeter/src/visualization_source.js

Appreciate any help/advise. Thank you.

[epescio_splunk]

Hi @arielpconsolaci ,

I think you just need to replace ['vizapi/SplunkVisualizationBase', 'vizapi/SplunkVisualizationUtils'] with ['api/SplunkVisualizationBase', 'api/SplunkVisualizationUtils'] in both visualization_src.js and webpack.config.js

[jaxjohnny2000]

I even opened a support case with splunk.  They told me to read the development guide.  apparently this error is a mystery to anyone who sees it.