-
Notifications
You must be signed in to change notification settings - Fork 127
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
isUserless doesn't work properly #210
Comments
Can you post the relevant code? |
There isn't anything else besides this
And this
|
Gonna need a bit more context here. When is AuthenticateAsUserlessTask executed? What about hasUser? |
I call it on onResume where I authenticate as userless (just for now just as I am testing) and after that load the user data (which of course won't be done if the boolean returned the right thing)
|
So, any way to resolve this? |
The reason Since |
True, but that doesn't explain why |
Can you log the value of |
I think I've found the issue. When return switch(RedditClient(http, current, creds, tokenStore, username)) (source) Here I should have this fixed by tomorrow. |
I think |
Fixed! To use this patch you can either wait until v1.1.0 or use JitPack: repositories {
maven { url 'https://jitpack.io' }
}
dependencies {
compile 'com.github.mattbdean:JRAW:6977732'
} If you find an issue with setAutoRenew please submit a bug report so I can fix it! |
When I first open the app, I
switchToUserless
and when I callisUserless
it returns true.However, when I open the app and
switchToUserless
again, all of a sudden `isUserless' now returns false, even though that's not true.Examples
When app opens for the first time:
Second time:
Also, because
isUserless
doesn't work properly, my app proceeds to load the account data of the userless account that doesn't exist, and crashes.Is this how it's supposed to be, since before 1.0.0
isUserless
always returned true if the app was not authenticated with a user accountThe text was updated successfully, but these errors were encountered: