yes am using local storage. this post https://medium.com/@benhansen/lets-build-a-slack-clone-with-elixir-phoenix-and-react-part-1-project-setup-3252ae780a1 has been my reference point
rickmutua
rickmutua
JosMPena
Hello!
I’m facing similar problem as yours and I’m interested in knowing how did you solve your issue.
Am I still on time to ask you for a little more detail?
Thanks in advance
0
nikolis
For future reference @NobbZ said
the :erlang.apply/3 is called with wrong kind of arguments. Usually the first argument should be a module name.
So usually the problem is that you might be invoking the Guardian.encode_and_sign_in function without alliasing MyApp.Guardian and that’s why you get this wierd looking error so either alias MyApp.Guardian at the start of your file or just use MyApp.Guardian.encode_and_sign_in.
0
al2o3cr
Guardian.Plug.sign_in calls Guardian.encode_and_sign/4 with the given parameters - that function expects its first argument (the one after conn in sign_in) to work with Guardian.token_module. Looks like that should be the name of the module in your code that calls use Guardian.
FWIW, the code in Guardian.Plug is not intended for direct use - saying use Guardian in that implementation module creates a specialized implementation of the plug:
https://github.com/ueberauth/guardian/blob/0b7aba1840bf2f8b75bc3a258463a3fba7f325de/lib/guardian.ex#L329-L338
So instead of calling Guardian.Plug.sign_in you’d call YourImplementationModule.Plug.sign_in which takes care of passing the implementation module behind the scenes.
1