You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 17, 2019. It is now read-only.
version : 'com.twitter.sdk.android:twitter-core:3.3.0'
I use custom event for reqeust the tempToken using OAuth1aService::requestTempToken.
The code is
public void requestTempToken(final Callback<OAuthResponse> callback) {
final TwitterAuthConfig config = getTwitterCore().getAuthConfig();
final String url = getTempTokenUrl();
api.getTempToken(new OAuth1aHeaders().getAuthorizationHeader(config, null,
buildCallbackUrl(config), "POST", url, null)).enqueue(getCallbackWrapper(callback));
}
So it enqueue the request directly without returning anything. That's means there is access to the call and hence no way to cancel that request. Which can lead to an memory leak or crash after Activity destroyed.
Can you add the call himself as an return value? Thanks!
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
version : 'com.twitter.sdk.android:twitter-core:3.3.0'
I use custom event for reqeust the tempToken using
OAuth1aService::requestTempToken
.The code is
So it enqueue the request directly without returning anything. That's means there is access to the call and hence no way to cancel that request. Which can lead to an memory leak or crash after Activity destroyed.
Can you add the call himself as an return value? Thanks!
The text was updated successfully, but these errors were encountered: