I have upgraded my iphone sdk from 3.1.3 to 3.2.3. But now i have a problem. The project i m working on is not compiling in new sdk. I have changed the target info settings also i.e. base sdk is set to iphone device 4.0. I have follwing build error:
Internal error occurred while creating dependency graph: ASSERTION FAILURE in /SourceCache/DevToolsBase/DevToolsBase- 1691/pbxcore/Target.subproj/PBXTargetBuildContext.m:2061
Details: Assertion failed: [filePath isAbsolutePath]
Object: <PBXTargetBuildContext:0x201779de0>
Method: -setHeadermapToolInvocation:forFilePath:
Thread: <NSThread: 0x20091e040>{name = (null), num = 5}
Backtrace:
0 0x00000001002857d8 -[PBXTargetBuildContext(DependencyGraphEvents) handleFailureInMethod:object:fileName:lineNumber:messageFormat:arguments:] (in DevToolsCore)
1 0x00000001002dab3f _XCAssertionFailureHandler (in DevToolsCore)
2 0x0000000100282342 -[PBXTargetBuildContext setHeadermapToolInvocation:forFilePath:] (in DevToolsCore)
3 0x0000000100141a6b -[XCCompilerSpecification computeDependenciesForFilePath:ofType:outputDirectory:inTargetBuildContext:] (in DevToolsCore)
4 0x0000000100381aa5 -[XCBuildRuleDGSnapshot(DependencyGraphCreation) computeDependenciesForFilePath:ofType:forBuildFileReference:withOutputDirectory:additionalProperties:inTargetBuildContext:] (in DevToolsCore)
5 0x000000010015b3cd -[XCResourcesBuildPhaseDGSnapshot(DependencyGraphCreation) computeDependenciesForBuildFileReference:inTargetBuildContext:] (in DevToolsCore)
6 0x000000010013d4a8 -[XCBuildPhaseDGSnapshot(DependencyGraphCreation) computeDependenciesForAllBuildFileReferencesInTargetBuildContext:] (in DevToolsCore)
7 0x000000010015b0e3 -[XCBuildPhaseDGSnapshot(DependencyGraphCreation) computeDependenciesInTargetBuildContext:] (in DevToolsCore)
8 0x000000010015b031 -[XCResourcesBuildPhaseDGSnapshot(DependencyGraphCreation) computeDependenciesInTargetBuildContext:] (in DevToolsCore)
9 0x000000010012d1eb -[XCProductTypeSpecification computeDependenciesInTargetBuildContext:] (in DevToolsCore)
10 0x0000000100128a19 -[XCNativeTargetDGSnapshot(DependencyGraphCreation) computeDependenciesInTargetBuildContext:] (in DevToolsCore)
11 0x0000000100124ba5 -[PBXTargetBuildContext createDependencyGraphWithTargetDGSnapshot:] (in DevToolsCore)
12 0x0000000100123b62 -[PBXTargetBuildContext(DependencyGraphEvents) dg_setTargetSnapshot:] (in DevToolsCore)
13 0x00007fff83eed0dc __invoking___ (in CoreFoundation)
14 0x00007fff83eecfad -[NSInvocation invoke] (in CoreFoundation)
15 0x000000010012357a -[PBXTargetBuildContext(DependencyGraphEvents) processDependencyGraphEvents] (in DevToolsCore)
16 0x00007fff83eed0dc __invoking___ (in CoreFoundation)
17 0x00007fff83eecfad -[NSInvocation invoke] (in CoreFoundation)
18 0x000000010012309b -[XCInvocationQueue _processNextInvocationInThreadSlotNumber:] (in DevToolsCore)
19 0x0000000100122e0d -[XCInvocationQueue _processInvocationsInThreadSlotNumber:] (in DevToolsCore)
20 0x00007fff829f9e99 __NSThread__main__ (in Foundation)
21 0x00007fff8845ff8e _pthread_start (in libSystem.B.dylib)
22 0x00007fff8845fe41 thread_start (in libSystem.B.dylib)
I have deleted build folder and trying to clean all targets but it does not work.
Are you trying to build an iPad app or an iPhone app?
As far as I know 3.2.x is for iPad.
Moreover, are you trying to run it on the device or on the simulator? if you are running on the simulator, make sure it is set correctly in the project settings.
Related
I am having trouble tracking down a crash from Google maps. Does anyone have any methods I could use to try and profile this to find the issue? I am unable to replicate but users using older devices are having this at an alarming rate.
Fatal Exception: NSInvalidArgumentException
0 CoreFoundation 0x182bbad8c __exceptionPreprocess
1 libobjc.A.dylib 0x181d745ec objc_exception_throw
2 CoreFoundation 0x182bc8098 __methodDescriptionForSelector
3 CoreFoundation 0x182bc05c8 ___forwarding___
4 CoreFoundation 0x182aa641c _CF_forwarding_prep_0
5 QuartzCore 0x186d40f24 -[CALayer display]
6 mfa 0x1006a4930 -[GMSOverlayLayer display]
7 QuartzCore 0x186cb28f4 CA::Context::commit_transaction(CA::Transaction*)
8 QuartzCore 0x186cda364 CA::Transaction::commit()
9 QuartzCore 0x186cdb1e4 CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*)
10 CoreFoundation 0x182b62910 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__
11 CoreFoundation 0x182b60238 __CFRunLoopDoObservers
12 CoreFoundation 0x182b60884 __CFRunLoopRun
13 CoreFoundation 0x182a80da8 CFRunLoopRunSpecific
14 GraphicsServices 0x184a65020 GSEventRunModal
15 UIKit 0x18ca9d758 UIApplicationMain
16 mfa 0x1002b1f98 main + 24 (AppDelegate.swift:24)
17 libdyld.dylib 0x182511fc0 start
This is a known bug on crashes occurring when removing overlays that was reported in Google's Issue Tracker: https://issuetracker.google.com/issues/130331383
The Release Notes for Maps SDK for IOS confirm this is fixed in version 3.2.0.
Version 3.2.0 - July 8, 2019
Resolved Issues:
Fixed a crashing bug that occurred occasionally
when removing overlays from a map.
Updating to 3.2.0 or the latest version should resolve this issue.
I've used MAMP Pro for years and never experienced this issue, until the last week or so. I haven't installed any updates for MacOS or MAMP Pro in that time.
On starting MAMP Pro the servers start to boot, MySQL fires up fine and before Apache can start properly the whole MAMP App crashes.
I'll not post the full crash report for fear of sending readers to sleep, however here is what I have worked out as the failing thread...
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff6d9fefce __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff6db3c150 pthread_kill + 333
2 libsystem_c.dylib 0x00007fff6d95b30a abort + 127
3 net.hockeyapp.sdk.mac 0x000000010b5a3c02 uncaught_exception_handler + 27
4 com.apple.CoreFoundation 0x00007fff4633fbd2 __handleUncaughtException + 770
5 libobjc.A.dylib 0x00007fff6ccc4a41 _objc_terminate() + 91
6 net.hockeyapp.sdk.mac 0x000000010b591417 BITCrashUncaughtCXXTerminateHandler() + 766
7 libc++abi.dylib 0x00007fff6b95b7c9 std::__terminate(void (*)()) + 8
8 libc++abi.dylib 0x00007fff6b95b843 std::terminate() + 51
9 libdispatch.dylib 0x00007fff6d875e9c _dispatch_client_callout + 28
10 libdispatch.dylib 0x00007fff6d881471 _dispatch_main_queue_callback_4CF + 1148
11 com.apple.CoreFoundation 0x00007fff46268b99 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9
12 com.apple.CoreFoundation 0x00007fff4622b44a __CFRunLoopRun + 2586
13 com.apple.CoreFoundation 0x00007fff4622a797 CFRunLoopRunSpecific + 487
14 com.apple.HIToolbox 0x00007fff4553f866 RunCurrentEventLoopInMode + 286
15 com.apple.HIToolbox 0x00007fff4553f5d6 ReceiveNextEventCommon + 613
16 com.apple.HIToolbox 0x00007fff4553f354 _BlockUntilNextEventMatchingListInModeWithFilter + 64
17 com.apple.AppKit 0x00007fff4383ca23 _DPSNextEvent + 2085
18 com.apple.AppKit 0x00007fff43fd1e6c -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
19 com.apple.AppKit 0x00007fff43831831 -[NSApplication run] + 764
20 com.apple.AppKit 0x00007fff438009d2 NSApplicationMain + 804
21 libdyld.dylib 0x00007fff6d8af145 start + 1
Has anyone else experienced this, or can offer an explanation of how I might be able to fix it? I work offline a lot so not being able to fire up MAMP is a game changer.
Cheers.
My issue is this: When connected to the web, Mamp freezes and takes several minutes just to load pages. As soon as I disconnect from the web- it loads pages immediately.
I've Flushed DNS, cleared caches etc all to no avail. I'm on a Macbook, tried editing etc/hosts and still nothing. Didn't change anything yet it all just came out of nowhere.
Frustrating and can't work properly like this.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
quit and restart, quit and restart, ..., for many times.
I got a log shown below:
Process: Xcode [1156]
Path: /Users/USER/Desktop/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 4.5 (1839)
Build Info: IDEApplication-1839000000000000~3
Code Type: X86-64 (Native)
Parent Process: launchd [150]
User ID: 502
Date/Time: 2012-09-25 21:02:15.533 +0800
OS Version: Mac OS X 10.8 (12A269)
Report Version: 10
Interval Since Last Report: 1620650 sec
Crashes Since Last Report: 66
Per-App Interval Since Last Report: 209706 sec
Per-App Crashes Since Last Report: 62
Anonymous UUID: 410E9490-9BA7-4C02-8213-2D855F72E50B
Crashed Thread: 1 Dispatch queue: com.apple.root.default-priority
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
ProductBuildVersion: 4G182
ASSERTION FAILURE in /SourceCache/IDEFoundation/IDEFoundation-1877/Framework/Classes/Model/SourceControl/IDESourceControlWorkspaceMonitor.m:1054
Details: Attempted to add repository (IDESourceControlRepository) Name:xuexi#192.168.0, Type:Subversion,
Location:svn://xuexi#192.168.0.109 when (IDESourceControlRepository) Name:xuexi#192.168.0,
Type:Subversion,
Location:svn://xuexi#192.168.0.109 already existed.
Object: <IDESourceControlWorkspaceMonitor: 0x408e59140>
Method: -_findWorkingTreesForFilePath:
Thread: <NSThread: 0x40937d480>{name = (null), num = 11}
Hints: None
Backtrace:
0 0x00000001075167ef -[IDEAssertionHandler handleFailureInMethod:object:fileName:lineNumber:messageFormat:arguments:] (in IDEKit)
1 0x00000001067e02a5 _DVTAssertionFailureHandler (in DVTFoundation)
2 0x0000000107073cfd __block_global_5 (in IDEFoundation)
3 0x00007fff93f9acac -[NSBlockOperation main] (in Foundation)
4 0x00007fff93f70bb6 -[__NSOperationInternal start] (in Foundation)
5 0x00007fff93f783d1 __block_global_6 (in Foundation)
6 0x00007fff8c07bf3d _dispatch_call_block_and_release (in libdispatch.dylib)
7 0x00007fff8c0780fa _dispatch_client_callout (in libdispatch.dylib)
8 0x00007fff8c07923e _dispatch_worker_thread2 (in libdispatch.dylib)
9 0x00007fff942f6ceb _pthread_wqthread (in libsystem_c.dylib)
10 0x00007fff942e11b1 start_wqthread (in libsystem_c.dylib)
objc[1156]: garbage collection is ON
abort() called
really need help!
How could I locate the crash code from the crash log in my ip4 device? As the crashed thread 0 presents a serial frameworks and main.m, I couldn't locate the accurate code launched this crash and debug it. Any suggestion? Thanks in advance!
Incident Identifier: B6BD84B7-CE0A-485D-A877-0FD0F5B75933
CrashReporter Key: b0b97a37f2a1e4911ce2ef34e1793e028463bb67
Hardware Model: iPhone3,1
Process: myApp [11615]
Path: /var/mobile/Applications/28AE71F2-36CA-4A87-83D9-07DF2DFE74F1/myApp.app/myApp
Identifier: myApp
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2012-06-09 21:12:22.792 +0800
OS Version: iPhone OS 5.1 (9B176)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000b
Crashed Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libobjc.A.dylib 0x36721f78 0x3671e000 + 16248
1 MapKit 0x34e7ace6 0x34e68000 + 77030
2 CoreFoundation 0x3525f1f4 0x35247000 + 98804
3 Foundation 0x311b6740 0x31112000 + 673600
4 CoreFoundation 0x352d4acc 0x35247000 + 580300
5 CoreFoundation 0x352d4298 0x35247000 + 578200
6 CoreFoundation 0x352d303e 0x35247000 + 573502
7 CoreFoundation 0x3525649e 0x35247000 + 62622
8 CoreFoundation 0x35256366 0x35247000 + 62310
9 GraphicsServices 0x36552432 0x3654e000 + 17458
10 UIKit 0x3234ce76 0x3231b000 + 204406
11 myApp 0x0001bac0 main (main.m:16)
12 myApp 0x0001ba80 start + 32
Is this the most recent version of your code that is crashing or a previous installed version?
If you are archiving your builds, you should be able to resymbolicate them via the XCode organizer. I think the most important thing is that you have a .dSYM files handy on your development machine for any builds you have installed on your various devices.
Here's a bit of Apple information on how to analyze crash reports.
Here is also a very related question here on StackOverflow that may help you out.
I am setting up an Android environment for the first time on Eclipse. I have many years of Eclipse experience, but new to Android. This is being done on an Apple Mac Mini, running MacOSX 10.6.3. I am using the latest Eclipse Classic, version 3.5.2. I am trying to get the tiny hello world program running.
When I run it, I get the following in the console window of Eclipse:
[2010-06-12 13:48:08 - HelloAndroid] Automatic Target Mode: launching new emulator with compatible AVD 'Android2.2AVD'
[2010-06-12 13:48:08 - HelloAndroid] Launching a new emulator with Virtual Device 'Android2.2AVD'
[2010-06-12 13:48:11 - HelloAndroid] New emulator found: emulator-5554
[2010-06-12 13:48:11 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...
[2010-06-12 13:48:12 - Emulator] 2010-06-12 13:48:12.783 emulator[50495:903] Warning once: This application, or a library it uses, is using NSQuickDrawView, which has been deprecated. Apps should cease use of QuickDraw and move to Quartz.
[2010-06-12 13:48:19 - HelloAndroid] emulator-5554 disconnected! Cancelling 'com.example.helloandroid.HelloAndroid activity launch'!
The emulator crashes with the following info.
I have followed all the instructions for running the hello world sample.
Anyone have any ideas?
Process: emulator [50398]
Path: /Users/jeremy/android-sdk-mac_86/tools/emulator
Identifier: emulator
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: eclipse [50388]
Date/Time: 2010-06-12 13:28:38.595 -0400
OS Version: Mac OS X 10.6.3 (10D573)
Report Version: 6
Interval Since Last Report: 363037 sec
Crashes Since Last Report: 9
Per-App Crashes Since Last Report: 7
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000007fd000
Crashed Thread: 4
Thread 0: Dispatch queue: com.apple.main-thread
0 emulator 0x000eed4e helper_set_cp15 + 30
Thread 1:
0 libSystem.B.dylib 0x9020bbd2 __workq_kernreturn + 10
1 libSystem.B.dylib 0x9020c168 _pthread_wqthread + 941
2 libSystem.B.dylib 0x9020bd86 start_wqthread + 30
Thread 2: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x9020cb42 kevent + 10
1 libSystem.B.dylib 0x9020d25c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib 0x9020c719 _dispatch_queue_invoke + 163
3 libSystem.B.dylib 0x9020c4be _dispatch_worker_thread2 + 240
4 libSystem.B.dylib 0x9020bf41 _pthread_wqthread + 390
5 libSystem.B.dylib 0x9020bd86 start_wqthread + 30
Thread 3:
0 libSystem.B.dylib 0x901e635a semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x90213ea1 _pthread_cond_wait + 1066
2 libSystem.B.dylib 0x90242a28 pthread_cond_timedwait_relative_np + 47
3 com.apple.audio.CoreAudio 0x9056f965 CAGuard::WaitFor(unsigned long long) + 219
4 com.apple.audio.CoreAudio 0x90572997 CAGuard::WaitUntil(unsigned long long) + 289
5 com.apple.audio.CoreAudio 0x90570294 HP_IOThread::WorkLoop() + 1892
6 com.apple.audio.CoreAudio 0x9056fb2b HP_IOThread::ThreadEntry(HP_IOThread*) + 17
7 com.apple.audio.CoreAudio 0x9056fa42 CAPThread::Entry(CAPThread*) + 140
8 libSystem.B.dylib 0x90213a19 _pthread_start + 345
9 libSystem.B.dylib 0x9021389e thread_start + 34
Thread 4 Crashed:
0 emulator 0x00040380 audioInDeviceIOProc + 96
Thread 4 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x007fd000 ecx: 0x000001fe edx: 0x0198f3f0
edi: 0x00000200 esi: 0x01119850 ebp: 0x01119800 esp: 0xb020fad0
ss: 0x0000001f efl: 0x00010212 eip: 0x00040380 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0x00000037
cr2: 0x007fd000
I had this exact same problem just now, and when I googled around a bit, I found some threads where people mentioned using Logitech USB headsets, and that unplugging those headsets made the problem go away.
I have a Logitech USB desktop microphone, and sure enough, after unplugging it, the problem went away for me, too. Even though the mic was turned off the whole time!
Having connected the Apple LED Cinema Display, just setting audio input to internal solved the problem for me - no need to set external audio playback aside.