# Vision Client Launcher Deployment Issues

**URL:** <https://forum.inductiveautomation.com/t/vision-client-launcher-deployment-issues/32641>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [February 26, 2020, 8:05pm UTC](https://forum.inductiveautomation.com/t/vision-client-launcher-deployment-issues/32641 "2020-02-26T20:05:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![osolorzano](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/osolorzano/32/6432_2.png) [@osolorzano](https://forum.inductiveautomation.com/u/osolorzano)\
**Post date:** [February 26, 2020, 9:36pm UTC](https://forum.inductiveautomation.com/t/vision-client-launcher-deployment-issues/32641/2 "2020-02-26T21:36:23Z")

</div>

This sounds a lot like the issue described here. Pre-deploy launchers right now do not function as expected yet. It's currently being worked on though.

> [@\[Feature-15996\] Ignition Launchers use ~/.ignition instead of AppData](http://forum.inductiveautomation.com/t/feature-15996-ignition-launchers-use-ignition-instead-of-appdata/32139/7):
>
> Getting closer. Now with the clientlauncher-data folder in the right spot with the json file, the launch opens up with the list of apps without having to have the json config file in the users .ignition folder. Now I am running into an error when I try to launch a project. [image] Shouldn’t it be looking in the same place as the json config file is and not my users folder?

---

_[View the full topic](https://forum.inductiveautomation.com/t/vision-client-launcher-deployment-issues/32641)._
