packaged webapp won't show main page on both beta and fennec nightly
i'm trying to install a webapp from http://www.unixmedia.it/webapp/ following the docs.
The webapp consist in just an "hello world" where i have a single page app and lauch_path to /index.html
trying to download the app by wget https://controller.apk.firefox.com/application.apk?manifestUrl=https%3A%2F%2Fwww.unixmedia.net%2Fwebapp%2Fpackage.manifest -O myapp.apk seems to work, unzipping the apk i can see the right files included in /res/raw/application.zip, and the app is correctly installed in android.
When i launch the app, both with fennec and firefox beta, the app starts up, i can see the splashscreen with the logo image, and then a white screen appears and nothing more.
I don't see any relevant error using adb logcat
Chosen solution
solved, is there an issue and a workaround:
https://bugzilla.mozilla.org/show_bug.cgi?id=993199
Read this answer in context 👍 0All Replies (6)
Hi,
I understand that you are installing a web app with the synthetic apk and all that is showing up is the icon and not the hello world message.
The packaged app is wrapped in a Android java pack, my question is how is the hello world implemented?
Irrelevant future references
- Bug 986085 - User-hand-holding to check the Unknown Sources checkbox.
- Run as a native Android App
- Have you submitted it to the marketplace? https://developer.mozilla.org/en-US/M.../Open_web_apps_for_android
If you need more help please see the irc marketplace channel or email the marketplace mailing list for more specific help. https://lists.mozilla.org/listinfo/dev-marketplace
The hello world is implemented just as linked source, following the docs about packaged apps.
And no, i don't intend to submit my app to the marketplace, i intend to distribute the app on my own web site
The source for the app ( it was linked in another thread ) is:
http://www.unixmedia.net/webapp/package.zip
This is the mini-manifest: http://www.unixmedia.net/webapp/package.manifest
Chosen Solution
solved, is there an issue and a workaround:
locking this question as nextime said it was solved