Can't Open Newly Downloaded OpenCPN on MacBook Pro

[crayiii]

Originally Posted by bdbcat

crayii...


I'm no Mac expert, but if it were related to app signing, then would not all users of the same version of MacOS be reporting similar issues?


Dave

I would guess so but I have no idea how many people are installing it on a daily basis. It only recently became an issue.

https://developer.apple.com/document...e_distribution

[CarCode]

Originally Posted by crayiii

I would guess so but I have no idea how many people are installing it on a daily basis. It only recently became an issue.

https://developer.apple.com/document...e_distribution

Please read here about Notarizing:
http://www.cruisersforum.com/forums/...ml#post2968810


So there is no issue actually.

[CarCode]

Originally Posted by bdbcat

crayii...
I'm no Mac expert, but if it were related to app signing, then would not all users of the same version of MacOS be reporting similar issues?
Dave

I don't know who has compiled and bundled the OpenCPN version for macOSX available at opencpn.org


But whoever did it he should respect a little bit the guidelines from Apple.
- dylibs goes normally into a folder called Frameworks and not in the MacOS folder.
- Also not a good idea to put symlinks of dylibs into the bundle.

[pjr587]

Interesting evolution...

So, I wanted to use this as a work app, on the aforementioned MBP, using it on vessels, at my desk, and in classrooms. I bought a new MBP earlier this month. Kind of sitting on it, going to set it up for working at home and editing video. I suppose I'll try loading it on the new machine and see what the results are. I'll admit that some of the stuff that was posted this morning will take me some time to fully understand.

Thank you all for you're attention, interest, and effort on this issue. I have moderated a few discussion boards, and I realize the value of an invested, arrive community. Nice place you have put together here- I can't wait to get into the other forums and explore!

[bcn]

macOS counts with about 10-15% of the installed park of systems where OpenCPN is running.

We see more or less the same percentage at o-charts/oeSENC/oeRNC as the sub-family of OpenCPN.

With Mojave there are issues with oeSENC on a few systems, but by far not on all. Mine is running well for example. Great fun to identify root causes. Over the years macOS has been rock solid in the case of S-63 and oeSENC. Mojave is the first one giving grieve.

That the gatekeeper in case of the OP throws an error does not look like an issue of OpenCPN.

Hubert

[CarCode]

Originally Posted by bcn

That the gatekeeper in case of the OP throws an error does not look like an issue of OpenCPN.
Hubert

Yes and No. OpenCPN for macOS is lacking an installer. So some users tries to fiddle with sudo and Terminal commands, often not knowing what dangerous things they are doing.