Description
When deploying the login-id screen, the value for branding.settings.logoUrl is always undefined. This is unexpected, as when retrieving the branding settings through the API, it is defined. In the example, you guys are extracting it from a CSS variable, but it should be coming through the context object as well if I'm not mistaken (it is accounted for in the types).
Reproduction
Deploy the login-id screen using the Auth0 cli. Enable all additional data (can also do this in the management UI) for the screen. Note that the context object provided to the client doesn't include the logo. It should be alongside colors, as in the API response. See the following example snippet from the context object.
{
"branding": {
"settings": {
"colors": {
"page_background": "#000000",
"primary": "#635dff"
}
}
}
}Environment
- @auth0/auth0-acul-react@1.2.0
- react/react-dom@18.2.0
- Chrome 145.0.7632.18
- Other modules/plugins: NA
Description
When deploying the login-id screen, the value for
branding.settings.logoUrlis alwaysundefined. This is unexpected, as when retrieving the branding settings through the API, it is defined. In the example, you guys are extracting it from a CSS variable, but it should be coming through the context object as well if I'm not mistaken (it is accounted for in the types).Reproduction
Deploy the
login-idscreen using the Auth0 cli. Enable all additional data (can also do this in the management UI) for the screen. Note that the context object provided to the client doesn't include the logo. It should be alongside colors, as in the API response. See the following example snippet from the context object.{ "branding": { "settings": { "colors": { "page_background": "#000000", "primary": "#635dff" } } } }Environment