No Flatpak manifest found in this workspace

[mijorus]

2023-12-29 20:02:10.883 [error] Error: No Flatpak manifest found in this workspace.
	at ManifestManager.<anonymous> (/home/lorenzo/.vscode/extensions/bilelmoussaoui.flatpak-vscode-0.0.36/out/manifestManager.js:214:23)
	at Generator.next (<anonymous>)
	at fulfilled (/home/lorenzo/.vscode/extensions/bilelmoussaoui.flatpak-vscode-0.0.36/out/manifestManager.js:5:58) flatpak-vscode.build-and-run {"value":"bilelmoussaoui.flatpak-vscode","_lower":"bilelmoussaoui.flatpak-vscode"}

From the same folder, GNOME Builder runs just file

[mijorus]

I dug a little deeper on this.
Apparently, the issue seems to be the fact that, for some reason, Code is not activating the extension:

bilelmoussaoui.flatpak-vscode, startup: false, activationEvent: 'workspaceContains:**/*.{json,yaml,yml}'

[SeaDve]

The manifest may also be a good start. Is it possible to show it here, including the file name?

[bilelmoussaoui]

Any updates on this one?

[mijorus]

Any updates on this one?

Not really, it still happens but I don't know why

[bilelmoussaoui]

Yes but we would need a way to reproduce it like sharing the manifest with us or the project itself if it is open source.

[sonnyp]

FYI I am experiencing this on a clone of https://github.com/sonnyp/Workbench
But I can't reproduce with a new fresh clone

[vixalien]

I'm having this issue persistently too. I don't know what exactly I changed. but Flatpak VSCode will now consistently ignore my build manifest until I move it to a separate directory and then move it back while VSCode is running.

This is extremely challenging because it means that Flatpak VSCode will now then recompile everything.

This could potentially be fixed by adding a command to manually re-lookup manifests in the project.

[mijorus]

I realized that simply by renaming the file is enough to trigger a rescan

[vixalien]

Yeah but that triggers a rebuild of all the modules Le lun. 15 juil. 2024 à 10:14, Lorenzo Paderi ***@***.***> a écrit :

…

I realized that simply by renaming the file is enough to trigger a rescan — Reply to this email directly, view it on GitHub <#229 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJB5FCIHTRPPCPDVWR2BLSTZMOAHRAVCNFSM6AAAAABBG5OTQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXHEZTEMBZGA> . You are receiving this because you commented.Message ID: ***@***.***>

[bilelmoussaoui]

I think #239 should fix the issue for you.