Installation of latest package does not complete on High Sierra about lipika-ime

[mtikekar]

@shivahnshankar Looking through the install log, I realized that the installer cannot find Swift libraries. You can install them from https://support.apple.com/kb/DL1998?locale=en_GB. It will install them to /usr/lib/swift so you can check if you don't have them.

According to the Apple link, this extra step is only needed on macOS version 10.14.3 and earlier. They come pre-installed on newer versions. @ratreya please consider adding these to the install instructions.

[shivahnshankar]

Version 2.1

[vassadi]

I was trying to install the same on Mac Catalina, it was saying Apple can not check for malicious software.

[meghanae]

Faced the same issue on Sierra. The package installation didn't complete. But the app was installed. Later had to force shut down the system to quit the installation process.

[manoharnikkam]

Faced same issue on Catalina. I get "LipikalME.pkg can't be opened because Apple cannot check it for malicious software."

[yashodhank]

@manoharnikkam if you right click on file and then click open from menu option, it you will be able to run this file without any issue.
This is standard security mechanism with MacOS where downloaded application packages does not run with just one click, unless you override it.

[manoharnikkam]

Thank you very much @yashodhank. It worked. Appreciate it.

[ratreya]

That's good sleuthing. I am inclined to up the minimum requirement to 10.14.4. The installer will refuse to install on an older OS version. Thanks for the investigation!

[mtikekar]

It does work nicely on older versions once you install the Swift libraries. And LipikaAPP works even without the Swift libraries because they are being packaged up into the app. Perhaps there is a way for the installer to link to those instead of /usr/lib/swift.

[ratreya]

I considered the option of hacking the search path to link against the libraries in the App. However, the next version that is currently being worked on in trunk uses SwiftUI which anyway requires 10.15. So, it renders the library issue moot.

[ratreya]

The latest release has a minimum requirement of 10.15 which is required for SwiftUI. Closing this as wontfix.