FileMaker Adv 15.0.2 crashes during development work on Mac OS 10.12

Frequent notices about uncaught inconsistency, option to crash and lose unsaved changes or continue. If opt to Continue get same message next time I try to may a change. SO only real option is Crash. Then get the option to send report to Apple, which I have done.

I have also going to saving changes in layouts and scripts frequently in case this happens.

I went to FMPA 15.0.2 as soon as it was available and then to Mac OS X 10.12 Sierra when it was available.

Started this discussion and also started communication with FileMaker Tech Support.

After trying various things suggested by FM Tech Support, reverted from Mac OS X 10.12 Sierra to Mac OS 10.11 El Capitan by doing a recovery from Time machine backup.

However, after that could not turn on FileVault, with the message that the disk was not formatted correctly. Talked with Apple Tech Support, found the format should be Mac OS Extended (Journaled) but was actually not Journaled, and that it had no recovery partition.

Went to the nearby Apple Store, erased the disk, formatted Mac OS Extended (Journaled) and got a clean install of Mac OS X 10.11 El Capitan. Recovered my files from Time Machine backup and turned on FileVault. All OK

Continued FileMaker development work in that OS environment, no more occurrences of the Uncaught Exception errors that I was getting before.

After a while, tested doing FileMaker development on my wife's computer which is a new MacBook Pro with clean install of Mac OS X 10.12 Sierra, did not encounter any problems.

About a week ago, decided to take the chance of upgrading my MacBook Pro to OS X 10.12 Sierra. That worked. I have been doing FileMaker development on my computer ever since, using FileMaker Pro Advanced 15.0.2.202, with no difficulties.

So maybe the earlier problem with the Uncaught Exception errors was due to a not-quite-right format of the hard drive and consequent not-quite-right configuration of Mac OS X 10.12 Sierra.

Anyhow, since I did the erase, reformat, clean install of Mac OS 10.11 El Capitan, then upgrade to Mac OS 10.12 Sierra, everything seems to be working fine.

I should also mention that I have had extensive email correspondence on this matter with FileMaker Tech Support, and have kept them informed of developments up to the present.

Yes, I would "upgrade" back to the previous version of FM and see if that works.

Difficult to be productive with unpredictable results. Seems like there is only one FM developer (at FMI) nowadays. Still no excuse for sloppy, untested, or (apparently) barely tested code like you're describing.

It's sad when companies dump software in your lap that's really not tested that well or ready for prime time. I'm not actually sure what the actual issue(s) is/are with 15, of course, and I don't plan to upgrade for barely incremental features added, anyway.

Got another crash of FileMaker Pro 15 today while I was editing a script. NOT while the script was running but while I was editing the script. All the crashes have occurred while I was editing a script, NOT during database operation.

I had shut down my computer in the morning, then started it up later. After I started up I was doing some script modifications and the crash occurred.

As Christian suggested, since nobody as I've seen from "TS" has commented here, you should file a bug report with FileMaker. It would be interesting/helpful to hear from other Mac folks with your same basic configuration to see if they're having issues as well.

One thing I would try is to load FM 15 on another (possibly virgin mac "VM" or similar) with the same solution. Does it crash there too? 15 is the latest version so it must run.

You can also call FM's 800 number if you're not getting any help with the bug report route....at least to get someone's attention. If you're like me, you don't have FM just for the heck of it, right? IOW, you want/need it to, well, work.

On advice of FileMaker Test Support, removed and did a fresh install of Filemaker Pro 15 Advanced, version 15.0.2.202.

Had earlier run the updater to go from FileMaker 15.0.1 to 15.0.2.202. Tech Support thought maybe there is some possibility the update might not have exactly done the job, and maybe a fresh installation of Filemaker Pro 15.0.2.202 would alleviate the problem. I will see what happens.

After extended communication with FM Tech Support, reverted my Mac to OS X 10.11.6 El Capitan. The problem with getting "Uncaught Exception" errors when editing scripts has not occurred since I did that. I plan to remain with Mac OS X 10.11.6 El Capitan until I have some reliable assurance from FileMaker that the issue is resolved.

In fairness to FMI, I wonder if the problem was unique to my system running Mac OS X 10.12 Sierra. The reason I pose this is because when I reverted to OS X 10.11, I discovered my hard drive had no recovery partition, which it should have. I ended up going to the nearby Apple store, to a Genius Bar appointment, and getting my hard drive erased and reformatted to Mac OS Extended Journaled, and then getting a clean install of OS X 10.11.6, then restoring all my files from my Time Machine backup. So I wonder if there was some oddity in my system under Mac OS X 10.12 than led to the Uncaught Exception errors.

It's NOT up to you to do back-flips and other gymnastics so the program is happy.

If there really are those restrictions, they should be listed in the installation instructions or stated by the TS folks here.

---

I'm now on Sierra and, fortunately, haven't seen any issues at all with FMPA 14. Assuming FMP 16 is not a FORCED SUBSCRIPTION (IOW, if you can still buy a regular license) and assuming there are actually new useful (v 1.0 or later type) features like Script search/replace, I'll dive in and get it.

Started this discussion and also started communication with FileMaker Tech Support.

After trying various things suggested by FM Tech Support, reverted from Mac OS X 10.12 Sierra to Mac OS 10.11 El Capitan by doing a recovery from Time machine backup.

However, after that could not turn on FileVault, with the message that the disk was not formatted correctly. Talked with Apple Tech Support, found the format should be Mac OS Extended (Journaled) but was actually not Journaled, and that it had no recovery partition.

Went to the nearby Apple Store, erased the disk, formatted Mac OS Extended (Journaled) and got a clean install of Mac OS X 10.11 El Capitan. Recovered my files from Time Machine backup and turned on FileVault. All OK

Continued FileMaker development work in that OS environment, no more occurrences of the Uncaught Exception errors that I was getting before.

After a while, tested doing FileMaker development on my wife's computer which is a new MacBook Pro with clean install of Mac OS X 10.12 Sierra, did not encounter any problems.

About a week ago, decided to take the chance of upgrading my MacBook Pro to OS X 10.12 Sierra. That worked. I have been doing FileMaker development on my computer ever since, using FileMaker Pro Advanced 15.0.2.202, with no difficulties.

So maybe the earlier problem with the Uncaught Exception errors was due to a not-quite-right format of the hard drive and consequent not-quite-right configuration of Mac OS X 10.12 Sierra.

Anyhow, since I did the erase, reformat, clean install of Mac OS 10.11 El Capitan, then upgrade to Mac OS 10.12 Sierra, everything seems to be working fine.

I should also mention that I have had extensive email correspondence on this matter with FileMaker Tech Support, and have kept them informed of developments up to the present.