You are reading a single comment by @stweedo and its replies. Click here to read the full conversation.
  • Just a note that I did make some changes to try and allow upload/download, and as part of that I realised I was ripping the webview down when I didn't need to: https://codeberg.org/gfwilliams/Gadgetbr­idge/commit/8e7bfa1e9115c69ee2d9fa0b8685­9f37681db925

    So when that goes in, hopefully you'll be able to move away (for example with the share dialog) and still stay on the App Loader view.

    I just noticed that if I enter an App loader URL in device specific settings in Gadgetbridge, the App loader will be forwarded to be opened with my web browser (Firefox) instead. This happens if I enter either https://espruino.github.io/BangleApps or https://banglejs.com/apps. If I leave it blank it works as expected, opening the Official App Loader in a webview inside Gadgetbridge. I tried this with the beta version on the Google Play Store.

    Edit:
    I got it to work by adding "/android.html" at the end, as hinted in the setting description. I haven't had to do this before though.

  • @Ganblejs I'm also using the beta version of gadgetbridge and I have a custom app loader that opens up normally in the GB app. Do you have chrome installed as well on your phone? I'm thinking it's actually supposed to use chrome within gadgetbridge to display it.

  • I'm thinking it's actually supposed to use chrome within gadgetbridge to display it.

    It uses webview (web engine component of android) inside GB. It's not exactly the same as opening it with an external browser even if it's based on webview (like chrome). Opening in an external browser uses the browser permissions (among other things like history etc.), like for example downloading files to storage.

About

Avatar for stweedo @stweedo started