using jarvis with authentication doesn't work anymore after upgrade to 3.2

[schluo]

*Please note that you may restore an old layout via jarvis adapter configuration directly within ioBroker

Prerequisites / Voraussetzungen
Version: v3.2.0-rc.1
Console Error:
App-hGejAmgnwn Authentication failed! User not logged-in for "authentication"!

Describe the bug / Beschreibe den Fehler
After upgrading to 3.2.0-rc1 starting jarvis is only possible if deactivating authentication. Otherwise start screen hangs. Before upgrading login works fine.
Futhermore, some setting changes within jarvis GUI (maybe all pro-account setting?!) can not be saved. Save buttons/mouse pointer are deactivated)

[Zefau]

Authentication method has changed from 3.1 to 3.2. From which version are you coming?

What are your adapter settings specifically?

[schluo]

Authentication method has changed from 3.1 to 3.2. From which version are you coming?
3.1.8
What are your adapter settings specifically?
see attached screenshot

[Zefau]

Die Version v3.2.0-rc.2 sollte den Fehler beheben - bitte einmal prüfen. Sofern es behoben ist, gerne das Issue schließen.

---

The version v3.2.0-rc.2 should fix the bug - please verify. If the bug has been solved, you may close the issue.

[schluo]

Thank you for providing 3.2.0 rc2. Authentication issues is solved. The issue regarding pro-feature enablement still exists.

[Zefau]

It is greyed out because somewhere in the configuration is an error (which prevents from saving). I will add more info about the errors in the next release candidate (rc).

[Zefau]

Die Version v3.2.0-rc.3 sollte den Fehler beheben - bitte einmal prüfen. Sofern es behoben ist, gerne das Issue schließen.

---

The version v3.2.0-rc.3 should fix the bug - please verify. If the bug has been solved, you may close the issue.

[schluo]

It is greyed out because somewhere in the configuration is an error (which prevents from saving). I will add more info about the errors in the next release candidate (rc).

the issues seems to be related to css which I heavily used before I updated -->styles:null

[Zefau]

Oh, after updating to 3.2 everything got erased to null? Do you have a backup? I will fix the issue, thanks for the feedback

[schluo]

Slightly different situation. After uprading to 3.2 and during hanging start screen the browser console told me there were issues with the css dp. After replacing the content in the dp with {} I was able to start.
What should I do to reset all css related settings? I already tried blank, [] and {}.
After resetting I would be able to insert the backuped css content via webui.
BTW: thank you very much for your unbelievable swift feedbacks :-)

[Zefau]

v3.2.0-rc.4 fixes the incorrect way of converting the v3.1 structure to v3.2. Thus, you should be able to convert correctly when restoring a backup once you have rc.4 installed.