You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found an interesting problem while trying to use ng-token-auth with cookie storage on Ionic but using ng-cordova-auth to handle my oauth process - the cookies get wiped. At least they do on Android. And, of course, having come out of the auth process ng-token-auth has lost it's auth tokens.
This appears to be due to the default configuration of the in-app-browser where it will clear the cookie cache before opening up the "new" browser window.
It's a bit of a pain to find this problem as it'll only appear once one deploys to an emulator or device.
Options I see are:
Detect the presence of the cordova object and maybe console.warn the developer
Include a note in the README.md either in the config section about the storage option
Create a Cordova-specific section somewhere in the README to collect and deal with these (edge?) cases
I could do any of those, just not sure which is most appropriate.
The text was updated successfully, but these errors were encountered:
We're working on inAppBrowser support in an upcoming PR ... See also Issues #90 and #141 for tracking other implementations / etc. Going to close this, as documentation is also being addressed in the PR.
The PRs are in for ng-token-auth #188 and devise-token-auth (lynndylanhurley/devise_token_auth#323). Please try these branches out and let us know if there are any issues in implementation. Will merge soon if no major issues are found!
Found an interesting problem while trying to use ng-token-auth with cookie storage on Ionic but using ng-cordova-auth to handle my oauth process - the cookies get wiped. At least they do on Android. And, of course, having come out of the auth process ng-token-auth has lost it's auth tokens.
This appears to be due to the default configuration of the in-app-browser where it will clear the cookie cache before opening up the "new" browser window.
It's a bit of a pain to find this problem as it'll only appear once one deploys to an emulator or device.
Options I see are:
cordova
object and maybeconsole.warn
the developerstorage
optionI could do any of those, just not sure which is most appropriate.
The text was updated successfully, but these errors were encountered: