You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After republishing an app on the Shoutem builder, in around 25% of the time, this results in a misconfigured app configuration file.
We debugged the issue and found out that the problem is a malformed app config json file. On the left you can see a non working app, and on the right side is the config as it should be. So our assumption is that there are some issues on the server side when constructing the app config file. Unfortunately we cannot debug any further here. And manually patching the malformed config file, seems to be error prone.
Later on in the middleware when the config file is parsed, on line 67 the screenLayout is retrieved, which results in undefined since our screen array is empty. The result is an empty screen. As we have experienced this only happens with shoutem.web-view.WebViewScreen.
The text was updated successfully, but these errors were encountered:
After republishing an app on the Shoutem builder, in around 25% of the time, this results in a misconfigured app configuration file.
We debugged the issue and found out that the problem is a malformed app config json file. On the left you can see a non working app, and on the right side is the config as it should be. So our assumption is that there are some issues on the server side when constructing the app config file. Unfortunately we cannot debug any further here. And manually patching the malformed config file, seems to be error prone.
Later on in the middleware when the config file is parsed, on line 67 the screenLayout is retrieved, which results in undefined since our screen array is empty. The result is an empty screen. As we have experienced this only happens with shoutem.web-view.WebViewScreen.
The text was updated successfully, but these errors were encountered: