-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Fix leaks #429
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
Fix leaks #429
Conversation
Thanks for this! Nothing wrong with the fix as it stands but I think the safer way to do this is to have the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, that's a much better way of doing it! (I'm complaining about twitter not having a good API and here I am doing the same thing! 😅)
@@ -55,6 +55,8 @@ | |||
private IdpCallback mCallbackObject; | |||
|
|||
public FacebookProvider(Context appContext, IdpConfig idpConfig) { | |||
appContext = appContext.getApplicationContext(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to do this or only call getApplicationContext
when we are passing it into the Facebook initializer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. Either way would have been fine.
Merging! |
I found another leak related to Twitter in
AuthMethodPickerActivity
:According to the Twitter and Facebook documentation, we weren't using the right context.
Once #418 gets merged, all leaks I've noticed will have been patched!