Closed truenicoco closed 2 years ago
What format are you providing your username in? You appear to be forcing SOAP authentication at the start, but the automatic renewal is using the Live (legacy) auth, which does not support application passwords -- this is presumably because you're passing in a Skype username instead of your Microsoft account's email address, and providing the latter should both avoid needing to force it and handle the renewal correctly.
Oh I am indeed providing my Skype username. I don't even know what my associated live email is. Thanks for your reply, I'll investigate and report back when I have time to work on this again.
EDIT: Logging in with the email address seems to fix the issue. Thanks for your help, and the solution was to remove my ugly bogus workaround, which is nice.
Context: I am using your library for an XMPP gateway and it works (almost) great. My account was created a long time account, before skype was bought by microsoft, but is now linked to a microsoft account. Since I had trouble logging in, I set up an application password. To successfully login, I had to hack something like this:
which works and can send/receive messages (with some other asyncio/threading hacks that I think are not relevant here) for a few days.
After a while, I guess when the connection token has to be refreshed, I have this traceback:
I am thinking this is probably related to the login hack I had to use. I think I can work around this by just re-logging like I do when this happens, but was wondering if there was an easy, cleaner fix that comes to mind. The library is quite complex and I must confess I do not master all the different auth options.