OF seems to have changed their behavior when detecting that an API is trying to communicate with them. I tested it now a couple of times and I'm sure that the current behavior is as follows:
Every needed parameter will get added to the auth.json
After starting the program and trying to communicate with OF, they will time you out, resulting in you having to log in again on the browser, resulting in a new sess value which will always get invalidated as soon as you try to communicate with them via OnlySnap again.
I don't know if this invalidates OnlySnap completely for usage or if there could be an alternative to avoid this behavior.
OF seems to have changed their behavior when detecting that an API is trying to communicate with them. I tested it now a couple of times and I'm sure that the current behavior is as follows:
I don't know if this invalidates OnlySnap completely for usage or if there could be an alternative to avoid this behavior.