unhelpful error message dialog

[john renfrew]

With the latest versions of ScriptMaster the error message 

java.util.concurrent.ExecutionException: java.lang.reflect.InvocationTargetException

is not exactly helpful as it gives no clue as to what the error might be. And I have been getting requests from people about broken code as this gives them no clue as to what is going on.

AND you can't turn it off to be able to just get the choice of being the full stack trace which gives a lot more clues as to the potential source of the error.

How can this be suppressed????

I have amended my v12 file for several years now but the latest version of the plugin shows this system dialog rather than returning "ERROR" as previously which the allowed me the choice of either the last error or stack trace to be outing the result field 

 

[sean360Works]

Hi John,

If you're still running into this issue, please try applying the built-in ScriptMaster functions SMLastError and SMLastStackTrace trace, which can be called right after a plugin error occurs to return more information on the error that occurred. Documentation for these functions can be found at the following link.

http://static.360works.com/plugins/SCRIPTMASTERPLUGIN/documentation.html#SMLastError

You can also take a look at the log files that may have captured this information. Reference the following link to find the location of those log files.

http://docs.360works.com/index.php/Plugin_log_files

If you'd like me to take a look at the logs, you can e-mail them to [email protected]. We'll take a look at the logs and reply back through the same e-mail thread.

 

Sean Kuhn
360Works Support
770.234.9293

[john renfrew]

Hi Sean

I spoke to Jesse about this at Devcon, and he understood the change in behaviour and I *think* the dev version of the plugin I have fixes this...

[TobiasLiebhartKoschierSE]

tbh. this new behavior crashes my FM installation regularly. Whenever ScriptMaster shows some java Error dialogs there is a rising chance they disappear after half a second or so and cannot be brought to the foreground while blocking FileMaker without any timeout. So I have to force quit FM after at most 2 calls to the faulty script. Really freaks me out when trying to develop new function.

[sean360Works]

Hello,

If you are using FileMaker 17, please download the latest developer build of ScriptMaster from the link below.

http://sc.360works.com/SuperContainer/RawData/pro/360/plugins/scriptmaster/latest

I was not able to reproduce the crash behavior you're seeing with this build. After calling SMSetErrorCapture(true), I did not receive anymore error dialogs for the remainder of my session, and I produced an error 10+ times in a row. I tested in FileMaker Pro Advanced 17.0.3.304 on Mac High Sierra 10.13.5, using jre 9.0.1.

If you're still having issues, try reinstalling the jre. Instructions on how to do that are at the following link.

http://docs.360works.com/index.php/Common_issues#Plugins_released_on_or_after_May_2017_fail_to_load

If you still continue to have issues, please produce the behavior, locate the log files before closing/reopening FileMaker(http://docs.360works.com/index.php/Plugin_log_files), and email them to support@360works with details on what you were doing to produce the error.

[TobiasLiebhartKoschierSE]

Wrong thread, please delete

 

Edited April 10, 2019 by TobiasLiebhartKoschierSE