Win32 il2cpp Process.Start not work

Unity2018.1.6f1
Win32 IL2Cpp Process.Start(run_path, url); not work.
Mone is fine.
output_log print this :
System.ComponentModel.Win32Exception: Success
System.Diagnostics.Process.Start_shell

 

(Case 1058636) Win32 il2cpp Process.Start not work.
https://fogbugz.unity3d.com/default.asp?1058636_k20hpprrme8tthcm

 

Has this ever been fixed? I am on 2019.3 right now and get the same error. This is really bad for any automation out of a Unity app and currently a blocker for me. Are there any workarounds known?

 

Thanks for the quick reply. I have switched to Mono for my Desktop builds and that works indeed nicely but it's a pity that this is yet another property my custom build chain will have to consider between platform builds. Would be really great to have this aligned

 

@JoshPeterson so starting a process from within an IL2CPP build is not possible, and thats a feature?

 

Ok; thanks for the quick response.

Luckily we could get around it, in case anyone wants to start a steam process you can also call OpenUrl with a `rungameid` url.

 

Is it planned to be possible in the foreseeable future?

 

That was a huge surprise for me when I've got the Win32Exception: Success in unity 2019 LTS while trying to start a process from the IL2CPP build xD

Hope it will be implemented in the future.

 

What's so challenging about implementing this feature? can't we at least execute a shell command and get the stdout?

I have to run "/bin/bash -c 'df -BM --output=avail "." | tail -n 1'" so I can get the correct free disk space, as no other tools are available for linux. But not being able to start a process seems a bit shocking

 

I see, so it's an all or nothing thing. Makes sense, but I think we'd be happy with just a few features implemented, and some throwing NotImplementedException (instead of cryptic native errors).
There are 2 guys on asset store each selling a partial implementation of this as an asset. I think it's in everyone's interest to approach them and take over their work, for fair price.
The one I chose doesn't seem to support the Process.StandardOutpout.ReadToEnd(). Might be something you could start with.

 

This information should be added to "Scripting Restrictions" in the docs.

 

Thanks for adding it to the 2023 docs Josh. On behalf of dozens of devs who'll run into this downstream from today, any chance it gets added to previous supported versions ?

It sucks to be looking for documentation for the version of Unity you use and have restrictions more up to date on the latest version but not the version we're on, and to have to crawl through forums and google search to look for it. I understand if updating legacy version docs is frowned upon - but supported versions should be up for grabs.

 

by any chance, was there any advancement in exposing this function in il2cpp?