Closed yuchunc closed 7 years ago
Apologies if I didn't do the pull request right, I am not familiar to the proper way of contributing to a project. Please let me know if I'm missing anything, I will patch it.
Thanks for the report @yuchunc 👍 I'll take a peek at your PR today.
Yep, I'm getting the same thing. Applying PR #243 fixed it locally. (Until it's merged I can't use it in my CI system, of course.)
Any idea on when you'll cut a new release for hex.pm? This will remain broken for anyone until then.
@jamesvl I intend to cut a new release today but in the meantime you can use master
:
{:guardian, github: "ueberauth/guardian"}
0.14.1 has been released.
Hi, I got this error even after the upgrade. I got the same error with 0.14.1
.
Same issue as @collegeimprovements after upgrade to 0.14.1. Found the issue and opened a pull request #250
@larryweya / @collegeimprovements / @NilsLattek — a fix has been merged into master, before I cut a new release could one of you please verify that master is working for you? I'm currently traveling and don't have everything I need to smoke test it.
@doomspork I was having the same problem and using {:guardian, github: "ueberauth/guardian"}
fixes it for me.
Is this the fix?
@doomspork works for me too.
Thank you @Ch4s3 and @larryweya 👍
I've released 0.14.2, hopefully this resolves everyone's issues. The ueberauth org is taking over GuardianDB maintenance so I'll be putting some time into clean-up in the coming weeks.
I am facing the same problem and 0.14.2 works fine
Can confirm, 0.14.2 works
Hi, I upgraded the to the latest Guardian package, and ran in to this exception:
after some digging into the code I think it's a miss match between:
GuardianDb's [after_encode_and_sign] (https://github.com/hassox/guardian_db/blob/master/lib/guardian_db.ex#L77)
and
Guardian's https://github.com/ueberauth/guardian/blob/master/lib/guardian.ex#L105
If we just tweak the pattern a little bit to {:ok, _} it would resolve the issue.