date:20160101

Re: Strange app crash

2016-01-01 Thread Graham Cox

> On 2 Jan 2016, at 1:26 PM, SevenBits  wrote:
> 
> here’s a screenshot from Xcode 

You can copy any text from Xcode and paste it into an email. Same for a crash 
report or log output. There’s no reason to take a screenshot and make everyone 
run around just to get a look at it (and you can’t attach images to emails on 
this list).

—Graham

___

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: Strange app crash

2016-01-01 Thread Roland King

> On 2 Jan 2016, at 10:54, SevenBits  wrote:
> 
> Okay, I reproduced the error. Setting an exception breakpoint didn’t help; 
> the app crashes anyway, leading me to believe that the problem either a) is 
> not an uncaught exception or b) it is an exception, but occurs before the 
> ObjC runtime is initialized.
> 
> I’ve run the app outside of Xcode and got the following crash report:
> 
> https://gist.github.com/SevenBits/dfff392c19f0332d81ef
> 

well it’s not a) because it is an uncaught exception, you can see that because 
it has the word exception all over the crash logs and it’s not been caught
and b) is meaningless

So what do you know - that it’s sending respondsToSelector() to something which 
isn’t an object. So usual things, turn on NSZombies, turn on the address 
sanitizer, whatever else you can find on that options page which looks handy. 
Address sanitizer is new, I haven’t used it, but I’ve heard wonderful things 
about it. GuardMalloc too if you like. The crash is so early you may as well 
just turn on the lot. 

I’d also try stuffing it through instruments to see if I can work out which 
bits of my code have already been run by the time it gets here. It’s unpacked 
the NIB, made windows, views too, so it’s run some stuff. 

Start with those. You could breakpoint in NSApplication updateWindows and poke 
around your threads see what else may be going on, not sure I’d go right there 
however. Would be interesting to see what selector it’s asking something 
whether it responds to. 

___

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: Strange app crash

2016-01-01 Thread Alex Zavatone

Am I correct in assuming that it's throwing an exception before it's drawn the 
first window?

If that is the case, check your window XIB.  It's possible that you have 
something mis-wired there.  If you replace your first XIB with a placeholder, 
does the problem go away?

On Jan 1, 2016, at 9:54 PM, SevenBits wrote:

> Okay, I reproduced the error. Setting an exception breakpoint didn’t help; 
> the app crashes anyway, leading me to believe that the problem either a) is 
> not an uncaught exception or b) it is an exception, but occurs before the 
> ObjC runtime is initialized.
> 
> I’ve run the app outside of Xcode and got the following crash report:
> 
> https://gist.github.com/SevenBits/dfff392c19f0332d81ef
> 
>> On Jan 1, 2016, at 9:31 PM, Roland King  wrote:
>> 
>> 
>>> On 2 Jan 2016, at 10:26, SevenBits  wrote:
>>> 
>>> OS X.
>>> 
>>> Sorry, it’s been a frustrating process.
>>> 
>>> I’m working on gathering the other info; in the meantime, here’s a 
>>> screenshot from Xcode at the moment that crash happens: 
>>> http://i.imgur.com/i7qsNOQ.png?1
>>> 
>> 
>> Looks more like an uncaught exception showing at the top level. Do you have 
>> the breakpoint for ‘All Exceptions’ set so you can see where it is?
>> 
>> Or temporarily wrap that call in a try/catch to catch it.
> 
> ___
> 
> 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/zav%40mac.com
> 
> This email sent to z...@mac.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: Strange app crash

2016-01-01 Thread SevenBits

Okay, I reproduced the error. Setting an exception breakpoint didn’t help; the 
app crashes anyway, leading me to believe that the problem either a) is not an 
uncaught exception or b) it is an exception, but occurs before the ObjC runtime 
is initialized.

I’ve run the app outside of Xcode and got the following crash report:

https://gist.github.com/SevenBits/dfff392c19f0332d81ef

> On Jan 1, 2016, at 9:31 PM, Roland King  wrote:
> 
> 
>> On 2 Jan 2016, at 10:26, SevenBits  wrote:
>> 
>> OS X.
>> 
>> Sorry, it’s been a frustrating process.
>> 
>> I’m working on gathering the other info; in the meantime, here’s a 
>> screenshot from Xcode at the moment that crash happens: 
>> http://i.imgur.com/i7qsNOQ.png?1
>> 
> 
> Looks more like an uncaught exception showing at the top level. Do you have 
> the breakpoint for ‘All Exceptions’ set so you can see where it is?
> 
> Or temporarily wrap that call in a try/catch to catch it.

signature.asc
Description: Message signed with OpenPGP using GPGMail
___

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: Strange app crash

2016-01-01 Thread SevenBits

Okay, trying to reproduce…

> On Jan 1, 2016, at 9:31 PM, Roland King  wrote:
> 
> 
>> On 2 Jan 2016, at 10:26, SevenBits  wrote:
>> 
>> OS X.
>> 
>> Sorry, it’s been a frustrating process.
>> 
>> I’m working on gathering the other info; in the meantime, here’s a 
>> screenshot from Xcode at the moment that crash happens: 
>> http://i.imgur.com/i7qsNOQ.png?1
>> 
> 
> Looks more like an uncaught exception showing at the top level. Do you have 
> the breakpoint for ‘All Exceptions’ set so you can see where it is?
> 
> Or temporarily wrap that call in a try/catch to catch it.



signature.asc
Description: Message signed with OpenPGP using GPGMail
___

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: Strange app crash

2016-01-01 Thread Roland King

> On 2 Jan 2016, at 10:26, SevenBits  wrote:
> 
> OS X.
> 
> Sorry, it’s been a frustrating process.
> 
> I’m working on gathering the other info; in the meantime, here’s a screenshot 
> from Xcode at the moment that crash happens: http://i.imgur.com/i7qsNOQ.png?1
> 

Looks more like an uncaught exception showing at the top level. Do you have the 
breakpoint for ‘All Exceptions’ set so you can see where it is? 

Or temporarily wrap that call in a try/catch to catch it. 
___

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

Fwd: Strange app crash

2016-01-01 Thread SevenBits

OS X.

Sorry, it’s been a frustrating process.

I’m working on gathering the other info; in the meantime, here’s a screenshot 
from Xcode at the moment that crash happens: http://i.imgur.com/i7qsNOQ.png?1


> Begin forwarded message:
> 
> From: SevenBits 
> Subject: Re: Strange app crash
> Date: January 1, 2016 at 9:23:52 PM EST
> To: Alex Zavatone 
> 
>> On Jan 1, 2016, at 9:18 PM, Alex Zavatone  wrote:
>> 
>> Mac OS or iOS?
>> 
>> You state there is a crash, but don't supply a crash log or tell us what 
>> type of a crash it is.
>> 
>> How do you expect us to help you?  Help us help you.
>> 
>> On Jan 1, 2016, at 9:14 PM, SevenBits wrote:
>> 
>>> Hi list,
>>> 
>>> Xcode has decided not to cooperate with me.
>>> 
>>> My latest app is crashing constantly when I launch it. It crashes 
>>> immediately, without showing any UI or starting the app delegate, so I know 
>>> that my code isn’t the cause. The app will be able to run 3 or 4 times 
>>> before this happens. This did not happen before I started accessing, and 
>>> writing to, my app’s Application Support directory.
>>> 
>>> The app is sandboxed, destined for the MAS, and is using ARC. Deleting my 
>>> app’s sandbox container fixes the problem, until it tries to write to the 
>>> Application Support directory and the cycle starts all over.
>>> 
>>> Does anyone have any pointers? Seen this before?
>>> 
>>> Thanks in advance.
>>> ___
>>> 
>>> 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/zav%40mac.com
>>> 
>>> This email sent to z...@mac.com
>> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
___

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: Strange app crash

2016-01-01 Thread Roland King


> On 2 Jan 2016, at 10:14, SevenBits  wrote:
> 
> Hi list,
> 
> Xcode has decided not to cooperate with me.
> 
> My latest app is crashing constantly when I launch it. It crashes 
> immediately, without showing any UI or starting the app delegate, so I know 
> that my code isn’t the cause. The app will be able to run 3 or 4 times before 
> this happens. This did not happen before I started accessing, and writing to, 
> my app’s Application Support directory.
> 
> The app is sandboxed, destined for the MAS, and is using ARC. Deleting my 
> app’s sandbox container fixes the problem, until it tries to write to the 
> Application Support directory and the cycle starts all over.
> 
> Does anyone have any pointers? Seen this before?
> 
> Thanks in advance.
> ___

crash report? stack trace? Anything from any of the logfiles in /var/log. If 
it’s crashing it’s dumping a crash report somewhere. Without that it’s just 
guesswork. 
___

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: Strange app crash

2016-01-01 Thread Alex Zavatone

Mac OS or iOS?

You state there is a crash, but don't supply a crash log or tell us what type 
of a crash it is.

How do you expect us to help you?  Help us help you.

On Jan 1, 2016, at 9:14 PM, SevenBits wrote:

> Hi list,
> 
> Xcode has decided not to cooperate with me.
> 
> My latest app is crashing constantly when I launch it. It crashes 
> immediately, without showing any UI or starting the app delegate, so I know 
> that my code isn’t the cause. The app will be able to run 3 or 4 times before 
> this happens. This did not happen before I started accessing, and writing to, 
> my app’s Application Support directory.
> 
> The app is sandboxed, destined for the MAS, and is using ARC. Deleting my 
> app’s sandbox container fixes the problem, until it tries to write to the 
> Application Support directory and the cycle starts all over.
> 
> Does anyone have any pointers? Seen this before?
> 
> Thanks in advance.
> ___
> 
> 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/zav%40mac.com
> 
> This email sent to z...@mac.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

Strange app crash

2016-01-01 Thread SevenBits

Hi list,

Xcode has decided not to cooperate with me.

My latest app is crashing constantly when I launch it. It crashes immediately, 
without showing any UI or starting the app delegate, so I know that my code 
isn’t the cause. The app will be able to run 3 or 4 times before this happens. 
This did not happen before I started accessing, and writing to, my app’s 
Application Support directory.

The app is sandboxed, destined for the MAS, and is using ARC. Deleting my app’s 
sandbox container fixes the problem, until it tries to write to the Application 
Support directory and the cycle starts all over.

Does anyone have any pointers? Seen this before?

Thanks in advance.


signature.asc
Description: Message signed with OpenPGP using GPGMail
___

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: CG Error with popovers - known issue?

2016-01-01 Thread Alex Kac

We’ve seen the same issue. So its definitely an OS X issue.

>> On 31 Dec 2015, at 9:32 AM, Jonathan Mitchell  
>> wrote:
>> 
>> I am seeing the exact same issue with NSPopover on 10.11.
>> The stack trace is identical.
>> Did you manage to make any further progress with this?
>> 
> 
> 
> Not really. I was able to determine that the error is triggered when a 
> popover’s edge changes (say from bottom to left and vice versa) but otherwise 
> my own code has no influence on it.
> 


___

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: App refuses to launch after adding iCloud Drive support

2016-01-01 Thread Quincey Morris

On Jan 1, 2016, at 01:19 , Graham Cox  wrote:
> 
> It’s not essential that I do this - presumably the user can add folders as 
> they wish, but since iApps and other Apple apps do this, it would be nice to 
> follow suit.

According to this thread on the developer forums:

https://forums.developer.apple.com/message/57044#57044 

> “In order to set up an iCloud container (visible to the user as the special 
> folder marked with the app icon), you *do* still need need to have the 
> traditional iCloud entitlements and Mac App Store distribution signatures.”

So I think you can’t do like you want to do. OTOH, I’m relaying hearsay, so 
there might be a better answer if you ask in the right place (e.g. a TSI?).

___

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: Getting key data out of the keychain

2016-01-01 Thread Chris Ridd

> On 1 Jan 2016, at 13:09, Andreas Mayer  wrote:
> 
> But I *still* don't know how to get at the key bytes of a SecKeyRef. :P

Try asking on the apple-cdsa mailing list. It covers the security frameworks in 
OS X, including (hence the historical name) CDSA.

Chris
___

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: Getting key data out of the keychain

2016-01-01 Thread Andreas Mayer

Hello Marco,

> Am 31.12.2015 um 19:23 schrieb Marco S Hyman :
> 
> After much play, head scratching, and code that managed to add a bogus entry 
> to the keychain that couldn’t be deleted (time machine to the rescue) I came 
> up with one way to add an entry to the keychain and retrieve the entry: use 
> the Generic Password class.  In swift the code to fetch the password looked 
> like this -- password returned as NSData.

thanks, but that's not what I was looking for.

Actually, I am able to save and retrieve the key just fine. It's just that I 
only get a SecKeyRef, not the binary data.

The trick to put a valid key into the keychain is to use 
SecKeyGenerateSymmetric() and have it save the key in the keychain immediately. 
You will then be able to retrieve it normally using SecItemCopyMatching().
To have SecKeyGenerateSymmetric() put the key into the default keychain, add 
the attribute kSecAttrIsPermanent with a value of true.
Or you can add the kSecUseKeychain attribute and supply the keychain you want 
it to use.

For now, I decided to work around the key bytes extraction problem by using 
SecTransforms - which take a SecKeyRef - for encoding instead of CCCrypt().
The reason I went with CCCrypt() first is, that I had a problem with creating 
SHA1 hashes with SecTransform and running that parallel inside an NSOperation. 
My application actually locked up with dozens of those NSOperations waiting on 
some semaphore. So I had to use CommonCrypto for that.

I didn't run into any problems with the SecEncrypt/DecryptTransform.

Here is my code if anyone is interested:

static func encryptData(data: NSData, withKey key: SecKeyRef) throws -> 
NSData {
return try cryptData(data, withKey: key, transformCreate: 
SecEncryptTransformCreate)
}

static func decryptData(data: NSData, withKey key: SecKeyRef) throws -> 
NSData {
return try cryptData(data, withKey: key, transformCreate: 
SecDecryptTransformCreate)
}

static func cryptData(data: NSData, withKey key: SecKeyRef, 
transformCreate: (SecKey, UnsafeMutablePointer?>) -> 
SecTransform) throws -> NSData {
var result: NSData?
var transform: SecTransformRef?
var error: Unmanaged?

transform = transformCreate(key, &error)
if error != nil { let retainedError: ErrorType = 
error!.takeRetainedValue(); throw retainedError }

SecTransformSetAttribute(transform!, kSecPaddingKey, 
kSecPaddingPKCS7Key, &error);
if error != nil { let retainedError: ErrorType = 
error!.takeRetainedValue(); throw retainedError }

SecTransformSetAttribute(transform!, 
kSecTransformInputAttributeName,
data, &error);
if error != nil { let retainedError: ErrorType = 
error!.takeRetainedValue(); throw retainedError }

result = SecTransformExecute(transform!, &error) as? NSData;
if error != nil { let retainedError: ErrorType = 
error!.takeRetainedValue(); throw retainedError }

return result!
}


But I *still* don't know how to get at the key bytes of a SecKeyRef. :P


Andreas
___

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: App refuses to launch after adding iCloud Drive support

2016-01-01 Thread Graham Cox

Hmmm, maybe I spoke too soon.

My app appears to be able to access iCloud Drive. Adding/removing the magic 
stuff to info.plist appears NOT to make any difference to this, though caching 
somewhere might be skewing the true picture, don’t know.

What I’d quite like to do is to follow the recommendation in the documentation 
and add a //Documents/ folder to the user’s iCloud drive. So I tried 
the following code, run from -[ appDidFinishLaunching]:


- (void)prepareICloudDrive
{
// creates subfolders in the iCloud drive if needed

NSDictionary* ubiquityContainers = [[NSBundle mainBundle] 
objectForInfoDictionaryKey:@"NSUbiquitousContainers"];

if( ubiquityContainers )
{
for( NSString* containerID in ubiquityContainers )
{
NSDictionary*   container = [ubiquityContainers 
objectForKey:containerID];

if( container )
{
// need to do this on a thread

NSOperationQueue* opq = [[NSOperationQueue 
alloc] init];

[opq addOperationWithBlock:^
{
NSFileManager* fm = [[NSFileManager 
alloc] init];
NSURL* iCloudURL = [fm 
URLForUbiquityContainerIdentifier:containerID];  //<—— always returns nil

if( iCloudURL )
{
// append //Documents/ 
to the URL

NSString* appContainerName = 
[[container objectForKey:@"NSUbiquitousContainerName"] 
stringByAppendingPathComponent:@"Documents"];
NSURL* iCloudDocFolderURL = 
[iCloudURL URLByAppendingPathComponent:appContainerName isDirectory:YES];
NSError* error = nil;

if( ![fm 
createDirectoryAtURL:iCloudDocFolderURL withIntermediateDirectories:YES 
attributes:nil error:&error])
{
NSLog(@"failed to 
create iCloud storage at %@, error = %@", iCloudDocFolderURL, error );
}
}

[fm release];
[opq release];
}];
}
}
}
}


The problem I have is that when the block runs, the result of 
-URLForUbiquityContainerIdentifier: is nil. The docs for this state that I have 
to pass a string in the form ., which doesn’t seem to be the 
case for the string the other documentation has (‘iCloud.com..'. It’s unclear how this is supposed to work without having 
entitlements, but the docs state that 10.11 apps don’t need the entitlements, 
just the magic.

It’s not essential that I do this - presumably the user can add folders as they 
wish, but since iApps and other Apple apps do this, it would be nice to follow 
suit.

Since 10.11 changed how this works, I’d expect to see an explanation at least 
in the release notes, but I don’t see anything there. Is there any other info 
about this? The docs as usual are ambiguous and self-contradictory.

—Graham





> On 1 Jan 2016, at 5:59 PM, Graham Cox  wrote:
> 
> Thank you Quincey!
> 
> I was thinking that if Apple want this stuff adopted, they really ought to 
> make it much easier. Turns out they did :)
> 
> 
> —Graham
> 
> 
> 
> 
>> On 1 Jan 2016, at 1:39 PM, Quincey Morris 
>>  wrote:
>> 
>> 
>>  
>> https://developer.apple.com/library/mac/documentation/General/Conceptual/iCloudDesignGuide/Chapters/DesigningForDocumentsIniCloud.html#//apple_ref/doc/uid/TP40012094-CH2-SW20
>> 
>> at the end of the page under the heading "Enabling Document Storage in 
>> iCloud Drive”.
>> 
>> In brief, for 10.11 non-Mac-App-Store access, do NOT set the entitlement, 
>> but DO add the magic thing to your info.plist.
>> 
> 
> 
> ___
> 
> 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/graham.cox%40bigpond.com
> 
> This email sent to graham@bigpond.com


___

Cocoa-dev maili

Re: Strange app crash

Re: Strange app crash

Re: Strange app crash

Re: Strange app crash

Re: Strange app crash

Re: Strange app crash

Fwd: Strange app crash

Re: Strange app crash

Re: Strange app crash

Strange app crash

Re: CG Error with popovers - known issue?

Re: App refuses to launch after adding iCloud Drive support

Re: Getting key data out of the keychain

Re: Getting key data out of the keychain

Re: App refuses to launch after adding iCloud Drive support

15 matches

Site Navigation

Mail list logo

Footer information