Wow, that looks like an odd bug not to have noticed before. Thanks. Alas I am out of action till probably late May and can't see myself attending to much in this space before then, but hopefully sometime after I'll clean up some of these PRs and the codebase.
Last I looked at it I was getting a load of errors and unable to login even with the registration work around and it was going to take some serious time to diagnose again. The pitfalls of a reverse engineered API.
I'm starting to w onder if a headless call to Chrome or Firefox isn't a needed a workaround our login issues.
Wow, that looks like an odd bug not to have noticed before. Thanks. Alas I am out of action till probably late May and can't see myself attending to much in this space before then, but hopefully sometime after I'll clean up some of these PRs and the codebase.
Last I looked at it I was getting a load of errors and unable to login even with the registration work around and it was going to take some serious time to diagnose again. The pitfalls of a reverse engineered API.
I'm starting to w onder if a headless call to Chrome or Firefox isn't a needed a workaround our login issues.