loqui / im

Loqui IM allows you to use all your chat accounts in just one FirefoxOS or Ubuntu Touch app.
https://loqui.im
304 stars 112 forks source link

authentication error #865

Closed BlackForest2015 closed 8 years ago

BlackForest2015 commented 8 years ago

Dear all,

since a few days I can't connect to WhatsApp. Tells me "Authentification error"

Using ZTEOpenC, firefoxOS 1.3

TitanNano commented 8 years ago

can you please provide us some logs.

2015-11-02 9:46 GMT+01:00 BlackForest2015 notifications@github.com:

Dear all,

since a few days I can't connect to WhatsApp. Tells me "Authentification error"

Using ZTEOpenC, firefoxOS 1.3

— Reply to this email directly or view it on GitHub https://github.com/loqui/im/issues/865.

BlackForest2015 commented 8 years ago

Sorry, I am only a user, not a coder, I have no idea how to do that. If there's a more or less simple way to do that I will not hesitate to provide.

tibtab commented 8 years ago
  1. Connect your device via USB with your PC
  2. Open your Firefox-Browser
  3. Press SHIFT + F8 -> the WebIDE opens
  4. Choose your device on the right side in the drop down list
  5. Accept the connection request on your phone
  6. In the WebIDE choose loqui in the drop down list on the left side
  7. Then go to "Console" and wait until your problem occurs
  8. Copy the error displayed by the WebIDE
BlackForest2015 commented 8 years ago

Am 02.11.2015 um 15:14 schrieb tibtab:

  1. Connect your device via USB with your PC
  2. Open your Firefox-Browser
  3. Press |SHIFT| + |F8| -> the WebIDE opens
  4. Choose your device on the right side in the drop down list
  5. Accept the connection request on your phone
  6. In the WebIDE choose loqui in the drop down list on the left side
  7. Then go to "Console" and wait until your problem occurs
  8. Copy the error displayed by the WebIDE

— Reply to this email directly or view it on GitHub https://github.com/loqui/im/issues/865#issuecomment-153028185.

Problem, my device is not shown on WebIDE, the mozilla help tells me in that case to click on “Remote debugging” in the developer mode, but I don’t have the checkbox remote debugging. I find external debugging and contacts debugging out... and a lot more although the mozilla held says I should have that checkbox on ffos1.3 and lower.

Sorry, I try my best

TitanNano commented 8 years ago

@BlackForest2015 it should be a selectbox at the top of the dev-settings.

TitanNano commented 8 years ago

@BlackForest2015 sorry my mistake. It's a checkbox indeed. You should be able to find it between "Show time to load" and "Wi-Fi output in ADB"

tibtab commented 8 years ago

I remember that when i still had fx os 1.3 I couldn't find "Remote debugging" as well, it should be "external debugging"

BlackForest2015 commented 8 years ago

This is quite exciting, I learned a lot! I had a lot of problems by install the USB driver. tibtab was right, the nam eof the checkbox is “external debugging” and Jovan was right, it’s located between “Show time to load" and "Wi-Fi output in ADB". So I copied everything I found on ffWebIDE:

B#ŽˆžÆ!à?‹› r ù ~ BinaryWriter.prototype._write@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:4743 [BinaryWriter] coseme.js:3541 Received socket data: 11 bytes! ~ BinaryReader.prototype.onSocketData@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:5179 [BinaryReader] coseme.js:3541

~ BinaryReader.prototype._readNextTree@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:5279 [BinaryReader] coseme.js:3541 Authentication failed! ~ retryOrFail@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6277 [auth] coseme.js:3541 Authentication failed: auth-failed ~ methodList.auth_login/<@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:7895 [ConnectionManager]

gargsms commented 8 years ago

I am thinking of making a Wiki entry for this thing.It is really hard for new users to get started and provide us with logs. My Flame is currently flashed with an unstable FxOS v3.0 image. Once I reach home, in the next few days I should be able to flash a new stable buld and work on it.

 On Monday, 2 November 2015 9:26 PM, BlackForest2015 <notifications@github.com> wrote:

This is quite exciting, I learned a lot! I had a lot of problems by install the USB driver. tibtab was right, the nam eof the checkbox is “external debugging” and Jovan was right, it’s located between “Show time to load" and "Wi-Fi output in ADB". So I copied everything I found on ffWebIDE:B#���Æ!à?��� r ù ~ BinaryWriter.prototype._write@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:4743 [BinaryWriter] coseme.js:3541 Received socket data: 11 bytes! ~ BinaryReader.prototype.onSocketData@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:5179 [BinaryReader] coseme.js:3541

~ BinaryReader.prototype._readNextTree@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:5279 [BinaryReader] coseme.js:3541 Authentication failed! ~ retryOrFail@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6277 [auth] coseme.js:3541 Authentication failed: auth-failed ~ methodList.auth_login/<@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:7895 [ConnectionManager]— Reply to this email directly or view it on GitHub.

TitanNano commented 8 years ago

@BlackForest2015 unfortunately that's not enough. Please connect with the WebIDE, open the console and click the reload button at the top of the WebIDE. This will print out the entire log from the application start.

TitanNano commented 8 years ago

@gargsms I just landed #867. you should add that to the wiki too. I think it's easier if people don't need to deal with the WebIDE

BlackForest2015 commented 8 years ago

I have no idea what I am really doing. Hope this is not my hidden Credit Card number ;-)

Received socket data: 11 bytes! ~ BinaryReader.prototype.onSocketData@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:5179 [BinaryReader] coseme.js:3541
<failure>
<not-authorized>
</not-authorized>
</failure>
 ~ BinaryReader.prototype._readNextTree@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:5279 [BinaryReader] coseme.js:3541
Authentication failed! ~ retryOrFail@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6277 [auth] coseme.js:3541
Authentication failed:  auth-failed ~ methodList.auth_login/<@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:7895 [ConnectionManager] coseme.js:3541
Disconnect sequence initiated... ~ methodList.disconnect@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:8252 [ConnectionManager] coseme.js:3541
Sending term signal to reader thread ~ methodList.disconnect@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:8253 [ConnectionManager] coseme.js:3541
Disconnected! undefined ~ methodList.disconnect@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:8260 [ConnectionManager] coseme.js:3541
Error invoking disconnect with ["undefined"] ~ call@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6519 [yowsupAPI] coseme.js:3541
Error details: TypeError: "_signalInterface is undefined" at .sendDisconnected@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:7439 > methodList.disconnect@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:8262 > call@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6517 > App.connectors.coseme/this.disconnect@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/loqui/connectors/coseme.js:65 > App.killAll@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/loqui/app.js:351 > @app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/loqui/bindings.js:79 > at.event.dispatch@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/meteor/blaze.js:2783 > at.event.add/m.handle@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/meteor/blaze.js:2726 >  ~ call@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6520 [yowsupAPI] coseme.js:3541
Write node called with  {"_tag":"presence","children":[],"attributes":{"type":"unavailable"},"_data":null} ~ self._writeNode@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:7569 [ConnectionManager] coseme.js:3541
Write node called with  {"_tag":"iq","children":[{"_tag":"status","children":[],"attributes":{},"_data":"."}],"attributes":{"to":"s.whatsapp.net","type":"set","id":"sendsetstatus_1","xmlns":"status"},"_data":null} ~ self._writeNode@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:7569 [ConnectionManager] coseme.js:3541
[l10n] #contactAdd is undefined. l10n.js:68
auth_login called for 4916095990270 ~ methodList.auth_login@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:7873 [ConnectionManager] coseme.js:3541
Connecting to: c2.whatsapp.net:5222 ~ openConnection@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6163 [auth] coseme.js:3541
SHOW main undefined undefined menu.js:297
Starting login... ~ tryLogin@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6179 [auth] coseme.js:3541
Sending stream start, features & authentication ~ tryLogin@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6184 [auth] coseme.js:3541
Waiting for stream start... ~ waitForAnswer@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6218 [auth] coseme.js:3541
<stream:features>
<receipt_acks>
</receipt_acks>
<w:profile:picture type="all">
</w:profile:picture>
<w:profile:picture type="group">
</w:profile:picture>
<notification type="participant">
</notification>
<status notification="true">
</status>
</stream:features>
 ~ BinaryWriter.prototype._write@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:4743 [BinaryWriter] coseme.js:3541
<auth mechanism="WAUTH-2" user="49***95990270">
</auth>
 ~ BinaryWriter.prototype._write@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:4743 [BinaryWriter] coseme.js:3541
Received socket data: 42 bytes! ~ BinaryReader.prototype.onSocketData@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:5179 [BinaryReader] coseme.js:3541
Got stream start! Waiting for challenge... ~ _processAnswer@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6239 [auth] coseme.js:3541
<stream:features>
</stream:features>
 ~ BinaryReader.prototype._readNextTree@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:5279 [BinaryReader] coseme.js:3541
Got the features. ~ _processAnswer@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6243 [auth] coseme.js:3541
<challenge>
÷õH‚¼mÍó(
ìë h}j¶à [</challenge>
 ~ BinaryReader.prototype._readNextTree@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:5279 [BinaryReader] coseme.js:3541
Got the challenge! Sending answer... ~ _processAnswer@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6247 [auth] coseme.js:3541
nonce (latin1): ÷õH‚¼mÍó(
ìë h}j¶à [ ~ KeyStream.getKeys@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6413 [KeyStream] coseme.js:3541
password (base64): MG1FHJAU+ucj4ZCoefPFsYtnSHc= ~ KeyStream.getKeys@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6414 [KeyStream] coseme.js:3541
Keys: {"outputKey":{"$super":{"$super":{}},"words":[1107444757,-1208428814,-2108855070,2057056233,-948348185],"sigBytes":20},"outputHMAC":{"$super":{"$super":{}},"words":[-1109213001,-834070107,-606912339,-2040273711,1846807755],"sigBytes":20},"inputKey":{"$super":{"$super":{}},"words":[1959837003,-740245364,670798895,-905291546,-867745674],"sigBytes":20},"inputHMAC":{"$super":{"$super":{}},"words":[1391136404,-653664404,115284007,-1895991242,811148040],"sigBytes":20}} ~ KeyStream.getKeys@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6434 [KeyStream] coseme.js:3541
<response>
–a2e -áÒTƒýÎ|_2&½œ“±ûŸ  1‘ ßx ëž_z!0µ:ëA‰'’¡ j Æ ­-ƒ§.ê$ê
¬zžUH¾ç½DIê87_½{qê¤t÷>˜u_rÌ`#^b;OM|†\'Û|Þјç*ý¦Ãéý1Ë-ó’´àrlpIî</response>
 ~ BinaryWriter.prototype._write@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:4743 [BinaryWriter] coseme.js:3541
Received socket data: 11 bytes! ~ BinaryReader.prototype.onSocketData@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:5179 [BinaryReader] coseme.js:3541
<failure>
<not-authorized>
</not-authorized>
</failure>
 ~ BinaryReader.prototype._readNextTree@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:5279 [BinaryReader] coseme.js:3541
Authentication failed! ~ retryOrFail@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:6277 [auth] coseme.js:3541
Authentication failed:  auth-failed ~ methodList.auth_login/<@app://{b98e8002-ef00-407f-94ea-e5dd73ed64b6}/scripts/mozillahispano/coseme.js:7895 [ConnectionManager]
cmeerw commented 8 years ago

Which version of Loqui IM are you using? You really need to update to the latest version of Loqui IM!

BlackForest2015 commented 8 years ago

I don't understand this question. I am using loqui since a few months and never needed an update so far, I was convinced that this App will update automatically, so I was wrong?

Am 02.11.2015 um 19:10 schrieb Christof Meerwald:

Which version of Loqui IM are you using? You really need to update to the latest version of Loqui IM!

— Reply to this email directly or view it on GitHub https://github.com/loqui/im/issues/865#issuecomment-153105080.

TitanNano commented 8 years ago

Yes you are right, you should get new updates automatically. Can you please check your Loqui version? open the app > go to the aside menu > select settings > select info.

cmeerw commented 8 years ago

Unfortunately, ZTE's Open C firmware is broken which means that you don't get any updates for apps installed via the marketplace. And the WhatsApp protocol changes from time to time making updates necessary.

BlackForest2015 commented 8 years ago

Sorry guys, my intention was not to steel anybody’s time, I am only a user, fan of FFOS and of the idea of mozilla.

So I uninstalled loqui at my ZTE OpenC, went to the marketplace and now it’s working again! I’m a little bit shocked because cmeerw wrote that ZTE OpenC’s firmware is broken. What does this mean? My device is more or less useless? Bad luck, so I have to watch for a new Smartphone using FFOS in my country.

Am 02.11.2015 um 19:29 schrieb Jovan Gerodetti:

Yes you are right, you should get new updates automatically. Can you please check your Loqui version? open the app > go to the aside menu > select settings > select info.

— Reply to this email directly or view it on GitHub https://github.com/loqui/im/issues/865#issuecomment-153117023.

cmeerw commented 8 years ago

It's mainly the update functionality that's broken in the ZTE Open C firmware. As mentioned in the camp-firefox forum, you could try installing http://svn.cmeerw.net/src/CheckUpdate/trunk/ to at least be able to manually update any installed apps. Another option is to install a community build from http://builds.firefoxos.mozfr.org/opencebay/