maxdeviant / lol-mastery-manager

A tool for managing mastery pages in League of Legends
MIT License
37 stars 21 forks source link

Application crashes as soon as it opens #17

Closed manjot97 closed 8 years ago

manjot97 commented 8 years ago

So today I opened the app, and it said downloading champion.gg data, then it stopped responding and windows said that an unexpected error occured, any fix?

maxdeviant commented 8 years ago

The new mastery format for 5.22 is probably causing an error to occur while downloading the mastery data.

This will need to be addressed in a release for patch 5.22.

DiteVQ commented 8 years ago

The same happened to me

manjot97 commented 8 years ago

Champion.gg released data for 5.22 So how long until the application will work again?

maxdeviant commented 8 years ago

Once I start work on it the turn-around should be a few days.

But I'm extremely busy currently with school and work, and probably won't get to it until after Wednesday. Would like to release by Monday, but that's entirely dependent on the scope of work involved.

On Mon, Nov 16, 2015 at 10:55 AM manjot97 notifications@github.com wrote:

Champion.gg released data for 5.22 So how long until the application will work again?

— Reply to this email directly or view it on GitHub https://github.com/maxdeviant/lol-mastery-manager/issues/17#issuecomment-157077018 .

DiteVQ commented 8 years ago

http://champion.gg/ also they have some problems with your page

maxdeviant commented 8 years ago

If you're referring to the "We are currently fixing issues with Jungle builds." across the top, I believe that is referring to the incorrect items being shown in the build path.

The actual format of the mastery data should be fine for me to start working with.

DiteVQ commented 8 years ago

a ok, good job indeed we are patiently waiting for the application

manjot97 commented 8 years ago

Dude, you're doing a great job. Never would want to invade into your time. School and work are more important :)

maxdeviant commented 8 years ago

Closing this in favor of #18, which is better representative of the reason behind the crash.

Follow that thread for 5.22 status/updates.