I tried to run the phonon example code, Music player Example, came with the sdk. It runs well on Windows, but crashes while starting on Mac OS Snow Leopard 10.6.8. This is the crash details:
crash line:
audioOutput = new Phonon::AudioOutput(Phonon::MusicCategory, this);
crash log and call stack:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0×0000000000000008
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 QtCore 0×0000000100e9c8f2 QObject::moveToThread(QThread*) + 34
1 QtDBus 0×00000001010b4912 _q_sessionBus() + 162
2 QtDBus 0×00000001010b4a71 QDBusConnection::sessionBus() + 17
3 phonon 0×000000010001beab Phonon::FactoryPrivate::FactoryPrivate() + 219
4 phonon 0×000000010001edc2 Phonon::Factory::registerFrontendObject(Phonon::MediaNodePrivate*) + 146
5 phonon 0×0000000100028f92 Phonon::MediaNodePrivate::MediaNodePrivate(Phonon::MediaNodePrivate::CastId) + 82
6 phonon 0×00000001000137bf Phonon::AudioOutput::AudioOutput(Phonon::Category, QObject*) + 63
7 com.yourcompany.qmusicplayer 0×00000001000026cc MainWindow::MainWindow() + 108
8 com.yourcompany.qmusicplayer 0×00000001000024a2 main + 114
9 com.yourcompany.qmusicplayer 0×0000000100002404 start + 52
I believe that this was a problem with Qt 4.8.0. It required dbus to be installed on your machine. There are workarounds like installing dbus on your machine or rebuilding Qt with a patch, but I believe it's fixed in Qt 4.8.1 so probably just use that.
Related
I recently submitted an app update to the App Store. The app runs well in Xcode (on device and simulator) for all versions of iOS including iOS 13+. I was surprised that it was rejected for crashing at startup. I checked using a Testflight build and it only crashed when ran on a device with iOS 13+. I could not replicate crashes from Xcode as it only crashes on the builds from Tesflight.
I've been researching online and see that this is not an uncommon issue, however, I can't identify what's the issue in my case. I've tried changing the build settings in Xcode and building from an older version of Xcode (10.2.1, doesn't work bc I use newer classes not compatible with anything lower than Xcode 11). I also tried changing the swift compiler optimization level to zero in the build settings. To upload a build to Tesflight, I am exporting the archive and uploading to iTunes Connect using Apple's Transporter app.
Using the crash log and podfile description below, can anyone identify the issue and/or make a suggestion on what's going wrong in the build.
Crash Log
OS Version: iPhone OS 13.2.3 (17B111)
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
libsystem_kernel.dylib 0x00000001baaf7ec4 __pthread_kill + 8
libsystem_pthread.dylib 0x00000001baa13774 pthread_kill$VARIANT$mp + 112
libsystem_c.dylib 0x00000001ba967844 abort + 100
libc++abi.dylib 0x00000001baac07d4 __cxa_bad_cast + 0
libc++abi.dylib 0x00000001baac09c4 demangling_unexpected_handler+ 6596 () + 0
libobjc.A.dylib 0x00000001baa28258 _objc_terminate+ 25176 () + 124
libc++abi.dylib 0x00000001baacd304 std::__terminate(void (*)+ 58116 ()) + 16
libc++abi.dylib 0x00000001baacd29c std::terminate+ 58012 () + 44
libdispatch.dylib 0x00000001ba9cd198 _dispatch_client_callout + 36
libdispatch.dylib 0x00000001ba975fd8 _dispatch_block_invoke_direct$VARIANT$mp + 224
FrontBoardServices 0x00000001bfe4e4c8__FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 40
FrontBoardServices 0x00000001bfe4e194 -[FBSSerialQueue _queue_performNextIfPossible] + 404
FrontBoardServices 0x00000001bfe4e6bc -[FBSSerialQueue _performNextFromRunLoopSource] + 28
CoreFoundation 0x00000001bac7d7c4 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24
CoreFoundation 0x00000001bac7d71c __CFRunLoopDoSource0 + 80
CoreFoundation 0x00000001bac7ceb4 __CFRunLoopDoSources0 + 180
CoreFoundation 0x00000001bac78000 __CFRunLoopRun + 1080
CoreFoundation 0x00000001bac778a0 CFRunLoopRunSpecific + 464
GraphicsServices 0x00000001c4bcf328 GSEventRunModal + 104
UIKitCore 0x00000001bed68740 UIApplicationMain + 1936
OnStation 0x0000000100a553ac main + 103340 (main.m:14)
libdyld.dylib 0x00000001bab02360 start + 4
Podfile
pod 'AWSCore'
pod 'AWSSNS'
pod 'AWSS3'
pod 'AWSCognito'
pod 'AWSCognitoIdentityProvider'
pod 'AWSCognitoSync'
pod 'AWSDynamoDB'
pod 'Flurry-iOS-SDK/FlurrySDK'
pod 'ArcGIS-Runtime-SDK-iOS', '100.2.1'
pod 'SVProgressHUD'
pod 'UICKeyChainStore'
pod 'RangeSeekSlider'
pod 'PubNub', '~> 4'
pod 'MessageKit'
I’m going to guess that this is due to a situation parallel to
iOS11 WKWebview crash due to NSInvalidUnarchiveOperationException
In other words, I'm guessing that you have something in your storyboard that comes from another framework that you need to link explicitly. That sort of thing often doesn’t crash from Xcode but does crash when launching independently.
While checking Xcode 8.2 changes I found that now we can record simulator using Terminal.
So I am trying to record video from iOS simulator as describe in this Apple Document.
Taking a Screenshot or Recording a Video Using the Command Line
Command:
xcrun simctl io booted recordVideo demoVideo.mp4
Error:
2016-12-20 15:44:27.206 simctl[6434:984477] *** Assertion failure in +[SimDisplayVideoWriter videoWriter], /BuildRoot/Library/Caches/com.apple.xbs/Sources/CoreSimulator/CoreSimulator-338.16/SimulatorKit/SimDisplayVideoWriter.m:48
2016-12-20 15:44:27.207 simctl[6434:984477] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Failed to create metal device for video writer.'
*** First throw call stack:
(
0 CoreFoundation 0x00007fffa07f90db __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fffb548ba2a objc_exception_throw + 48
2 CoreFoundation 0x00007fffa07fdc32 +[NSException raise:format:arguments:] + 98
3 Foundation 0x00007fffa2266d50 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
4 SimulatorKit 0x000000010a248c53 +[SimDisplayVideoWriter videoWriter] + 1015
5 SimulatorKit 0x000000010a2499e5 +[SimDisplayVideoWriter videoWriterForURL:fileType:] + 316
6 simctl 0x000000010a168a00 simctl + 31232
7 simctl 0x000000010a166bee simctl + 23534
8 simctl 0x000000010a170d52 simctl + 64850
9 libdispatch.dylib 0x00007fffb5d3fef7 _dispatch_call_block_and_release + 12
10 libdispatch.dylib 0x00007fffb5d370b8 _dispatch_client_callout + 8
11 libdispatch.dylib 0x00007fffb5d39029 _dispatch_root_queue_drain + 917
12 libdispatch.dylib 0x00007fffb5d38c47 _dispatch_worker_thread3 + 99
13 libsystem_pthread.dylib 0x00007fffb5f84712 _pthread_wqthread + 1299
14 libsystem_pthread.dylib 0x00007fffb5f841ed start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException
Abort trap: 6
iOS simulator and application both working properly. This error only shown in Terminal.
I am using Xcode 8.2. Tried in Simulator of iPhone 7, 7 Plus, SE with iOS 10.2.
Am I missing any detail or need to install and component?
Video recording is only supported on Macs that support Metal. If your system doesn't support metal, you will see an abort with that message. Yeah, we should make that error message more user friendly.
To see a list of supported systems, you can check out https://support.apple.com/en-us/HT205073
this was also fixed in Xcode 8.3 Beta: http://adcdownload.apple.com/Developer_Tools/Xcode_8.3_beta/Release_Notes_for_Xcode_8.3_beta.pdf
• Videos recorded by the simctl tool of the xcrun command line tool now support scrubbing and import into video editors correctly. (29654098)
I did not test this currently but it is quite possible that in stable version of Xcode this bug will be fixed
I'm dealing with some legacy code, won't compile on anything later than SDK 10.5 due to randomly abolished APIs, so I have good reason to stick with old compilers. I've been using Xcode 4.6.3; I recently clean-installed from OS X 10.7 to 10.9.
A new problem arises: Xcode reliably crashes on the Run command. I can build my applications just fine; they run successfully if I double-click the built product. But if I try to run directly from Xcode, Xcode crashes. The nature of the app doesn't seem to matter; I have tried this both with commandline and GUI apps. Selfsame result. Any insights?
From the crash report, in case it helps:
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
ProductBuildVersion: 4H1503
UNCAUGHT EXCEPTION (NSInvalidArgumentException): -[__NSCFString alloc]: unrecognized selector sent to instance 0x400c22b60
UserInfo: (null)
Hints: None
Backtrace:
0 0x00007fff8f224244 __exceptionPreprocess (in CoreFoundation)
1 0x00007fff91ebae75 objc_exception_throw (in libobjc.A.dylib)
2 0x00007fff8f22712d -[NSObject(NSObject) doesNotRecognizeSelector:] (in CoreFoundation)
3 0x00007fff8f182272 ___forwarding___ (in CoreFoundation)
4 0x00007fff8f181df8 _CF_forwarding_prep_0 (in CoreFoundation)
5 0x00000001107070a6 -[DBGLLDBDebugLocalService operationWorkerWithLaunchSession:error:] (in DebuggerLLDBService)
6 0x0000000110707593 -[DBGLLDBRunLocalService operationWorkerWithLaunchSession:error:] (in DebuggerLLDBService)
7 0x000000010b1bf8e7 -[IDERunDestination runOperationForLaunchSession:error:] (in IDEFoundation)
8 0x000000010b1be557 -[IDELaunchSchemeAction
I have a problem with my Vagrant VM running on VirtualBox: every time I close the lid of my MacBook, the VM is aborted and I have to 'vagrant up' it again. I don't think it's the intended behaviour, and it's quite annoying to start over every time.
Checking the DiagnosticReports folder I can find a crash report from VirtualBox every time I close the lid with a running VM, this is an extract from the first part:
Process: VBoxHeadless [6267]
Path: /Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless
Identifier: VBoxHeadless
Version: ???
Code Type: X86-64 (Native)
Parent Process: VBoxSVC [6215]
Responsible: VirtualBox [6210]
User ID: 501
Date/Time: 2015-02-15 10:27:16.982 +0100
OS Version: Mac OS X 10.10.2 (14C109)
Report Version: 11
Anonymous UUID: 453DE236-2C46-1B97-1C8F-D91BAF75710E
Sleep/Wake UUID: 21FE4DBC-7544-453E-B166-C48801F5CDDB
Time Awake Since Boot: 35000 seconds
Time Since Wake: 2700 seconds
Crashed Thread: 7 EMT
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
-->
__TEXT 0000000100000000-0000000100008000 [ 32K] r-x/rwx SM=COW /Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8bf734de mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff8bf7264f mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff8b356b34 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff8b355ffb __CFRunLoopRun + 1371
4 com.apple.CoreFoundation 0x00007fff8b355858 CFRunLoopRunSpecific + 296
5 VBoxHeadless.dylib 0x0000000100080b91 TrustedMain + 44177
6 VBoxHeadless.dylib 0x0000000100080e5b TrustedMain + 44891
7 VBoxHeadless.dylib 0x0000000100079b31 TrustedMain + 15409
8 VBoxHeadless 0x0000000100003d95 start + 7061
9 VBoxHeadless 0x0000000100002234 start + 52
Is there anything I can do to fix this thing by myself, or do I have to open a bug report for the VirtualBox support team?
OSX v10.10.2
VirtualBox v4.3.22
Vagrant v1.7.2
This bug has been report to Oracle Virtualbox.
And the bug has just been fixed and released in Virtualbox 4.3.24. You can download the latest version (VirtualBox-4.3.24-98716-OSX.dmg) from https://www.virtualbox.org/wiki/Downloads.
As chaserx pointed out, it's a matter of version.
Reverting to VirtualBox v4.3.20 solved the problem, for the moment...
If anyone is having this problem on Ubuntu, adding following lines to /etc/NetworkManager/NetworkManager.conf and restarting service with sudo service network-manager restart solved the problem for me:
[keyfile]
unmanaged-devices=interface-name:vboxnet0
Source: https://www.virtualbox.org/ticket/13873#comment:16
VirtualBox Manager 5.0.8
Network Manager 1.0.4-0ubuntu5
I cant seem to refresh my provisioning profiles in Xcode without crashes. Every time I press the refresh button in organizer it crashes and I retrieve this line from the error log:
UNCAUGHT EXCEPTION (NSInvalidArgumentException): *** setObjectForKey: object cannot be nil (key: teamId)
So I checked my teamId but dont find anything unusual. Anybody have any ideas what causing my problem? This uses to work for me every time I refreshed my profiles. Even did that this morning for like 10 times.
EDIT:
Heres the crash report if needed:
Process: Xcode [1136]
Path: /Applications/Xcode.app/Contents/MacOS/Xcode
Identifier: com.apple.dt.Xcode
Version: 4.6.1 (2067)
Build Info: IDEApplication-2067000000000000~2
App Item ID: 497799835
App External ID: 14581035
Code Type: X86-64 (Native)
Parent Process: launchd [272]
User ID: 501
Date/Time: 2013-03-15 15:21:43.906 +0100
OS Version: Mac OS X 10.8.3 (12D78)
Report Version: 10
Interval Since Last Report: 14773 sec
Crashes Since Last Report: 9
Per-App Interval Since Last Report: 14523 sec
Per-App Crashes Since Last Report: 7
Anonymous UUID: E5C08B95-3313-ABC3-6BB7-F22E76735A98
Crashed Thread: 2 Dispatch queue: NSManagedObjectContext Queue
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
ProductBuildVersion: 4H512
UNCAUGHT EXCEPTION (NSInvalidArgumentException): *** setObjectForKey: object cannot be nil (key: teamId)
UserInfo: (null)
Hints: None
Backtrace:
0 0x00007fff92639aee __exceptionPreprocess (in CoreFoundation)
1 0x00007fff98d703f0 objc_exception_throw (in libobjc.A.dylib)
2 0x00007fff926c85b7 -[__NSDictionaryM setObject:forKey:] (in CoreFoundation)
3 0x0000000107d42d88 +[DTDKTeamBasedService _createRequestDictionaryForTeam:andPlatform:] (in DTDeviceKit)
4 0x0000000107d45315 +[DTDKDownloadProvisioningProfileService serviceForTeam:andPlatform:andProfileID:withError:] (in DTDeviceKit)
5 0x0000000107d6e1c0 +[DTDKDownloadProvisioningProfileService serviceForProvisioningProfileRecord:withError:] (in DTDeviceKit)
6 0x0000000107d73728 __72+[DTDKPortalDatabase _refreshFromProvisioningProfileListServices:error:]_block_invoke (in DTDeviceKit)
7 0x00007fff9429d4dc developerSubmittedBlockToNSManagedObjectContextPerform (in CoreData)
8 0x00007fff9429d40a -[NSManagedObjectContext performBlockAndWait:] (in CoreData)
9 0x0000000107d73246 +[DTDKPortalDatabase _refreshFromProvisioningProfileListServices:error:] (in DTDeviceKit)
10 0x0000000107d75816 __56+[DTDKPortalDatabase refresh:parentWindow:withCallback:]_block_invoke_5 (in DTDeviceKit)
11 0x00007fff942cd7cf developerSubmittedBlockToNSManagedObjectContextPerform_privateasync (in CoreData)
12 0x00007fff90dd20b6 _dispatch_client_callout (in libdispatch.dylib)
13 0x00007fff90dd347f _dispatch_queue_drain (in libdispatch.dylib)
14 0x00007fff90dd32f1 _dispatch_queue_invoke (in libdispatch.dylib)
15 0x00007fff90dd31c3 _dispatch_worker_thread2 (in libdispatch.dylib)
16 0x00007fff964d4d0b _pthread_wqthread (in libsystem_c.dylib)
17 0x00007fff964bf1d1 start_wqthread (in libsystem_c.dylib)
objc[1136]: garbage collection is ON
abort() called
.....
[The report itself is very large and contains much more than this]
Remove this file:
~/Library/Developer/Xcode/connect1.apple.com 4.6.1.db
before running Xcode 4.6.1.
Here is apple's official workaround:
Run this command in terminal:
mkdir ~/Library/Developer/Xcode/OldPortalDBs; mv ~/Library/Developer/Xcode/connect1.apple.com* ~/Library/Developer/Xcode/OldPortalDBs
Worked like a charm for me.
Someone had this problem at NSCoder Night this week. Cleared by removing:
~/Library/Caches/com.apple.dt.Xcode.
sqlite3 ~/Library/Caches/com.apple.dt.Xcode/PortalData/connect1.apple.com
Shows that file to be an SQLite database, with references to certificates, teams, and profiles. I suspect (but haven't tried) that removing the PortalData folder would be sufficient to clear the error.
Removing this file worked for me.
~/Library/Developer/Xcode/connect1.apple.com 4.6.1.db
Thanks!