awasthi / corporateaddressbook

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

org.xmlpull.v1.XmlPullParserExecption: PI must not start with xml (postion:unknown@1:147 in java.io.InputStreamReader@xxxxxxx) #69

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. Download and install app
2. Input credentials and server information
3. Select "login" after adding credentials and server information

What is the expected output? What do you see instead?

I exepected no errors.  

Instead I see:

org.xmlpull.v1.XmlPullParserExecption: PI must not start with 
xml(postion:unknown@1:147 in java.io.InputStreamReader@xxxxxxx)

Then when a GAL search is performed, I get the message "No Matches Found". It 
doesn't matter what name I search.

What version of the product are you using?

1.2.3

What version of Android are you running?
ver 2.2.1 FRG83D

What version of Exchange are you connecting to?

Exchange 2010 SP1

Please provide any additional information below.

** IMPORTANT: After 35 - 45 minutes, I am able to search the GAL **

During my first time installing & configuring the app, tried using IP addresses 
as well as DNS of all our front end CAS servers.  Credentials are correct, as I 
have deliberately inuput a bad password and received an authentication failure.

Also everytime you choose login within the app, a new device entry is populated 
under the user account (this can been seen by logging into OWA, Options-->See 
all options-->Phone).  By default no more than 10 devices are permitted.  The 
user will be made aware if this threshold is reached.

Original issue reported on code.google.com by agent...@gmail.com on 20 Aug 2011 at 2:02

GoogleCodeExporter commented 9 years ago
Hi there

Thank you for your message and trying out my app. I am sorry about the issues 
that you are having. A few comments on this

- org.xmlpull.v1.XmlPullParserExecption: PI must not start with 
xml(postion:unknown@1:147 in java.io.InputStreamReader@xxxxxxx)

This seems like an error with malformed XML being returned from your Exchange 
server. I have seen errors like this before and typically it is because the XML 
parser sees an entry in a place where it is not expected, and chokes on it. I 
can try to work around this, but I will need to see the XML it chokes on. I can 
send you a DEBUG build, which will generate this XML, allow you to edit it (to 
remove any personal information) and send it across to me. Will you be willing 
to install such a build?

- The issue with the app adding multiple accounts
You should only see this issue if you add and remove accounts from the app. If 
the same account settings are used, the app will re-use the existing 
connection. However everytime the connection setting is edited, the app creates 
a new entry. 
My app does not currently remove the old entry, I think that will be something 
I can add in a later release

Regards
Vivek

Original comment by viveki...@gmail.com on 23 Aug 2011 at 10:48

GoogleCodeExporter commented 9 years ago
Vivek, I appologize for not searching first. Issue 71 is the same as this. I 
can help with a debug build if you're willing.

Original comment by phalko...@gmail.com on 20 Oct 2011 at 4:55

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?

1. Download and install app
2. Input credentials and server information
3. Select "login" after adding credentials and server information

What is the expected output? What do you see instead?

I exepected no errors.  

Instead I see:

org.xmlpull.v1.XmlPullParserExecption: PI must not start with 
xml(postion:unknown@1:147 in java.io.InputStreamReader@xxxxxxx)

Then when a GAL search is performed, I get the message "No Matches Found". It 
doesn't matter what name I search.

What version of the product are you using?

1.2.3

What version of Android are you running?
ver 2.3.5

What version of Exchange are you connecting to?

Exchange 2010 SP1

I have exactly the same probleme.
On the other side, i have other users with the same kind of phone and the same 
kind of account and it's ok with your apps.

I'm really annoyed with this problem.

Thanks a lot.
SR.

Original comment by sravi...@gmail.com on 23 Jan 2012 at 12:00

GoogleCodeExporter commented 9 years ago
Hi,

Same issue here. Each try seems to add a phone entry (shown in outlook web 
access). In 'mobile phone details' in OWA I notice:
Access state:   Gathering client information.
Access set by:  Device Grouping Permissions
Further, very litte info is recorded in this entry, while the 'real' mail entry 
has all details filled, amongst others:
Device name:    GT-I9070
Device model:   GT-I9070
Mobile network: NL KPN  
Device type:    SAMSUNGGTI9070
Device ID:  ***
Device IMEI:    ***

Device OS:  Android
Device language:    Nederlands
User agent: SAMSUNG-GT-I9070/100.20306

Access state:   Access Granted
Access set by:  Global Permissions

Our company forces policies on devices using exchange, like setting a password. 
Could the issue be related to this?

Joep.

Original comment by jsu...@gmail.com on 17 Sep 2012 at 7:38

GoogleCodeExporter commented 9 years ago
Issue 73 has been merged into this issue.

Original comment by dan.matt...@gmail.com on 22 Sep 2012 at 2:03

GoogleCodeExporter commented 9 years ago
Can you folks please try the latest build from the Android market. This should 
be fixed with that.

Thanks
Vivek

Original comment by viveki...@gmail.com on 25 Sep 2012 at 11:46

GoogleCodeExporter commented 9 years ago
Hi Vivek,

Issue fixed, it works as it is supposed to!
My first impression is that it is great product, showing all fields. In 
contrast, the ejay product only displays selected fields (not the one with the 
cell phone numbers in my company).

Very valuable app, I will make a donation shortly.

Thank you very much & keep up the good work!

Joep

Original comment by jsu...@gmail.com on 26 Sep 2012 at 1:16

GoogleCodeExporter commented 9 years ago

Original comment by dan.matt...@gmail.com on 26 Sep 2012 at 1:32