It can handle three scenarios:
1) When user has token in `localStorage` and it is invalid then event `oidcauth:silentInitRefreshStarted` will be broadcasted to `$rootScope` and library will try to do `silentRefresh`. Then you receive this signal you can show popup message `logging in..` and wait for one of this signals: `oidcauth:silentRefreshSucceded` or `oidcauth:silentRefreshTimeout`
2)  When user has token in `localStorage` and it is valid I can send you event just give me a string but anyway, lib will start the loop for keeping token refreshed.. just test `$auth.isAuthenticated()` before api call to check token and silent refresh loop. The event `oidcauth:tokenExpires` is being thrown just before token expiration minus `config.advancedRefresh` (in seconds) and then one of `oidcauth:silentRefreshSucceded` or `oidcauth:silentRefreshTimeout`will occur after `oidcauth:silentRefreshStarted`.
3) When user hasn’t token in `$localstorage` (user permormed logout action or never log in) I can send you event just give me a string but anyway, lib will NOT start the loop for keeping token refreshed..

Last note:
 - Lib will start loop for refreshing token when it is not running and user perform log in or silent successful refresh token.
 - Lib will stop the loop when user performing logout

fixed IONIC integration