Version 6.0 (6A313) crash when refreshing provisioning profiles

Refreshing provisioning profile in Xcode 6 worked for me for a while and xcode 6 crashes today when I refresh it .

Any one can help? I saw there is a ticket on stackoverflow and it does not help in my case.

"Xcode crash when refreshing provisioning profiles"

Xcode crash when refreshing provisioning profiles

Thanks in advance.

 Process:         Xcode [979]

Path: /Applications/Xcode 2.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 6.0 (6299) Build Info: IDEFrameworks-6299000000000000~8 Code Type: X86-64 (Native) Parent Process: launchd [357] Responsible: Xcode [979] User ID: 501

Date/Time: 2014-11-14 11:14:00.919 -0800 OS Version: Mac OS X 10.9.5 (13F34) Report Version: 11 Anonymous UUID: 13628E65-2AA7-5BA1-59E1-B82B3CC26059

Crashed Thread: 15 Dispatch queue: NSManagedObjectContext Queue

Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000

Application Specific Information: ProductBuildVersion: 6A313 UNCAUGHT EXCEPTION (NSInvalidArgumentException): -[NSNull longLongValue]: unrecognized selector sent to instance 0x7fff7c4ba240 UserInfo: (null) Hints: None Backtrace: 0 0x00007fff93a58244 exceptionPreprocess (in CoreFoundation) 1 0x000000010c119184 DVTFailureHintExceptionPreprocessor (in DVTFoundation) 2 0x00007fff963ffe75 objc_exception_throw (in libobjc.A.dylib) 3 0x00007fff93a5b12d -[NSObject(NSObject) doesNotRecognizeSelector:] (in CoreFoundation) 4 0x00007fff939b6272 ___forwarding_ (in CoreFoundation) 5 0x00007fff939b5df8 _CF_forwarding_prep_0 (in CoreFoundation) 6 0x00007fff93eb952b -[NSSQLiteConnection execute] (in CoreData) 7 0x00007fff93ed3fd0 newFetchedRowsForFetchPlan_MT (in CoreData) 8 0x00007fff93ec085f -[NSSQLCore objectsForFetchRequest:inContext:] (in CoreData) 9 0x00007fff93ec0397 -[NSSQLCore executeRequest:withContext:error:] (in CoreData) 10 0x00007fff93ebfe63 -[NSPersistentStoreCoordinator executeRequest:withContext:error:] (in

abort() called

This is part of crash log.

Solution

It works later without any change. It may be caused by developer center issue.

Thanks for comments.