---
title: "Comment by Muhammad Danial Amsyar Mohd Razali on \"Launch Flatpak Apps With Custom Args and Environment Variables\" | Hashnode"
description: "This is a very helpful guide, thank you for writing it 😁 Regarding the custom desktop entry, Flatpak doesn't always put it under ~/.local/share/flatpak/exports"
url: "https://hashnode.com/posts/launch-flatpak-apps-with-custom-args-and-environment-variables/634a98ef36153a67705247b5/comment/6604b4c764d6bf3bbb084d11"
---

[Discussion](https://hashnode.com/posts/launch-flatpak-apps-with-custom-args-and-environment-variables/634a98ef36153a67705247b5)

Comment [Launch Flatpak Apps With Custom Args and Environment Variables](https://hashnode.com/posts/launch-flatpak-apps-with-custom-args-and-environment-variables/634a98ef36153a67705247b5)

[Muhammad Danial Amsyar Mohd Razali](https://hashnode.com/@amsyarzero)

[Mar 28, 2024](https://hashnode.com/posts/launch-flatpak-apps-with-custom-args-and-environment-variables/634a98ef36153a67705247b5/comment/6604b4c764d6bf3bbb084d11)

This is a very helpful guide, thank you for writing it 😁

Regarding the custom desktop entry, Flatpak doesn't always put it under `~/.local/share/flatpak/exports/...`

For me, it was under `var/lib/flatpak/exports/share/applications` (just like the first proposed solution in the flatpak repo issue).