Closed GoogleCodeExporter closed 8 years ago
@silas: please check this issue.
Original comment by felix.bechstein
on 28 Oct 2010 at 6:43
next try :p
Original comment by felix.bechstein
on 28 Oct 2010 at 6:51
Doesn't happen for me. Maybee there was a temporary problem with meimbmw.de?
Are you still able to reproduce the issue?
Btw the last time sometimes I had the problem that the message was not
delivered even though it was sent successfully. So I'll try if I can fix this
by faking the connector's user agent. But the problem described here should be
another thing...
Original comment by silas.gr...@gmail.com
on 28 Oct 2010 at 7:04
Ok, seems to be reproducable now. But only for the first time I try to send a
message. The second try works... I'll have a look at that.
Original comment by silas.gr...@gmail.com
on 29 Oct 2010 at 10:08
Hi! Since yesterday, it always fails when I try to send SMS :-(
Original comment by Andy.Mi...@googlemail.com
on 29 Oct 2010 at 10:24
Hi again, it seems that it connector didn't check the username and the password
because the failure occurs even if I use a wrong username/password...
Original comment by Andy.Mi...@googlemail.com
on 30 Oct 2010 at 8:10
I expect the bug to be in a generic http request method, so it occurs even in
the login part. I will add some more logging to figure out the reason this
weekend. Maybe there is some kind of a ssl problem.
Original comment by silas.gr...@gmail.com
on 30 Oct 2010 at 8:18
@silas: if ssl cert check fails, just have a look on the smspilot.ru or o2
connector.
with the new api calls you can add a few trusted certs the android system does
not trust.
Original comment by felix.bechstein
on 30 Oct 2010 at 9:07
Thanks Felix but the SSL check is ok. There's an IOException "SSL shutdown
failed: I/O error during system call, Broken pipe", see
https://issues.apache.org/jira/browse/HTTPCLIENT-951?focusedCommentId=12901563&p
age=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12
901563
Seems to be exaclty what is reported in this comment (doesn't happens all the
time...) the only question is how to workaround it.
Original comment by silas.gr...@gmail.com
on 30 Oct 2010 at 9:19
To correct myself: The SSL check is not ok but that's not an issue since I'm
using a DefaultHttpClient and this class accepts untrusted certificates (on
Android).
Original comment by silas.gr...@gmail.com
on 30 Oct 2010 at 9:20
I've written a quick'n'dirty port using Felix' Ultis.getHttpClient() that
seemed to work for me two times but the error occured again. A quick look in
Utils.java shows that Felix uses the buggy DefaultHttpClient, too.
Ideas anybody?
Original comment by silas.gr...@gmail.com
on 30 Oct 2010 at 11:12
After playing around a little bit at least on my device I think the issue
occurs after beeing idle for a while or after toggling wifi/3g/flightmode. In
this cases a second try afterwards works.
I have attached a new version with a dirty hack (in case of the IOException try
a second time and fire the WebSMSException only if this didn't work, too), that
might fix the issue.
Please let me know if it works for you, Andy
Original comment by silas.gr...@gmail.com
on 30 Oct 2010 at 1:15
Attachments:
Unfortunately ist still the same. Everytime "MeinBMW: Der Service ist down.
Bitte versuche es später noch einmal."
No matter if I use WLAN or 3g :-(
Original comment by Andy.Mi...@googlemail.com
on 30 Oct 2010 at 2:08
Strange :/ Please use the one attached. Do you also get the "broken pipe" error
above?
Did you try it repeatedly?
Original comment by silas.gr...@gmail.com
on 30 Oct 2010 at 2:20
Attachments:
Message: "MeinBMW: Not trusted server certificate"
Will be offine till tomorrow morning.
Original comment by Andy.Mi...@googlemail.com
on 30 Oct 2010 at 2:27
Wow, that's unexpected for me! Please try the new version.
Original comment by silas.gr...@gmail.com
on 30 Oct 2010 at 5:37
Attachments:
this untrusted exception is the one i ment above.
the websms-api can handle that.
Original comment by felix.bechstein
on 30 Oct 2010 at 6:32
Yes I know. That's the reason why I use it in the latest attached apk. The only
thing I don't understand is that this happens only for Andy...
Original comment by silas.gr...@gmail.com
on 30 Oct 2010 at 6:40
Hi! Tonight I tried and it seemed to work! Now I tried again and "MeinBMW:
Falsche Mailadresse oder Passwort angegeben" appears. But this should be a
problem from www.meinbmw.de because at the moment I cannot login from the
website, too.
Original comment by Andy.Mi...@googlemail.com
on 31 Oct 2010 at 10:04
That's good news! When the "wrong user" error appears the ssl encrypted
connection has already been established. Please also try the attached apk
because yesterday's version simply accepts all ssl certificates what is a
security hole. This one should accept only the correct MeinBMW one. If it works
for you you can stay with this connector version.
Before I commit it to the git repository for Felix to release the update in
Android market I'll wait for issue 239 since I'd like to limit messages in this
connector to 160 characters, too.
Original comment by silas.gr...@gmail.com
on 31 Oct 2010 at 1:17
Attachments:
please do not wait for this issue, as i do not have time to implement it for
the next weeks.
just check the length inside the connector and throw a exception if it's too
long.
that's what i did for innosend too.
Original comment by felix.bechstein
on 31 Oct 2010 at 4:05
Hi! It works like the version before! At the moment "MeinBMW: Falsche
Mailadresse oder Passwort angegeben" appears but the webside login is also not
possible at the moment!
Original comment by Andy.Mi...@googlemail.com
on 31 Oct 2010 at 4:39
Ok, thanks Andy. Let me know if you encounter any problems again.
Felix: Ok, I'll do that and commit the changes tomorrow. I misunderstood
jonaguera and thought that he would extend the API this weekend.
Original comment by silas.gr...@gmail.com
on 31 Oct 2010 at 5:10
Works fine now! Thanks a lot for your efforts!
Original comment by Andy.Mi...@googlemail.com
on 4 Nov 2010 at 7:30
No problem, thank you for the bug report. The fix is already commited, Felix
will release it to the market.
Original comment by silas.gr...@gmail.com
on 4 Nov 2010 at 7:34
Hi again! Since today sometimes the SMS will be sent and sometimes "MeinBMW:
Falsche Mailadresse oder Passwort angegeben" appears again :-( The website is
always working...
Original comment by Andy.Mi...@googlemail.com
on 6 Nov 2010 at 6:00
Really strange. I return "Falsche Mailadresse oder Passwort angegeben" only
when the error message on the website appears. So I assume there was really a
login problem on it.
Have you tried to rest your login data in WebSMS' settings?
Original comment by silas.gr...@gmail.com
on 7 Nov 2010 at 1:43
It's very strange, sometimes it works at the first time, sometimes only after
the 5th.
I reseted the login data many times...
Original comment by Andy.Mi...@googlemail.com
on 7 Nov 2010 at 4:12
Now a message has been sent altough the login on the website doesn't work !?
Original comment by Andy.Mi...@googlemail.com
on 7 Nov 2010 at 5:14
For me it seems that there is a problem with MeinBMW's login procedure that
causes the login to fail randomly.
Original comment by silas.gr...@gmail.com
on 7 Nov 2010 at 6:03
may be this is an caching issue?
cookies may live until the connector process was killed by the system.
Original comment by felix.bechstein
on 7 Nov 2010 at 9:01
Unlikely. The connector first tries to load the SMS page. If this fails
(because there's no valid session), there's a redirect to the login page. The
error above means that the login failed with a "wrong user" message on the
website.
Unfortunately I'm very busy during the next two or three weeks, so I won't be
able to investigate any further :/
Original comment by silas.gr...@gmail.com
on 8 Nov 2010 at 7:17
Just to inform you, the last days it worked fine without any failures!
Original comment by Andy.Mi...@googlemail.com
on 12 Nov 2010 at 6:33
Original issue reported on code.google.com by
Andy.Mi...@googlemail.com
on 28 Oct 2010 at 4:06