I am wondering why the WebViewer works in my test app but not in my production app.
The test app is however tested in ai2.appinventor.mit.edu (=production env) with AI Companion, as the production app is tested in ai2-test.appinventor.mit.edu (=test env) by generating and downloading apk file (this is due to some functionality reasons because some components do not work in another env).
I am using TaifunTools.PathToAssets in both env, so should I refer to them differently in different environments?
From the pictures attached you can see that in test env the WebViewer lists nicely, but in production env there is only a part of the “Pura Vida Apps” logo visualized and nothing else.
There are not any overlapping fields either.
Suspecting that something to do with TaifunTools and/or the table.html which is loaded from there.
–clip–
There is one special thing to consider for HTML documents uploaded as assets into App Inventor: During development, you have to use the development path to the embedded HTML document.
file:///mnt/sdcard/AppInventor/assets/.html
Before building the app, use the production path .
Returns the path to the assets. This method is useful, if you want to access files from the webviewer component stored in the assets of the app. The method will return file:///android_asset/ in case the app is running after building the app as apk file and will return file:///mnt/sdcard/AppInventor/assets/ in case the app is running inside the companion app (development mode).
Actually the issue was not there however; I noticed that the WebViewer component was inside a HorizontalArrangement that had configured as fixed length. Changing the length as automatic (and also long enough) and the WebViewer component to fill the parent, now everything works!
Taifun.
