Skip to content
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

Schedule shows "not enrolled" after relogging in #24

Open
andrewlin16 opened this issue Jan 23, 2015 · 3 comments
Open

Schedule shows "not enrolled" after relogging in #24

andrewlin16 opened this issue Jan 23, 2015 · 3 comments
Labels
Milestone

Comments

@andrewlin16
Copy link
Contributor

Sometimes when logging out, logging back in, and checking schedules, no schedules appear for any semester, and for the current semester, it shows the "not enrolled for this semester" message despite being registered for classes.

I haven't figured out exact reproduction steps, but I think I've encountered this bug using these steps:

  1. Open UTilities.
  2. Log in (using persistent login).
  3. Press Schedule.
  4. ???? (In my experience, this step has been going to the home screen and doing things for a few minutes. Key thing here seems to be doing enough such that UTilities gets kicked out of memory or something. Sorry this step is so unclear. Speaking with @NasaGeek, we think it might have to do with some auth cookies expiring but not all.)
  5. Relaunch UTilities. This should bring back the schedule view but show a message about being logged out of UTDirect.
  6. Go back to the main view.
  7. Log out if necessary and log back in.
  8. Press Schedule again. This should show the "not enrolled" message.

A workaround for this is to completely exit UTilities by swiping it out through the recents menu and relaunching it.

I may look into this bug myself if I have time.

@NasaGeek NasaGeek added the bug label Jan 23, 2015
@NasaGeek
Copy link
Owner

Because logging out doesn't fix this, I'm pretty sure this is an issue related to not clearing all the appropriate cookies that get set upon login when logging out. Simple fix might be to just clear the entire CookieManager when logging out. I also remember seeing a logcat complaining about cookies one time when I tried to investigate this issue a couple weeks ago.

@NasaGeek
Copy link
Owner

Just managed to pull a logcat when this occurred, but didn't see anything of interest.

edit: I can now reliably reproduce this by killing the app's process from Android Studio and then relaunching it, though (very similar to your methodology, @andrewlin16)

@NasaGeek NasaGeek added this to the 2.0 milestone Feb 1, 2016
@NasaGeek
Copy link
Owner

NasaGeek commented Feb 1, 2016

I've heard some reviews complaining about this behavior too. Need to fix for 2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants