Fv2 Launcher

[Albina Hickel]

Weare on V8.1.0 and are experiencing the same thing. Project title does not have any special characters (though parent project does). Nothing described here has worked. Work around is to add any other application then change its configuration properties to match the project that you are unable to add via the usual method.

Just an addition incase the previous solutions did not help, I faced the problem of not seeing the project on the client launcher and later figured out its because I had a blank project with no windows in it. Just adding even a test window will make the project appear on the client launcher. Hope that helps!

Best Practice

It's good practice to download and install the Designer Launcher every time you install a new release of Ignition. The Designer Launcher is a separate application and is not part of an Ignition release, so it's important not to have an outdated Designer Launcher shortcut residing on your desktop

Until the point when someone finds an exploit and you didn't apply the patch since it's just a launcher. There's certainly less risk of an exploit with a smaller codebase but running out-of-date software is generally bad practice and I think particularly egregious in this case since updating the designer launcher is minimal risk to your production environment

Whenever an Application is launched from a Launcher, the Launcher will check to see if it needs an update. If the Gateway containing launched application is several revisions ahead of the Launcher, the Launcher will provide a popup notifying you that an update is available.

However manual upgrades can be performed. Simply download and run a new launcher installer from a more recent Ignition Gateway. During installation, simply set the installation directory to the same directory as the old launcher.

As of 8.0.13's bundled client/designer launcher, you'll get a prompt if you connect to a gateway that's got a significantly different version of the launcher available. Not quite auto-updates, but pretty good.

...

That aside, they only get better, so there's certainly no harm in updating

I think ultimately the issue is that of communication. Once a project gets above a certain size you will have different people controlling the gateway software installations vs those who are building the application. So there is always the chance (ok 100% certainty) that one group doesn't talk to the other about what version of software is in use. Thus is makes sense to automatically minimize the friction by getting the computers to do what they do best - talk to each other.

My test gateway is running on Ubuntu (just to see how Ignition handles linux) and this morning Ubuntu told me that there were new updates available. After doing said updates (1) I could no longer open the Inductive website in Firefox (2) Thus Ubuntu stopped me from downloading some software called Ignition HMI, that's apparently full of exploitable holes

This is on 20.04.1 LTS updated as of today. Firefox 84.0.2 (64 bit). Running in a VM under Windows 10

I just loaded youtube.com and www.wikipedia.org from firefox within this system, but I can't get to support.mozilla.com

But I've also had the firefox crash reporter pop up a few times today.

nslookup works for inductiveautomation.com and returns 52.52.32.221

But I can't ping it. Firefox fails to load, but it will redirect from the to the url of the site before dying.

But I can get to the correct inductive site via 2 other systems (windows and mac) so I know it's just the Ubuntu system. My guess is something was screwed up with the update, but as this is a test system I don't really care too much about that aspect.

Same problem here, I even have the same certificate on the Ignition gateway and the ssl termination point in front of it (a web application firewall). Designer launcher works directly to the gateway, but not through the WAF (SSL Certificate not found). The certificate is trusted: LetsEncrypt.

All, not sure if it has been addressed elsewhere in the forums, but Designer Launcher using Self Signed certificates on a Gateway with redundancy needs to have the Subject Alternates included in the Master and Backup gateways. It will ask to trust both certificates. There should be a note in the section stating this is required for Gateways using redundancy.

I just realized I misread the launcher code. It creates a command that adds a launcher to the main area. The file browser extension invokes that command if there is no other widget open. So if you add your widget to the main area in your activate function, the file browser will notice there is something already there and will not create a launcher tab by default.

@jasongrout I am working with aafshar. I tried adding my extension to the MainAreaWidget inside the extension activate function but this resulted in some strange behaviour. More often than not, on page refresh, the launcher is rendered on the MainAreaWidget. However, every once in a while on page refresh, my extension is rendered onto the MainAreaWidget as intended.

Is this the proper implementation of your description above?

Unfortunately, this url did not open the desired testingworkspace workspace but opened just a launcher (I assume it just opened a default workspace). Is this the correct workflow to save and open a custom workspace?

I have an ELVIS II MX board for ECPI university. About 4 weeks ago it stopped allowing me to launch the instrument launcher. I attempt to bring it up by clicking it and nothing happens. There is no error message or screen flash. It does not appear in the task manager at all. I had previously been using it since June of 2017. I have uninstalled and reinstalled the NI student edition and myDAQ software suite. This has not corrected the issue. There are no real specific instructions on my school site as to what to install other than "This download enables students to install the same NI software used in campus laboratories, on their own laptops and computers. By using the serial number below, students will be able to access Student Install Options for both Multisim and LabVIEW. " I am unsure how to resolve this issue.

Since the patch yesterday the game launcher won't open for me. It briefly flickers ("initializing") then disappears. I've tried repairing it, reinstalling the game and restating my computer but nothing fixed it. Does anyone else have this problem or know a way to fix it?

i think the launcher is probably already running but stuck, so you need to kill off the "Gw2-64.exe" process in task manager. its also possible the launcher is failing to patch itself due to permission issues, so make sure it can write to its directory (don't put it in program files, but on your desktop or user folder is fine).

For me the launcher window only appears after I kill the task in task manager. So I click gw2, nothing happens except my cursor telling me something is loading. No launcher appears. Go to task manager, end gw2 process (its a high power process). As soon as I do that the launcher appears like normal.

If I don't do the task manager process I can click on the gw2 icon and a process will appear for each time I click but no launcher window will open.

I still have that problem. Guild Wars 2 processes don't seem to close correctly when ending the application. You can do a workaround by killing all GW2 process manually, but I really hope this will get fixed sooner or later.

if we talk about the epic launcher, there is no other app in this world that behaves worse than this. switching between tabs and menus takes ages. is incredible how bad it is and still no changes years later.

This issue is still present. When some of our staff try's launching a MS office file from drive it will only give the option to open with Google Sheets or Docs. I have to tell them to back out of the open with screen that come up with a preview and try again. This works 50% of the time. This just isn't expectable.

I will state, that this seems to be only happening on Windows 10 machines, since the December update to Chrome I haven't had any issues with my Windows 11 machine. I will have to ask around and see if this is 100% the case with Windows 10 only.

Unfortunately, this issue is also still present on Windows 11. We've checked all the updates for Windows and chrome, deleted caches etc. However we have at least one member of staff who can still open with MS and Adobe apps- but we can't find any difference in settings or OS and browser versions.

February '24. This is still not working for anyone in my team.

I've updated Chrome to the latest version available to me: 122.0.6261.58 (Official Build) (64-bit). I've uninstalled and reinstalled the extension (From the old Chrome Web store). The new Chrome Web store does not list the application launcher - could this be anything to do with the issue?

This is really frustrating for teams managing files in a Google Workspace environment through Chrome who also have to open certain files in native software, such as complex excel workbooks or InDesign files. Any ideas of what to try next?

Dear colleagues, we are facing this issue now and the funny things that it works for some people and it doesn't for others. I tried to update, reinstall etc.. but still it did not work. I know the process is tedious re this darned app launcher.

3a8082e126