Frederik Nakstad
Frederik Nakstad
I had the same problem, and the [solution by enabling keychain sharing](http://stackoverflow.com/questions/38456471/secitemadd-always-returns-error-34018-in-xcode-8-in-ios-10-simulator#answer-38543243) worked for me as well. However, is this really the correct solution to go with here? Keychain sharing...
This is a rather nasty bug if you do end up with a mistake in your routing setup, but I don't have a good solution for it yet as this...
Excellent observation! Thank you so much. I'd be happy to receive a PR for this since you've already solved it. If it's too much bother, let me know and I...
I haven't tried, but I doubt you can use it with the solution as it presently is in the repo. You need to be able to tweak some of the...
That's a very good idea! I'll put it on my todo list, and of course would be happy to receive pull requests for this :)
Yea, seems to be a Chromium/Chrome bug judging from the discussion surrounding this (of which both of you guys seem to have partaken in :). I want to avoid adding...
Yea, seems like that article describes the same problem as in the bug report submitted to the Chromium project. And the fix doesn't seem to be specific to the Angular.js...
Excellent! I guess we'll just hang tight for the moment.
That is an awesome example, and may very well be the way to go forward. I don't see the point in having two repo's solving the same problem in the...
Hmmm, the error trace isn't very descriptive... The example app is also running on Heroku, so the first thing that comes to mind is that if you're using social logins...