HWComputerScience / iHW-iOS

iHW iOS App
4 stars 4 forks source link

Downloading Schedules doesn't get past login page #14

Open jononon opened 8 years ago

jononon commented 8 years ago

I reached out to diadax and they had just enabled SSH. They disabled it for now and everything is working, but I still am going to find out how we can get this working with SSH.

jburns20 commented 8 years ago

do you mean SSL?

jononon commented 8 years ago

Yep that one

jburns20 commented 8 years ago

This can probably be fixed by modifying the URLs here so that they begin with https:// instead of http://. Look at the URLs that you go to when you get the schedule manually in a browser for reference.

lbagdasarian1 commented 8 years ago

I'm getting a "schedule unavailable notification." Then when I press "choose year" multiple times, I am able to close that box and click redownload schedule, but the HW website login never loads. Is anyone else having that problem?

jononon commented 8 years ago

HW changed to ssl, I asked them to change back to non secure logins until we sorted it out but maybe they turned ssl back.

On Jan 19, 2016, at 6:39 PM, lbagdasarian1 notifications@github.com wrote:

I'm getting a "schedule unavailable notification." Then when I press "choose year" multiple times, I am able to close that box and click download schedule, but the HW website login never loads. Anyone else having that problem?

— Reply to this email directly or view it on GitHub https://github.com/HWComputerScience/iHW-iOS/issues/14#issuecomment-173065105.

lbagdasarian1 commented 8 years ago

So basically the app won't work unless they switch back unless users have logged in already and have their schedules stored locally?

jononon commented 8 years ago

Or we switch… forward? To ssl.

On Jan 19, 2016, at 6:45 PM, lbagdasarian1 notifications@github.com wrote:

So basically the app won't work unless they switch back?

— Reply to this email directly or view it on GitHub https://github.com/HWComputerScience/iHW-iOS/issues/14#issuecomment-173066450.

lbagdasarian1 commented 8 years ago

How large of a change do you think that would be?

jononon commented 8 years ago

A few lines

On Jan 19, 2016, at 6:49 PM, lbagdasarian1 notifications@github.com wrote:

How large of a change do you think that would be?

— Reply to this email directly or view it on GitHub https://github.com/HWComputerScience/iHW-iOS/issues/14#issuecomment-173068105.

lbagdasarian1 commented 8 years ago

While we're at it, what do you think about migrating to Parse and storing user data there as well as on the app?

jononon commented 8 years ago

If it ain’t broke...

On Jan 19, 2016, at 6:55 PM, lbagdasarian1 notifications@github.com wrote:

While we're at it, what do you think about migrating to Parse and storing user data there as well as on the app?

— Reply to this email directly or view it on GitHub https://github.com/HWComputerScience/iHW-iOS/issues/14#issuecomment-173069192.

lbagdasarian1 commented 8 years ago

I mean if we keep a record of user data/schedule info, we could add some sort of a feature to allow students to search for each other's schedules or find common free periods.

jburns20 commented 8 years ago

This is another issue that I considered and rejected due to privacy concerns. This feature would effectively give you, the developers, access to everyone's schedules. Since we're dealing with confidential educational information, I decided to keep schedules on the client only. Feel free to discuss this with the administration, though, as their opinions may have changed.

jononon commented 8 years ago

I second this view - it’s not our responsibility to store and share schedules.

On Jan 19, 2016, at 7:26 PM, Jonathan Burns notifications@github.com wrote:

This is another issue that I considered and rejected due to privacy concerns. This feature would effectively give you, the developers, access to everyone's schedules. Since we're dealing with confidential educational information, I decided to keep schedules on the client only. Feel free to discuss this with the administration, though, as their opinions may have changed.

— Reply to this email directly or view it on GitHub https://github.com/HWComputerScience/iHW-iOS/issues/14#issuecomment-173074207.