According to reports, FileMaker Pro 11 ,12 and 13 did not work with High Sierra. When High Sierra was first rolled out, FileMaker Pro users also reported compatibility issues with the new macOS.

It is the developer’s responsibility to produce updates to make sure that their app works well with the new operating system. It is also unfortunate that macOS is not designed to be compatible with old versions of applications. This problem has been experienced by FileMaker Pro users in previous macOS updates. Nothing NewįileMaker Pro not working in the recent Mac update is not a new issue. While other developers are already Mojave-ready, FMP is still stuck with the old versions even if the beta has been released for months.

Some users have also complained that FileMaker is always so late to the game compared to other developers, considering that FileMaker is a subsidiary of Apple. He said that he always gets ‘a long spinning beachball’ whenever he interacts with the script editor (like clicking or typing a character). He also noticed that the FMP Script editor stopped working every time it was launched. The first issue involved importing from a spreadsheet causing the app to crash, and the second problem happened when he was creating new buttons in layout mode. In a FileMaker community thread, user sccardais mentioned that he was beta testing Mojave 10.14 (18A314k) with FileMaker Pro 17 and noticed two significant issues. During macOS Mojave’s beta testing phase, users already detected some compatibility issues between Mojave beta and FileMaker. Other users also reported having the same issue. V14 seems to crash, V11-13 did crash under macOS 10.13, will probally crash under mojave as well.” “Older versions than 15 do have problems with mojave. About Outbyte, uninstall instructions, EULA, Privacy Policy.

Wait time in filemaker pro server