Re: Is the list alive?

[Carl Hoefs via Cocoa-dev]

> On May 29, 2019, at 6:02 AM, Steve Mills via Cocoa-dev 
>  wrote:
> 
> On May 28, 2019, at 19:46:26, Leo via Cocoa-dev  
> wrote:
>> 
>> 
>> Hmm... my earlier message today never got through.
> 
> Supposedly, these lists are to be done away with at some point. Someone 
> started co...@apple-dev.groups.io, which many of us have moved to. Or use the 
> annoying and inferior dev forums.developer.apple.com.

Note sure if all the bugs are worked out yet... I signed up with 
apple-dev.groups.io  but my emails keep bouncing. 
I go to the web page and have to click a "stop bouncing my emails" button. Then 
it goes back to bouncing again...

-Carl

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Is the list alive?

[Leo via Cocoa-dev]

On 5/29/19 9:02 AM, Steve Mills via Cocoa-dev wrote:

On May 28, 2019, at 19:46:26, Leo via Cocoa-dev  
wrote:


Hmm... my earlier message today never got through.

Supposedly, these lists are to be done away with at some point. Someone started 
co...@apple-dev.groups.io, which many of us have moved to. Or use the annoying 
and inferior dev forums.developer.apple.com.

--
Steve Mills
Drummer, Mac geek


Thanks for the info.

Now I see that my emails do get through - however, it takes HOURS for 
them to show up (like 5+ hours).


I wonder if it's normal - or should I adjust something on my end?


Leo
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Is the list alive?

[Jens Alfke via Cocoa-dev]

> On May 29, 2019, at 7:22 AM, Richard Charles via Cocoa-dev 
>  wrote:
> 
> Internally at Apple I would bet that most developers get their questions 
> answered by asking another developer.

Back when I worked at Apple (1998-2007) there were internal mailing lists much 
like these — I learned a lot and shared a lot on macosx-dev-internal. But yes, 
I think lists.apple.com  is only still alive because 
nobody at Apple can locate the Power Mac G4 that runs it, to shut it down. ;-)

> I need to take a look at co...@apple-dev.groups.io 
> . It looks interesting.

I started that list, and several others. You can see all the lists at 
https://apple-dev.groups.io/g/main  . The 
xcode list there is pretty lively too.

It’s easy to create more, if someone has another topic they think deserves a 
list of its own.

—Jens
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Is the list alive? (Leo)

[Casey McDermott via Cocoa-dev]

Thanks for the mention of  co...@apple-dev.groups.io
It looks promising, but this list is still uniquely useful.

Apple's documentation is mediocre.  Header files sometimes help,
but source code is not visible so it requires much guesswork.  
There are many "gotchas" lurking.

Stack Overflow has hits for any problem, but many answers are
old (and wrong).  It's even worse for Obj-C, since new answers are 
mostly Swift.  Not much sweet spot in between.

When other options fail, sometimes folks on this list have already been
there, and provide invaluable help.  Thanks to all of them!

Casey McDermott
Turtle Creek Software
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Notarization error: The signature algorithm used is too weak

[Richard Charles via Cocoa-dev]

> On May 28, 2019, at 8:18 PM, Leo via Cocoa-dev  
> wrote:
> 
> Can you please elaborate on this...

Perhaps this will help.

https://stackoverflow.com/questions/25152451/are-mac-app-store-code-sign-resource-envelopes-always-version-1

--Richard Charles

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Is the list alive?

[Richard Charles via Cocoa-dev]

> On May 29, 2019, at 7:02 AM, Steve Mills via Cocoa-dev 
>  wrote:
> 
> Supposedly, these lists are to be done away with at some point. Someone 
> started co...@apple-dev.groups.io, which many of us have moved to. Or use the 
> annoying and inferior dev forums.developer.apple.com.

It is a mystery why this list is still alive.

Internally at Apple I would bet that most developers get their questions 
answered by asking another developer. The current documentation is very 
artistic but not very functional or useful for serious development.

A lot of questions can be answered by looking in stackoverflow, perusing older 
documentation or searching the web.

You can always submit a technical support incident but you will most likely be 
asked to submit a focused sample project demonstrating the issue.

I need to take a look at co...@apple-dev.groups.io. It looks interesting.

--Richard Charles

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: code signing fails to verify on 10.10?

[David M. Cotter via Cocoa-dev]

well,  the solution was to just re-build the offending library with 10.9 as  
the target and all is well 

> On May 20, 2019, at 9:38 AM, David M. Cotter  wrote:
> 
> i saw this article:
> https://stackoverflow.com/questions/41865537/how-does-apples-codesign-utility-decide-which-sha-algorithms-to-sign-a-shared
>  
> 
> 
> which seemed to be related, but the odd thing is that the app launches FINE 
> on 10.9, or 10.11 and later.
> 
> why fail only on 10.10?
> 
> 
>> On May 19, 2019, at 8:38 PM, David M. Cotter  wrote:
>> 
>> I’m developing on 10.14.4
>> using Xcode 9.4.1
>> signing via command line (not via xcode)
>> 
>> my app works fine on 10.12 and above
>> but on 10.10.5, i get this:
>> 
>>> Application Specific Information:
>>> dyld: launch, loading dependent libraries
>>> Dyld Error Message:
>>> Library not loaded: @loader_path/../Frameworks/libboost_thread.dylib
>>> Referenced from: /Users/USER/Desktop/kJams 2.app/Contents/MacOS/kJams 2
>>> Reason: no suitable image found.  Did find:
>>> /Users/davec/Desktop/kJams 
>>> 2.app/Contents/MacOS/../Frameworks/libboost_thread.dylib: code signature 
>>> invalid for '/Users/davec/Desktop/kJams 
>>> 2.app/Contents/MacOS/../Frameworks/libboost_thread.dylib'
>> 
>> on the command line of 10.10.5, however, it seems to pass the tests:
>> davec$ codesign - --deep /Users/davec/Desktop/kJams\ 2.app 
>>> --prepared:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/Growl-123.framework/Versions/Current/.
>>> --validated:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/Growl-123.framework/Versions/Current/.
>>> --prepared:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/Growl.framework/Versions/Current/.
>>> --validated:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/Growl.framework/Versions/Current/.
>>> --prepared:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/libboost_atomic.dylib
>>> --validated:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/libboost_atomic.dylib
>>> --prepared:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/LAME.framework/Versions/Current/.
>>> --validated:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/LAME.framework/Versions/Current/.
>>> --prepared:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/libboost_system.dylib
>>> --validated:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/libboost_system.dylib
>>> --prepared:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/libboost_thread.dylib
>>> --validated:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/libboost_thread.dylib
>>> --prepared:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/libgnsdk_manager.3.2.0.dylib
>>> --validated:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/libgnsdk_manager.3.2.0.dylib
>>> --prepared:/Users/davec/Desktop/kJams 2.app/Contents/MacOS/HelperTool
>>> --validated:/Users/davec/Desktop/kJams 2.app/Contents/MacOS/HelperTool
>>> --prepared:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/libgnsdk_musicid.3.2.0.dylib
>>> --validated:/Users/davec/Desktop/kJams 
>>> 2.app/Contents/Frameworks/libgnsdk_musicid.3.2.0.dylib
>>> --prepared:/Users/davec/Desktop/kJams 2.app/Contents/MacOS/InstallTool
>>> --validated:/Users/davec/Desktop/kJams 2.app/Contents/MacOS/InstallTool
>>> /Users/davec/Desktop/kJams 2.app: valid on disk
>>> /Users/davec/Desktop/kJams 2.app: satisfies its Designated Requirement
>> 
>> and:
>>> davec$ spctl -a -t exec -vv /Users/davec/Desktop/kJams\ 2.app 
>>> /Users/davec/Desktop/kJams 2.app: accepted
>>> source=Developer ID
>>> origin=Developer ID Application: David M. Cotter (GZPG2DNS57)
>> 
>> so… what gives?
> ___
> 
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> 
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
> 
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/cocoa-dev/me%40davecotter.com
> 
> This email sent to m...@davecotter.com

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Is the list alive?

[Steve Mills via Cocoa-dev]

On May 28, 2019, at 19:46:26, Leo via Cocoa-dev  
wrote:
> 
> 
> Hmm... my earlier message today never got through.

Supposedly, these lists are to be done away with at some point. Someone started 
co...@apple-dev.groups.io, which many of us have moved to. Or use the annoying 
and inferior dev forums.developer.apple.com.

--
Steve Mills
Drummer, Mac geek

___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Notarization error: The signature algorithm used is too weak

[Leo via Cocoa-dev]

On 5/28/19 9:26 PM, Richard Charles wrote:

On May 28, 2019, at 3:43 PM, Leo via Cocoa-dev  
wrote:

-I recently contacted Apple again and they pointed me to some resource page 
that was created back in 2016. It briefly mentions a similar error - but still 
without any info on how to solve it:
https://developer.apple.com/library/archive/technotes/tn2206/_index.html#//apple_ref/doc/uid/DTS40007919-CH1-TNTAG301

-A search on this error didn't produce anything useful.

-The tar.gz file in question is an eSellerate licensing framework. As many 
people may know, it's been a popular licensing??platform for Mac software for 
over a decade. While I switched to a different licensing platform some time 
ago, I still have thousands of customers with eSellerate licenses (as I'm sure 
is the situation with many other Mac developers).

As far as I understand, this whole situation has to do something with signing 
files inside tar.gz archives - on which I couldn't find any info either

Looks to me like your eSellerate framework is signed with a version 1 
signature. You need to resign the framework with a version 2 signature.

--Richard Charles




Thanks Richard,

Can you please elaborate on this...

I'm on Xcode 10 and Mojave. As far as I understand, ever since Mavericks 
it's always version 2 signature.


Or am I missing something?

I don't see any option in codesign to specify the signature version.


Thanks,
Leo
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Is the list alive?

[Leo via Cocoa-dev]

Hmm... my earlier message today never got through.
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com