-
Notifications
You must be signed in to change notification settings - Fork 260
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
making the login state app wide ? #39
Comments
@matantsu, SocialNetworkManager is just a fragment, so you can use something like this to get instance of it
And then just call getSocialNetwork().isConnected() |
thanks , and just one more thing , is there a way to set up a primary social network ? |
You want user to login with google and have an ability to post to facebook? This is not possible, to post something you need to login. |
the will log in to both , and post to both , however the app will consider one social network as the primary and will use it's id , profile pic etc... |
Ah, no, library does provide so functionality. You will need to handle this by yourself. |
ok. so i tried:
app crashes at logCat:
|
Ah, sorry, this is just a typing error in code
The issue is that SocialNetworkManager is a fragment, and initializing it is a transaction, you can call for getSocialNetwork method only after onSocialNetworkManagerInitialized called. You have an interface for this: OnInitializationCompleteListener. Check demos project for more info. |
code:
error:
|
if i trigger the request from a button click it works perfectly. but onSocialNetworkManagerInitialized not. |
Yeah, I see the issue, startResolutionForResult is called only during requestLogin. |
This library could be so awesome if there weren't all this stupid minor bugs... |
I think onSocialNetworkManagerInitialized should be called only when all social networks are ready to perform requests. |
Haha, agree :) It was written for one of my projects, and it works fine there. If everyone here will make a pull request, when find the bug, library will become better. As for me, I don't have time to work on it, so I fix something or add new features, only when QA team create issues in projects but tracker.
This is how it works right now. You have issue with Google+ because you use it, not like all others. Default behaviour login->requestPerson->storeData. Then if we are connected(), we just load data from the storage. So in this scenario, we have initialized, mGooglePlusClient. |
i have integrated this library into my app , and it for now works great on google plus , i can call a function to login in my fragment and all is good.
just one question , how can i acsess the state of the user from anywhere in the app ? (eg. isConnected() etc...)
The text was updated successfully, but these errors were encountered: