search

TheGoddessInari / hamsket

Free and Open Source messaging and emailing app that combines common web applications into one.
GNU General Public License v3.0
883 stars 55 forks source link

Teams loses login status each reboot #235

Open ngoonee opened 3 years ago

ngoonee commented 3 years ago

I have seen https://github.com/TheGoddessInari/hamsket/issues/231 and am already using hamsket-nightly via this PKGBUILD https://aur.archlinux.org/packages/hamsket-nightly-bin which basically downloads the nightly release and copies it to the right place.

Teams remembers my login but I am always asked to input my password. This was not previously an issue (same version of hamsket-nightly-bin) but I added a new Teams service in hamsket (the old one had a cache corruption problem, Microsoft's fault, also happened in browser) and since then this has happened.

TheGoddessInari commented 3 years ago

I don't have a Teams login, so you may have to git bisect this yourself.

TheGoddessInari commented 3 years ago

Electron apps like this (using the built in storage instead of a special third party solution for everything) CAN randomly lose state, but that's wholly dependent on your operating system, filesystem, and how well it handles things like OS crashes, suspend, power loss, etc.

This should never occur on every restart of the program. It's more likely to have a less-stable underlying configuration with OS/filesystem. Hamsket currently fully depends on the built in storage stuff, as Rambox does, and there won't be any particular difference there.

Eventually I'd like to use something more portable, smaller in generated size, but there are also security issues there (some people want encryption and other protections there), so unfortunately it's relatively low priority as it'd require losing all data and is highly likely to break in a change, and it'd generally require actually discussing how to design and implement things like encrypted data store properly, which I'm open to.

But realistically, if your OS isn't losing data, it's most likely Microsoft choosing to do this. Have you tried different User Agents/platforms?