# Vision Client Launcher same application name different Gateways not allowed

**URL:** <https://forum.inductiveautomation.com/t/vision-client-launcher-same-application-name-different-gateways-not-allowed/38374>\
**Category:** Ignition\
**Tags:** ignition80, vision\
**Created:** [September 3, 2020, 9:10pm UTC](https://forum.inductiveautomation.com/t/vision-client-launcher-same-application-name-different-gateways-not-allowed/38374 "2020-09-03T21:10:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![cesrom](https://avatars.discourse-cdn.com/v4/letter/c/ea666f/32.png) [@cesrom](https://forum.inductiveautomation.com/u/cesrom)\
**Post date:** [September 3, 2020, 9:10pm UTC](https://forum.inductiveautomation.com/t/vision-client-launcher-same-application-name-different-gateways-not-allowed/38374/1 "2020-09-03T21:10:01Z")

</div>

Ignition Vision Client Launcher versions: 1.0.0 - 1.0.16

I have added multiple Gateways, and in some Gateways, I have used the same Application name, but form some reason Ignition Vision Client Launcher does not allow the same name so it automatically appends a `(1)`.

Sure, it makes sense on a single Gateway, where the Project Name must be unique, but it does not make sense on different Gateways.

A minor annoyance, but I was wondering if this is something that someone else has brought up in the past and if there is a possible solution for this in upcoming releases.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [September 24, 2020, 9:14pm UTC](https://forum.inductiveautomation.com/t/vision-client-launcher-same-application-name-different-gateways-not-allowed/38374/2 "2020-09-24T21:14:10Z")

</div>

@jcoffman

---

<div class="post-metadata">

**Author:** ![jcoffman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jcoffman/32/6429_2.png) [@jcoffman](https://forum.inductiveautomation.com/u/jcoffman)\
**Post date:** [September 30, 2020, 3:46pm UTC](https://forum.inductiveautomation.com/t/vision-client-launcher-same-application-name-different-gateways-not-allowed/38374/3 "2020-09-30T15:46:25Z")

</div>

Hi @cesrom,  
The reason for this is that application names must be unique to allow launching from shortcuts that are created. Some systems in the past had issues with shortcuts which had commands that were too long on certain operating systems which prevented launching or resulted in the command being truncated and some of the args would drop off.

Hope that helps!  
Jonathan C

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 30, 2020, 5:29pm UTC](https://forum.inductiveautomation.com/t/vision-client-launcher-same-application-name-different-gateways-not-allowed/38374/4 "2020-09-30T17:29:26Z")

</div>

This is a terrible excuse, as a solution combing gateway address and project name in a shortcut would certainly satisfy the length issue.

Not allowing same names on different gateways is going to cause problems with dev/staging/production setups.