$ timeout（）不调用inappbrowser [Ionic]

Question

I am using an initial screen(initial.html) and i want it to act as a splashscreen and then call the inappbrowser.

But inappbrowser is not opening. If i place it directly it works. No error is also coming. The required functionality is to have a splash screen view getting redirected to inappbrowser, user will log in and upon successful login will be redirected to the view.( Individual parts are working, but when i put it inside a TimeOut function it is not working ).

Is there any better way to achieve this functionality.

controller.js

.controller('LoginCtrl', function($scope,$timeout,$rootScope,LoginService, $ionicPopup, $state,$location,$ionicPopup) {
  $timeout(function(){                    
    LoginService.loginUser().success(function(data) {
        console.log(data); 
        $location.path('app/playlists');
    }).error(function(data) {
        var alertPopup = $ionicPopup.alert({
            title: 'Login failed!',
            template: 'Please check your credentials!'
        });
    });    
}, 3000);
})

services.js

angular.module('starter.services', [])
.service('LoginService', function($q,$rootScope,$cordovaInAppBrowser,$http,$state,jwtHelper,$location) {
return {
    loginUser: function() {
       var deferred = $q.defer();
       var promise = deferred.promise;
        console.log("Hi Service"); // IT IS REACHING HERE THEN STUCK
        $cordovaInAppBrowser.open(URL, '_self',options).then(function(event){     
    console.log(event);
     // success
  })

  .catch(function(event) {
     console.log(event);
     // error
  });

 $rootScope.$on('$cordovaInAppBrowser:loadstop', function(e, event){
if(userValid){
deferred.resolve(username);  }
else{
deferred.reject('Auth Failed');
}
});

 //promise created outside
 promise.success = function(fn) {
            promise.then(fn);
            return promise;
        }
        promise.error = function(fn) {
            promise.then(null, fn);
            return promise;
        }
        return promise;
    }
});

Answer 1

I removed and reinstalled the inappbrowser plugin and it worked correctly. I apologize for the confusion