-
Notifications
You must be signed in to change notification settings - Fork 530
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing whitelabel themes in wizard #6804
Comments
I cannot seem to reproduce this. In the second screenshot, it seems that the custom colors are disabled. |
Also on the first screenshot there clearly is a whitelabel theme, I will try to repro it as well but if not then I'd say it's okay |
Good catch, but the color was enabled on the web. Could be just a server delay?
Yes, but should have two of them, one for mup4test and one for vaf |
So if I am correct, you had the both the web and Android clients open at the same time. The web client with the custom colors and the Android without. Is that right? If that is the case, I do not think it is related to the onboarding wizard. The Android client was respecting the settings it had. This might be an issue about syncing user settings.
If the custom colors were disabled on the Android client, the |
No, I setup the whitelabel on the web, put a nice color on it and after that I added the account to the android device and the theme wasn't shown up.
Yes, probably is related to the last question. Also the vaf theme took a while to appears into the wizard, I had to trigger the wizard 2/3 times To be honest, maybe isn't a thing with the wizard itself, but with the load process of custom themes. |
I mentioned it but maybe only in person but the wizard page grabs only what is already loaded: so it's probably a timing issue, whether |
On Android one of the whitelabel themes is missing and to show the first one, I had to trigger the wizard several times through the about dialog.
Steps to reproduce:
On Android:
Originally posted by @murilopereirame in #6770 (comment)
Test Notes
The text was updated successfully, but these errors were encountered: