SikuliX should be able to work in a sandboxed environment (partly fixed in 2.0.5)
the most urgent case: Windows - APPDATA folder not accessible - sikulixapi is contained in a fat jar
Available in 2.0.5: As a first solution in Java applications - to be continued I added a feature, that allows to specify a private APPDATA folder, which must be used before accessing any SikuliX feature:
import org.sikuli.script.support.RunTime;
...
... more
...
RunTime.startAPI("someFolder")
where someFolder is a valid path string (must not exist, but must be writable)
If it is not an absolute path spec, the folder is created in the user's home folder.
Hi,
I am currently having this issue as well. I am currently using the TagUI rpa which uses sikulix. I have the same issue as above as the appdata on the env I am using it is on a network drive.
The issue is that Tagui uses the jar file of sikulix. Do you have any suggestions how the above workaround could be applicable on the jar file that tagui uses?
Thanks.
Sorry, but for use with TagUI there is currently no solution, since the APPDATA access is implemented on the Java level.
You have to wait for 2.0.6 (no commitment).
Thank you very much.