Gabriele Modena

> I need to look into supporting generic URI, but that sounds like a nice feature to have. Supporting installation from a flatpakref URL is pretty straightforward. What complicates things...

> The only workaround I can think of is downloading the .flatpakref file and mapping the URL to the declared Name and RuntimeRepo. I did some further testing. This might...

Hey @Bear-03 > As I understand it, it's missing the GPG key tht is included in the .flatpakref. That's why my next approach was to just keep the file and...

> Isn't that already possible though? you can provide a local path with `file://` like I did in my config. Although now that I think of it, the protocol could...

@Bear-03 @SpiderUnderUrBed I still need to add some unit tests before resolving, but if you want to give it a go #80 should be in a decent enough shape. You...

@SpiderUnderUrBed thanks for giving it a go! Could you paste me the content of `$HOME/.local/state/home-manager/gcroots/flatpak-state.json` (if you load nix-flatpak as an HM module) or `/nix/var/nix/gcroots/flatpak-state.json` (if you load nix-flatpak as...

@SpiderUnderUrBed thanks for sharing. `flatpak-state.json` look ok to me. Unfortunately I have not been able to repro your error: ``` Oct 11 00:48:48 daspidercave sabklji2jdalpb044z360f89k2cdlrmm-flatpak-managed-install[48600]: The following refs are installed...

> This error should be replicated if you install a remote, like "sober" which is a remote automatically made when you install from a flatpak ref. I did try to...

Thanks for confirming. > Then you can address this bug with your suggested failsafe. I'll open a dedicate PR for this.

Hey @Bear-03, This sounds related to https://github.com/gmodena/nix-flatpak/issues/90. > The issue is fixed if i run flatpak uninstall --all, but it fails again the next time I try to rebuild. Ack....