While editing a script in FMP Advanced, FMP crashed.
Have seen this three times.
Known issue has to do with scrolling in Script Editor. In other words, almost always.
Need a fix ASAP.
Had been having issues with WEBD
I updated OS X on the computer to 10.12
I uninstalled sever s/w
installed server 15.02 from scratch (not using the updater)
WEBD worked; but, I started getting the CRASHES while in the script editor.
This morning, WEBD issues returned. So now, no WEBD or SCRIPT EDITING.
I don't know of any known issue as you describe. There was an 'Script Editor' issue in FM14 where script steps moved.
Crashes can be a sign of a corrupt file. Have you tested backup copies of your database, to verify it still crashes?
Your file could had corruption in it for a while so it is wise to test a older backup copy. Have you tested with other new databases? The database you are having problems with, was it create in FMP15 or was created in a previous version of FMP?
I would make backup of the database and run recover on the backup copy to verify file. Note, even if recover does not detect file corruption, it does not mean that there is not any corruption in the file.
Issues should be posted Report a Product Issue
Restarted computer and WEBD loaded; but, showed the "UGLY" that was associated with 15.1, and should not be associated with 15.2 (which has the known script-editing-crashing issue).
Thank you for your posts.
There is a known issue in the Scripts Workspace under macOS Sierra 10.12. Usually, for some script steps (e.g., Set Variable, If, Print] that displays a gear icon to the right of the script step. However, when you scroll, those gear icons may disappear from view. If you then click the area where the gear icon is supposed to appear, you will get a crash. Sometimes, if you wait a few seconds, the gear icons will re-appear.
Is this what you are encountering?
I don't recall those details. But I will watch for them.
In general, I'd be working on a script; and, the surprise dialog box would appear.
When it does, I press CONTINUE and exit the script workspace. Often I close the client s/w too, and then restart it.
Let's hope there is a fix soon.
Retrieving data ...