And here is the error that I see thrown in browser console logs.
Error: [$injector:unpr] http://errors.angularjs.org/1.2.7/$injector/unpr?p0=%24ionicLoadingProvider%20%3C-%20%24ionicLoading
at Error (native)
at http://localhost:8000/js/lib/angular/angular.min.js:6:449
at http://localhost:8000/js/lib/angular/angular.min.js:32:125
at Object.c [as get] (http://localhost:8000/js/lib/angular/angular.min.js:30:200)
at http://localhost:8000/js/lib/angular/angular.min.js:32:193
at c (http://localhost:8000/js/lib/angular/angular.min.js:30:200)
at d (http://localhost:8000/js/lib/angular/angular.min.js:30:417)
at Object.instantiate (http://localhost:8000/js/lib/angular/angular.min.js:31:80)
at http://localhost:8000/js/lib/angular/angular.min.js:61:486
at http://localhost:8000/js/lib/angular/angular.min.js:49:14
Hi Calendee - Thanks for such a quick reply! First of all I would like to say that ionic looks amazing and its so great for someone like me who just cant decide what stack to use for mobile development.
Back to the problem, I am using the basic app that I got while creating the project from CLI and the HTML files reference the files as this.
Frameworks - Oh boy - I know where you’re coming from. I bounced around all of them and finally settled here. You’ve made a good choice.
CLI : It seems the Ionic CLI tools are a bit behind the times. For right now, I’d go with the bundle as in the example. However, I caution you may need to change that down the road. It seems there’s been some conflict with 3rd party angular-modules. Having said that, the individual files should still work just fine. Here’s a sample with 0.9.26 using individual files:
FYI : You don’t need to use angular-touch nor angular-route as those are replaced with other alternatives in Ionic.
Thank you so much. I have got the ionicLoding working by making use the codepen project. The default app created with CLI did contain a confusing folder structure. Thank you much for your help!