Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address bar still showing in my app #4868

Open
Sabbam opened this issue Jan 16, 2025 · 3 comments
Open

Address bar still showing in my app #4868

Sabbam opened this issue Jan 16, 2025 · 3 comments

Comments

@Sabbam
Copy link

Sabbam commented Jan 16, 2025

Dear Team,

I hope this message finds you well. I am currently working on uploading the APK generated from the Progressive Web App (PWA) for Dunnage Mart to the Google Play Store. However, I've encountered an issue where, upon opening the app, it displays the browser UI instead of functioning like a native Android application.
Here are the steps I have followed so far:

Manifest Configuration:

The manifest.json is correctly set with "display": "standalone".
All other properties like background_color, theme_color, and icons have been set appropriately.
Bubblewrap Configuration:

I used Bubblewrap to generate the APK, ensuring the app is configured to use Trusted Web Activities (TWA).
The twa-manifest.json is correctly configured with the host URL, package name, and icon.
Digital Asset Links Setup:

I understand that we need to configure Digital Asset Links by placing the assetlinks.json file on our server at /.well-known/assetlinks.json.
The file includes the app's signature and the corresponding sha256_cert_fingerprints.
Despite following these steps, I am still encountering the issue where the app shows the browser UI. Some have suggested that this could be due to the Digital Asset Links not being set up correctly.

Questions:
Can you please confirm if the assetlinks.json is properly set up for our domain?
Since we are running multiple websites under Odoo.sh, it is crucial that the correct configuration is applied to the relevant website.

Is there anything else I might have missed in the configuration?
I have also made sure the APK runs as a native app by testing it locally before attempting to upload to the Play Store.

Next Steps:
If everything is correct, I plan to test the APK again and ensure it runs properly without the browser UI.
Once the issue is resolved, I will proceed with uploading the APK to the Play Store.
I would appreciate your feedback or any further guidance on this issue.

Thank you for your support!

Best regards,

Sabbam Chandraneel

App Developer

@aalfiann
Copy link

I got same problem, but when I trying to submit into the playstore using .aab and install it via playstore, its standalone. But the apk itself is not standalone.

@pkoepke
Copy link

pkoepke commented Jan 30, 2025

I had this issue today, but managed to resolve it. I forgot to add my app to my <Host URL of your PWA>/.well-known/assetlinks.json file as described here: https://docs.pwabuilder.com/#/builder/android?id=_1-deploy-the-assetlinksjson-file. Once I fixed that I downloaded a new version of my app from pwabuilder. I also uninstalled the app from my device and reset it - I think something about assetlinks.json may have been cached during install.

Anyway, I suggest double-checking your assetlinks file (I had a type in mind), uninstalling your app and rebooting your phone, then uploading a new version of your app to the Play Store. One of those steps fixed it for me, unfortunately I don't know which one it was.

Edit: after reading the documentation I think uninstalling the app, rebooting your phone, then reinstalling should work without having to make a new apk/aab. But I'm not an expert, so take it with a grain of salt.

@aalfiann
Copy link

thanks, it works now.

Just simply upload the assetlinks.json into web hosting.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants