"Failed getting Registration Token" leads to assertion failure in BitlBee

[robert-scheck]

With 2290013 I'm seeing the following warning in BitlBee:

[00:09:41] -!- (process:8880): Json-CRITICAL **: json_node_get_object: assertion `node != NULL' failed
[00:09:41] -!- ** (process:8880): CRITICAL **: skypeweb_string_get_chunk: assertion `haystack && start' failed
[00:09:41] <@root> skypeweb - Error: Failed getting Registration Token
[00:09:41] <@root> skypeweb - Signing off..

Maybe there's a way for the future to avoid the assertion failure?

[EionRobb]

https://github.com/EionRobb/skype4pidgin/tree/master/skypeweb#issues

[robert-scheck]

@EionRobb, the "Failed getting Registration Token" shows up here about once a day and a reconnect works normally. I just would like to get rid of the assertion failures using this issue (do they really need to be thrown?).

[EionRobb]

Switching to the alternate auth will skip the Registration Token method entirely. The assert is necessary to assert that the login succeeded

[dequis]

If you're using systemd socket units you'll want something like this https://github.com/bitlbee/bitlbee/commit/bdf9214217579534c9ea6e906ddecaba136e2916

If using (x)inetd i think you can't do much about it

[sdfg2]

@EionRobb how would I enable the alt-login method for spectrum?

[Thaodan]

Just tested this, this issue no longer happens.

[Thaodan]

@EionRobb how would I enable the alt-login method for spectrum?

@sdfg2: Did you try Spectrum2/Setting libpurple plugins configurations ?