New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Unknown prop triggerLogout
on <button> tag" after updating from 3.2.1 to 3.4.0
#60
Comments
Same thing here. |
@andrijan Yeah this happens because you didn’t implement About the second bug, I don’t understand, which provider is concerned and how can I reproduce it? |
Thanks for the fast reaction 🙏 Regarding the first issue, I just copied the sample code from the readme - could you please give an example how |
Oh yeah, this sample didn’t took account of Regarding logout process implementation, you will need a container handling login state. You should look at new demo files, specifically As I implemented it, we have a container handling login state and forwarding a Also, ref handling here is tricky because I handle multiple providers in one login state manager but it could be easier/simpler to make a container per provider. |
Unfortunately I'm still too much of a beginner to understand all these ins and outs. Especially with HOC. Thanks a lot for your explanation, but I'll wait patiently until the readme perhaps have a simpler example 😅 |
It's LinkedIn, I'll find the code to reproduce it. |
Facebook doesnt work for me after the upgrade. |
Do you have to click twice to get the It seems like it's triggering something after the first click, then when you click again, you get the error, because it's still processing the first click. |
@andrijan Exactly! I have to click it twice. |
@andrijan @Amurmurmur When you call |
I cloned the repo and used the SocialLogin wrapper from that code, instead of release 3.4.0 and that seems to work, I at least get the popup. |
So what's the deal? Can you show us both code samples please? See what's causing this, thx |
I believe I've figured it out, I was using React 15.6.1, but it seems it needs 16.0.0 at least now. |
Huh, weird. I'll have to dig into this. |
@andrijan Yep thats right. Just upgraded to react 16 and it works now, dialog pops up. |
@andrijan @Amurmurmur Just tried to run the demo in a separate context with its own I ran the following tests:
I really can’t say what is the matter here… Could you give it another try or setup a repo reproducing the error please? |
@nicolas-goudry Honestly, I tried with the older version of React, the window doesn't pop up with the exact same code. :/ |
Hi guys i have the following configuration and i cannot get it working. Steps:
Any idea about this guys? |
I am running into the same issue. Steps:
Suggestions on work around? |
I am running into the above issue as well, from what i understand is after any succesful or unsucesful login, if you click the button again this "Fetching user" error message is displayed .
After any one of these function executes, clicking the button again results in "Fetching User" |
Hi,
|
Getting the same Fetching User issue. |
Code
Screenshot
The text was updated successfully, but these errors were encountered: