0.2.4: cannot connect

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start mobbler
2. Try to connect to last.fm

What is the expected output? What do you see instead?
A message stating that the connection was stablished

What version of the product are you using? On what operating system?
A message stating that ther is en error with the connection.

Please provide any additional information below.
The error message is the string STR_mobbler_note_comms_error with the 
suffix "<connect>". It is not a password related problem, because when I 
put a wrong password I get a different error message 
(STR_mobbler_note_bad_auth)

Toni

Original issue reported on code.google.com by tonilounavarro on 31 Aug 2008 at 7:37

[GoogleCodeExporter]

There is no problem connecting with version 0.2.0, so it must be a 0.2.4 
related 
problem.

Original comment by tonilounavarro on 31 Aug 2008 at 7:47

[GoogleCodeExporter]

Hi Toni,

That sounds quite serious.

You should only get an error like this if a http transaction fails.  0.2.4 now 
also
connects to the last.fm web services API, for the love/ban stuff, so there is 
now one
more transaction going on now when you connect.  I have been using this for a 
about a
week now with my N78 and not had any problems, some friends with an E71 and an 
N95
have also tried very recent dev versions and it's all been fine.

I'm hoping that the last.fm web services server was down when you tried to use 
it. 
Could you try again, please?  Failing that.  What phone do you have?

On a side note;  The language files are a little messed up at the moment 
because it
is quite difficult to maintain these 20 files as the English changes and gets
extended.  I have a friend that is going to solve this for me though so this 
should
be better in future.

Michael

Original comment by eartle@gmail.com on 1 Sep 2008 at 7:31

[GoogleCodeExporter]

Hi

I have just tried the connection with 0.2.4 with the same error: 
STR_mobbler_note_comms_error + "<connect>". I tried it with 0.2.0 and connected 
with 
no problem.

I have a Nokia N81 with firmware 11.0.045.

Toni

Original comment by tonilounavarro on 1 Sep 2008 at 2:52

[GoogleCodeExporter]

Mmm... Strange...

When I try to connect to last.fm with 0.2.4 I get the above error message, but 
the 
connection seems to establish and the phone sends the off-line scrobbled tracks 
to 
last.fm. Even the love/ban thing works...

However, I can't see the "Start a new station" menu items. It seems the phone 
is not 
aware it is connected, but it sends data to the web.

Toni

Original comment by tonilounavarro on 1 Sep 2008 at 3:26

[GoogleCodeExporter]

Just got a friend to try it on her N81 and she says that it crashes just after 
the
select connection dialog.  Nightmare!  I have no idea why this would not work 
on the
N81 when it works on all the other devices I have tried it on.

I will have a look into this and see what I can do, but I have no leads at the 
moment.

Original comment by eartle@gmail.com on 1 Sep 2008 at 3:26

• Changed state: Accepted

[GoogleCodeExporter]

Oh.  Didn't see your last message.  That gives me a little more to go on.  
Cheers.

Original comment by eartle@gmail.com on 1 Sep 2008 at 3:33

[GoogleCodeExporter]

Yes, mobbler sometimes crashes also for me, but in a random way. I can't see 
the 
pattern. If I can figure something I'll post.

Toni

Original comment by tonilounavarro on 1 Sep 2008 at 3:39

[GoogleCodeExporter]

When you say that you are able to love tracks, did you actually wait for the 
track to
scrobble?  This is when the web services love call is actually made.

I think that the web services handshake is failing on your phone (still have no 
idea
why) and when it tries to send the love call it will probably crash as it 
doesn't
have the session key.

Original comment by eartle@gmail.com on 1 Sep 2008 at 5:22

[GoogleCodeExporter]

Hi

Forget my comment about the love track function working.

What I have observed so far:

(1) Mobbler records offline played tracks ok. The queued tracks counter gets 
updated,
(2) Whem I try to connect to last.fm: the connection dialog shows up.
(3) I select my wifi connection and I get the "<connect>" error. However, the 
scrobbled track shows on the web as just listened.
(4) Moreover, the scrobbled tracks counter is not always cleared. And the sent 
tracks counter is not always updated.
(5) When I close mobbler and reconnect to last.fm, sometimes I get a crash as 
your 
friend stated.

Toni

Original comment by tonilounavarro on 1 Sep 2008 at 7:32

[GoogleCodeExporter]

STR_mobbler_note_comms_error on N78 with latest firmware :(

Original comment by spassov on 1 Sep 2008 at 7:34

[GoogleCodeExporter]

Thanks for the details.  I have made some changes to clean up the code based on 
them.
 Effectively, as the connect is failing, Mobbler now remains in the unconnected
state, as it should do, so that this strange behaviour does not happen anymore. 
 This
doesn't fix the problem that it is not connecting for you though.

The real problem is that the web services http transaction is failing.  I am 
inclined
to say that, if a http transaction is failing, then it is out of my hands and 
it is
an error somewhere between Mobbler and last.fm, but that is not a very helpful
approach.  So instead I have made a version of Mobbler that will tell you why 
the
transaction has failed and will send it to your gmail.

Original comment by eartle@gmail.com on 2 Sep 2008 at 12:28

• Changed title: 0.2.4: cannot connect
• Changed state: Started

[GoogleCodeExporter]

Hi

I tested the modified version. It tries to connect, fails and shows the error 
message rls_string STR_mobbler_note_lastfm_error. So maybe last.fm server is 
down by 
now.

I'll continue testing and let you know.

Toni

Original comment by tonilounavarro on 2 Sep 2008 at 3:30

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It's connecting for me.  I've sent you a version that will tell you what the 
last.fm
error actually is.  I think I should be adding all this error printing stuff 
anyway.

Original comment by eartle@gmail.com on 2 Sep 2008 at 4:30

[GoogleCodeExporter]

Ok, found and working!

The error was "Invalid authentication token supplied. Please check 
username/password".

So I rechecked the username and password. The problem was the initial capital 
letter 
from my username! That is,

* "tonilou" works with 0.2.x forall x
* "Tonilou" works with 0.2.x, x <= 3 and fails with 0.2.4

I assume the authentication method has changed someway in 0.2.4 and now it 
honours 
the username capitalization.

Thanks!

Original comment by tonilounavarro on 2 Sep 2008 at 6:43

[GoogleCodeExporter]

Good news!

When connecting Mobbler handshakes with three last.fm services; scrobble API, 
radio
API, web services API.  The web services API was only added in 0.2.4.  It seems 
that
the other two don't care about case, but this one does.

Still doesn't explain my friend's phone crashing, but I will look into that 
seperately.

Cheers!

Original comment by eartle@gmail.com on 2 Sep 2008 at 6:55

• Changed state: Invalid

[GoogleCodeExporter]

I thought about this some more on the way home and realised that this IS 
actually a
bug in Mobbler.

Usernames should always be case insensitive.  The problem with the new web 
services
API is that the username is hashed as part of the authentication.  different 
cases
create different hashes and it seems that last.fm expects you to hash a lower 
case
version of the username.

I have changed it so that when you enter your username Mobbler converts it to 
all
lower case for you.

I will put the fix in the next release, but until then the username should 
always be
entered in lower case.

Thanks again for raising this.

Original comment by eartle@gmail.com on 2 Sep 2008 at 8:56

• Changed state: Started

[GoogleCodeExporter]

Got the same issue in Nokia E51. Fixed it by editing my username. After that I
connected and was able to stream a station over a Wi-Fi connection. Great!

Original comment by marti...@gmail.com on 4 Sep 2008 at 8:36

[GoogleCodeExporter]

same issue and fix with an e71. Many thanks!

When you enter your username in mobbler it sets the first character to 
upper-case by
default, I had to go back and change it

Original comment by mike%alv...@gtempaccount.com on 4 Sep 2008 at 3:26

[GoogleCodeExporter]

still doesnt work on my e71...even after changing the first character to 
lower-case!!

Original comment by jonathan...@gmail.com on 19 Sep 2008 at 4:51

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Thanks a lot!

Fixed it by editing the first character!

Original comment by oesc...@gmx.de on 17 Oct 2008 at 8:17

[GoogleCodeExporter]

The username bug has been fixed and Mobbler 0.3.0 and should also not crash if
connection is unsuccessful.

If there are problems connecting then it is normally down to your data 
connection so
try using different access points to see if you get different results.

Original comment by eartle@gmail.com on 19 Oct 2008 at 12:10

• Changed state: Fixed