Error with Themes

Hi Everyone,
I am using the Qr code Scanner component in marketplace, to further enhance my app. We wanted the buttons to be coloured, so we played around with custom themes. We have come into this issue though.


At first this was only on the backendless viewer, but we have now found this on our editing page as well.

App Id: 0EE54AB3-AC00-4219-840A-995C9ABF7D1D

Thank You,
Tyler

I’m part of Tyler’s development team and we’re currently working on an app utilizing the QR Code Scanner component from the marketplace. Recently, we implemented a custom theme to enhance the UI design. However, we’ve encountered the issue that @Tyler_Scott previously mentioned.

After some investigation, I was able to locate the styles.less file referenced in the error message:

Theme Link: UI Builder Theme

The problem appears to be related to the theme’s modifications, specifically concerning button styles. It seems that the custom theme is causing unintended side effects, which could potentially be conflicting with the QR code scanner component’s own CSS or styles.

Could you please assist us in identifying the root cause of this issue and advise on how to resolve it? Our goal is to ensure that the custom theme works as intended, without negatively impacting the appearance or functionality of the QR code scanner component or any other app elements.

I hope this additional context proves useful for troubleshooting.

Best regards,
Tom

Hi Backendless Team,

Just wanted to update you on the issue I previously mentioned. It appears that the error has unexpectedly resolved itself. The QR Code Scanner component, along with the preview and login functions, is now working perfectly — no visual glitches or functional issues as before.

It’s a bit strange since we haven’t made any changes to the theme or code that would explain this fix. Is it possible that this was caused by a temporary caching issue or some transient conflict in the UI Builder?

At this point, everything seems to be functioning as expected, but I thought it might be worth sharing this update in case the issue resurfaces.

Thanks again for your support,
Tom