Hi there. I see that 8.3.3 is out, but I couldn't find a mention of this in the release notes. Could you please confirm whether this issue was fixed in this release?
Thank you. Just a feedback: while your workaround prevents the exception from throwing, the layout is sometimes broken as shown below:
Thank you. Are there any workarounds we could use for fixing this issue until we wait for the next release?
I sent you an email.
Thanks!
Hi, just an update. After a lot of debugging, I figured out that this happens when the app can't reach the API and it simply crashes upon startup if that's the case. From what I could tell, it's trying to call the API for localization purposes.
This is not ideal for my scenario, as I want the API address to be configured by the app user and saved in local storage. So in summary, I can't have the app hitting the API upon startup and crashing if it can't reach it. Ideally, the API should only be first called when the app user tries to log in.
What would be the best approach in this case?
