# Native Client Launcher Improvements

**URL:** <https://forum.inductiveautomation.com/t/native-client-launcher-improvements/7811>\
**Category:** Ignition\
**Created:** [January 9, 2014, 10:17pm UTC](https://forum.inductiveautomation.com/t/native-client-launcher-improvements/7811 "2014-01-09T22:17:29Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [January 15, 2014, 7:59pm UTC](https://forum.inductiveautomation.com/t/native-client-launcher-improvements/7811/4 "2014-01-15T19:59:40Z")

</div>

Ok, something just isn’t adding up here.

The client launcher, as Matt mentioned, was designed explicitly to handle this situation gracefully. It _does_ check that the gateway is not just started up, but ready to handle logins.

A few things:

1. Can you “tail” wrapper.log during the startup to make sure that the client launcher isn’t letting the client start until you see:  
[tt]Ignition["/main", state=STARTING] ContextState = RUNNING[/tt]

2. I’m assuming that once the client launches, it takes some time before it fails back to the login screen? Is this assumtion true? If so, can you grab a gateway thread dump during this time?

---

_[View the full topic](https://forum.inductiveautomation.com/t/native-client-launcher-improvements/7811)._