Problems trying to access $ionicConfigProvider

ionic-v1
1

I seem to be gettting an unknown provider error when I am trying to call the config provider

Uncaught Error: [$injector:modulerr] Failed to instantiate module starter due to:
Error: [$injector:unpr] Unknown provider: $ionicConfigProvider

For reference, here’s my app.js file. I am building on a combination of both the side starter app and the tinder cards. Is there something I am missing here?

angular.module('starter', ['ionic', 'starter.controllers', 'ionic.contrib.ui.tinderCards'])
.config(function($ionicConfigProvider, $stateProvider, $urlRouterProvider, $logProvider) {
  openFB.init({appId: '782463241814945'});
  $logProvider.debugEnabled(true);

  $stateProvider
  .state('app', {
    url: "/app",
    abstract: true,
    templateUrl: "templates/menu.html",
    controller: 'AppCtrl'
  })

  .state('app.login', {
    url: "/login",
    views: {
      'menuContent': {
        templateUrl: "templates/login.html"
      }
    }
  })


  .state('app.single', {
    url: "/playlists/:playlistId",
    views: {
      'menuContent': {
        templateUrl: "templates/playlist.html",
        controller: 'PlaylistCtrl'
      }
    }
  });
  // if none of the above states are matched, use this as the fallback
  $urlRouterProvider.otherwise('/app/login');
})

.run(function($ionicPlatform) {
  $ionicPlatform.ready(function() {
    // Hide the accessory bar by default (remove this to show the accessory bar above the keyboard
    // for form inputs)
    if (window.cordova && window.cordova.plugins.Keyboard) {
      cordova.plugins.Keyboard.hideKeyboardAccessoryBar(true);
    }
    if (window.StatusBar) {
      // org.apache.cordova.statusbar required
      StatusBar.styleDefault();
    }
  });
});
2

Hi @rommelc did you find a solutions for this?? I’m getting the same thing… :anguished:

3

I found the solution! You have to call the $ionicConfigProvider from the app.config() instance. You can’t call it from a controller.

app.config(function($ionicConfigProvider){
});
3 Likes
4

Thanks for the info! I decided to solve some other stuff before looking back into this.