abragon / procurement

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

Login error after loading characters #487

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
1.) Did you first check the wiki for your issue?
Yes.
2.) Did you check to see if there is already a ticket for your issue?
Yes, didn't find anything concerning it.
What version of Procurement are you using? On what operating system?
Version 1.9.0 on Windows 7 64-bit
What steps will reproduce the problem?
1.Authenticating 
XXXXXXXXX@XXXXXX.com                              
                   

2.Loading 
characters...                                 �
�                                   
3.[Error] There was an error deserializing the object of type 
System.Collections.Generic.List`1[[POEApi.Model.JSONProxy.Character, 
POEApi.Model, Version=1.9.0.0, Culture=neutral, PublicKeyToken=null]]. 
Encountered unexpected character '<'.

What is the expected output? What do you see instead?
I expect to log in to procurement but it hasn't logged in once since 
downloading it and I tried everything I can, such as re-installing, with no 
luck.

Please paste the contents of your DebugInfo.log file below if applicable.
To minimize the size of the file, delete your existing debuginfo.log file,
before replicating the issue.

[06-02-2015 10:13] System.Runtime.Serialization.SerializationException: There 
was an error deserializing the object of type 
System.Collections.Generic.List`1[[POEApi.Model.JSONProxy.Character, 
POEApi.Model, Version=1.9.0.0, Culture=neutral, PublicKeyToken=null]]. 
Encountered unexpected character '<'. ---> System.Xml.XmlException: Encountered 
unexpected character '<'.
   at System.Xml.XmlExceptionHelper.ThrowXmlException(XmlDictionaryReader reader, XmlException exception)
   at System.Runtime.Serialization.Json.XmlJsonReader.ReadAttributes()
   at System.Runtime.Serialization.Json.XmlJsonReader.Read()
   at System.Xml.XmlBaseReader.IsStartElement()
   at System.Xml.XmlBaseReader.IsStartElement(XmlDictionaryString localName, XmlDictionaryString namespaceUri)
   at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalIsStartObject(XmlReaderDelegator reader)
   at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalReadObject(XmlReaderDelegator xmlReader, Boolean verifyObjectName)
   at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
   --- End of inner exception stack trace ---
   at System.Runtime.Serialization.XmlObjectSerializer.ReadObjectHandleExceptions(XmlReaderDelegator reader, Boolean verifyObjectName, DataContractResolver dataContractResolver)
   at System.Runtime.Serialization.Json.DataContractJsonSerializer.ReadObject(XmlDictionaryReader reader)
   at POEApi.Model.POEModel.GetCharacters()
   at Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass2.<Login>b__1()
   at System.Threading.Tasks.Task.Execute()

Original issue reported on code.google.com by alaa1als...@gmail.com on 6 Feb 2015 at 8:18

GoogleCodeExporter commented 8 years ago
Solved the issue, I use a proxy server to hide my ip address and that was the 
reason causing this problem. Once I used a network without using a proxy server 
it worked. You should add an option for the program to use a proxy ip address 
and port because some users use it. I saw another guy with the same issue and 
you suggested trying sessionID to login and he claimed that it have worked. 
Well, I'm sure that was by coincidence because he wasn't using a proxy server 
by then since I had the same exact error code and trying sessionID to login 
failed. 

Original comment by alaa1als...@gmail.com on 6 Feb 2015 at 9:23

GoogleCodeExporter commented 8 years ago
Hi,

Procurement moved to github over a year ago, and I have not been monitoring the 
google code issue tracker. 

Google is shutting down google code in 3 weeks time, as such I am disabling 
this issue tracker as I will not be able to reply after that date.

If you are still having issues please relog your issue on Procurement's github 
page at https://github.com/Stickymaddness/Procurement

Original comment by stickymaddness on 30 Jul 2015 at 3:45