How to cope with Javascript stack trace in my web browser JS debugger's console after a migration?

Component: Bonita | Version: 7+ | Edition: All

Question

How to cope with JavaScript stack trace in my web browser JS debugger's console after a migration?

As a developer, using the UI Designer, I am modifying the web pages for our living applications. One HTML widget is not displayed anymore since environments have been migrated.

There are two distinct stack traces, one which get generated with the production environment and another one when the newpage is loaded from the tomcat associated with the Studio.

Production environment

Error: [$<a>injector:unpr</a>] <a href="http://errors.angularjs.org/1.3.18/$injector/unpr?p0=modalServiceProvider%20%3C-%20modalService">http://errors.angularjs.org/1.3.18/$injector/unpr?p0=modalServiceProvider%20%3C-%20modalService</a> vendor.min.<a>js:105</a> at vendor.min.js:9 at vendor.min.js:41 at Object.d [as get] (vendor.min.js:39) at vendor.min.js:41 at d (vendor.min.js:39) at Object.e [as invoke] (vendor.min.js:39) at E.instance (vendor.min.js:79) at vendor.min.js:62 at q (vendor.min.js:10) at x (vendor.min.js:62)

Development (Studio) environment

Error: [$<a>parse:syntax</a>] <a href="http://errors.angularjs.org/1.3.18/$parse/syntax?p0=%2F&p1=no%20a%20primar...Fbonita%2Fapps%2Fwheel-store%2Frequest%2F">http://errors.angularjs.org/1.3.18/$parse/syntax?p0=%2F&p1=no%20a%20primar...Fbonita%2Fapps%2Fwheel-store%2Frequest%2F</a> VM7780 vendor.min.<a>js:105</a> at <a href="http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:9:417">http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:9:417</a> at lb.throwError (<a href="http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:195:113">http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:195:113</a>) at lb.primary (<a href="http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:194:330">http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:194:330</a>) at lb.unary (<a href="http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:200:451">http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:200:451</a>) at lb.multiplicative (<a href="http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:201:178">http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:201:178</a>) at lb.additive (<a href="http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:201:36">http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:201:36</a>) at lb.relational (<a href="http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:200:404">http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:200:404</a>) at lb.equality (<a href="http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:200:260">http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:200:260</a>) at lb.logicalAND (<a href="http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:200:136">http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:200:136</a>) at lb.logicalOR (<a href="http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:200:6">http://localhost:8080/bonita/portal/resource/app/wheel-store/request/content/js/vendor.min.js:200:6</a>)

Answer

As a developer, it is needed to clear the cache's data of the web browser you are using.

The final users won't experience this behavior.