"SageMath is damaged and can't be opened" on macOS 10.14

[Szabolcs Horvát]

I just installed the app version of SageMath 9.0 on macOS 10.14. When I try to launch it, I get "SageMath is damaged and can't be opened." Version 8.9 worked fine on the same macOS version.

Do others have this problem too? It would be surprising to me if this were a universal problem, as it would have certainly been noticed before publishing the distribution ...

Is there a workaround?

Is SageMath struggling with getting enough developer resources? Recently one has to go through more and more hoops to be able to use it ... it's no longer possible to just download a binary and start it like any normal app. The last few versions already took minutes to start on macOS unless they were launched manually from the command line. 

[Dima Pasechnik]

On Fri, Jan 10, 2020 at 8:01 AM Szabolcs Horvát <szho...@gmail.com> wrote:
>
> I just installed the app version of SageMath 9.0 on macOS 10.14. When I try to launch it, I get "SageMath is damaged and can't be opened." Version 8.9 worked fine on the same macOS version.
>
> Do others have this problem too? It would be surprising to me if this were a universal problem, as it would have certainly been noticed before publishing the distribution ...
>
> Is there a workaround?

don't use the app version. Use a "normal" terminal version.

>
>
>
> Is SageMath struggling with getting enough developer resources? Recently one has to go through more and more hoops to be able to use it ... it's no longer possible to just download a binary and start it like any normal app. The last few versions already took minutes to start on macOS unless they were launched manually from the command line.

Apple keeps introducing new security features that are supposed to
make MacOS "safer" :-)

We don't have any active developers who are experts in MacOS specifics.
And no paid engineers to look into this sort of unpleasant stuff,
since the end of OpenDreamKit grant few months ago.

I think the app version must be pulled, I have been saying this for some time.

[kcrisman]

Which app version was used?   I just tested the one I built on my own computer and I was able to get it going.  However, that is OS X 10.11 - I don't have access to the newer versions.

There is a thread where Ivan suggested some possibilities, at least one of which (the one where the user specifies a binary) would use an existing technology in the app.   I'm surprised that the 8.8 app did work on the same computer - can you try the 10.11 version of the app rather than the 10.15 one?

Finally, note that you can use any binary you want with the app; you seem pretty knowledgeable, so probably you could only upgrade the binary itself (also available for download) without any loss (for now, Dima is right about not having someone with the right skill set currently active).  Please report back if you do try one of these, we might get lucky and have an easier fix.

[kcrisman]

See https://groups.google.com/forum/#!topic/sage-devel/nlXP6cv4LAY

[Justin C. Walker]

> On Jan 10, 2020, at 09:18 , kcrisman <kcri...@gmail.com> wrote:
>
>
>
> On Friday, January 10, 2020 at 3:18:17 AM UTC-5, Dima Pasechnik wrote:
> On Fri, Jan 10, 2020 at 8:01 AM Szabolcs Horvát <szho...@gmail.com> wrote:
> >
> > I just installed the app version of SageMath 9.0 on macOS 10.14. When I try to launch it, I get "SageMath is damaged and can't be opened." Version 8.9 worked fine on the same macOS version.
> >
> > Do others have this problem too? It would be surprising to me if this were a universal problem, as it would have certainly been noticed before publishing the distribution ...
> >
> > Is there a workaround?
>
> don't use the app version. Use a "normal" terminal version.
> >
> >
> >
> > Is SageMath struggling with getting enough developer resources? Recently one has to go through more and more hoops to be able to use it ... it's no longer possible to just download a binary and start it like any normal app. The last few versions already took minutes to start on macOS unless they were launched manually from the command line.
>
> Apple keeps introducing new security features that are supposed to
> make MacOS "safer" :-)
>
> We don't have any active developers who are experts in MacOS specifics.
> And no paid engineers to look into this sort of unpleasant stuff,
> since the end of OpenDreamKit grant few months ago.
>
> I think the app version must be pulled, I have been saying this for some time.
>
> Which app version was used? I just tested the one I built on my own computer and I was able to get it going. However, that is OS X 10.11 - I don't have access to the newer versions.

FWIW, I am running the Sage 9.0 app on macOS 10.13.6 (it appears to have been built for 10.11, according to the name).

I will be trying later versions of the app on 10.13.6, 10.14.6 and (I think) 10.15.x later today or this weekend.

Justin

--
Justin C. Walker
Director, Institute for the Absorption of Federal Funds
--
Taxes, n.:
Of life's two certainties, the only one
for which you can get an extension.
--

[kcrisman]

FWIW, I am running the Sage 9.0 app on macOS 10.13.6 (it appears to have been built for 10.11, according to the name).

 

That is the one I built.  Glad it works there.

I will be trying later versions of the app on 10.13.6, 10.14.6 and (I think) 10.15.x later today or this weekend.

 

Yeah, I think that the 10.14 and 10.15 issue is more serious and harder to avoid.  I don't think that just using System Preferences or right-clicking can overcome it (aside from the very long wait issue).