search

mylilpenguin / procurement

Automatically exported from code.google.com/p/procurement
0 stars 0 forks source link

[NOT OK]ERROR: Object reference not set to an instance of an object. #17

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 

What version of the product are you using? On what operating system?
win 7 64bit

Please provide any additional information below.

Error on login,crash at tab 4, nothing special in my tab 4 though. 

"[NOT OK]ERROR: Object reference not set to an instance of an object."

Attached debuginfo included

Original issue reported on code.google.com by hudu...@gmail.com on 21 Feb 2013 at 3:46

Attachments:

GoogleCodeExporter commented 8 years ago 
That was with latest release btw, this log below is dev build 0.04

System.NullReferenceException: Object reference not set to an instance of an 
object.
   at POEApi.Model.ItemFactory.Get(Item item)
   at POEApi.Model.Stash.<.ctor>b__0(Item item)
   at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at POEApi.Model.Stash..ctor(Stash proxy)
   at POEApi.Model.POEModel.GetStash(Int32 index, String league, Boolean forceRefresh)
   at POEApi.Model.POEModel.GetStash(String league)
   at Procurement.ViewModel.LoginWindowViewModel.loadStash(Character character)
   at Procurement.ViewModel.LoginWindowViewModel.<Login>b__1()
   at System.Threading.Tasks.Task.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()

Original comment by hudu...@gmail.com on 21 Feb 2013 at 3:50

GoogleCodeExporter commented 8 years ago 
Hello hudu, I'm not a dev, just another person experiencing something similar - 
for me it's caused by a specific item in my stash. I can move this shield to 
wherever, then run the program and it will error when it reaches that shield. 
Mostly because I'm curious, if you figure out which item is causing the error 
you should link it.

Original comment by jpmc...@gmail.com on 21 Feb 2013 at 5:44

Attachments:

GoogleCodeExporter commented 8 years ago 
We have found the issue with this! Patch will be out shortly. Thanks for your 
help with this

Original comment by original...@gmail.com on 21 Feb 2013 at 6:43

GoogleCodeExporter commented 8 years ago 
v0.0.5 has been upped which should fix this for you, please test and let us 
know.

Original comment by stickymaddness on 21 Feb 2013 at 7:17

GoogleCodeExporter commented 8 years ago 
Yes, its been fixed now thanks!

Original comment by hudu...@gmail.com on 22 Feb 2013 at 10:06