Problem deploying Hololens app to emulator from Visual studio 2019 - visual-studio-2019
I am building a simple hololens app using MRTK PalmUpHandMenu, I am able to build the app in unity but not able to deploy on hololens Emulator from visual studio. The app is playing in game mode of unity.
I am using the following tools.
Visual Studio 2019
unity 2019.2.21f1
Windows SDK 10.1.18362.1
Hololens 2 emulator 10.1.18362.1053
mixed reality toolkit 2.3.0
Windows 10 pro
Here are my unity build configuration
Here are my Visual Studio configuration
Here are my Debug logs from the visual studio.
The thread 0x14dc has exited with code 0 (0x0).
'Hololens 2.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\shlwapi_onecore.dll'
CreateDirectory 'C:/Data' failed: Operation has failed with error 0xb7: Cannot create a file when that file already exists.
(current dir: C:/Data/Users/DefaultAccount/AppData/Local/DevelopmentFiles/Template3DVS.Debug_Win32.Salman/Data)
Logging to C:/Data/Users/Visitor0/AppData/Local/Packages/Template3D_pzq3xp76mxafg/TempState/UnityPlayer.log
[0.799436 / 0.830282] - Initializing Unity runtime
Loading native plugins
Loading AudioPluginMsHRTF.dll
Module information:
Built with Compiler Ver '191627012'
Built from '2019.2/staging' branch
Version is '2019.2.21f1 (9d528d026557)'
Debug build
Application type 'D3D'
Exception thrown at 0x77C33E02 in Hololens 2.exe: Microsoft C++ exception: Cn::XH at memory location 0x021CE6F4.
onecoreuap\windows\moderncore\inputv2\inputhost\components\cursor\client\cursorclient.cpp(44)\InputHost.dll!74422413: (caller: 7442258C) ReturnHr(1) tid(1110) 87B20809 onecoreuap\windows\moderncore\inputv2\inputhost\components\cursor\client\cursorclient.cpp(76)\InputHost.dll!744225A3: (caller: 743E034D) ReturnHr(2) tid(1110) 87B20809 OS 'Windows 10 (10.0.18362) 64bit'
[0.001811 / 3.483454] - AppCallbacks::SetCoreWindowEvents
PlayerConnection initialized from C:/Data/Users/DefaultAccount/AppData/Local/DevelopmentFiles/Template3DVS.Debug_Win32.Salman/Data (debug = 0)
'Hololens 2.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\ResourcePolicyClient.dll'
PlayerConnection initialized network socket : 0.0.0.0 55403
Multi-casting "[IP] 192.168.233.185 [Port] 55403 [Flags] 2 [Guid] 4154280957 [EditorId] 0 [Version] 1048832 [Id] UWPPlayerX86(HOLOLENS-PURI8R) [Debug] 0 [PackageName] Template3D_pzq3xp76mxafg" to [225.0.0.222:54997]...
Started listening to [0.0.0.0:55403]
Exception thrown at 0x77C33E02 in Hololens 2.exe: Microsoft C++ exception: _com_error at memory location 0x021C82A0.
Exception thrown at 0x77C33E02 in Hololens 2.exe: Microsoft C++ exception: _com_error at memory location 0x021C82D0.
PlayerConnection already initialized - listening to [0.0.0.0:55403]
'Hololens 2.exe' (Win32): Unloaded 'C:\Windows\SysWOW64\dxilconv.dll'
[5.860794 / 6.849624] - Initialize
'Hololens 2.exe' (Win32): Unloaded 'C:\Windows\system32\HostDriverStore\FileRepository\iigd_dch.inf_amd64_38bfcb542ef4272e\igdinfo32.dll'
'Hololens 2.exe' (Win32): Unloaded 'C:\Windows\system32\HostDriverStore\FileRepository\iigd_dch.inf_amd64_38bfcb542ef4272e\igd12dxva32.dll'
'Hololens 2.exe' (Win32): Unloaded 'C:\Windows\system32\HostDriverStore\FileRepository\iigd_dch.inf_amd64_38bfcb542ef4272e\igdgmm32.dll'
'Hololens 2.exe' (Win32): Unloaded 'C:\Windows\system32\HostDriverStore\FileRepository\iigd_dch.inf_amd64_38bfcb542ef4272e\igd12umd32.dll'
The thread 0x1418 has exited with code 0 (0x0).
[4.616554 / 8.100700] - AppCallbacks::InitializeD3DWindow
The thread 0x1060 has exited with code 0 (0x0).
[XR] Discovering subsystems at path C:/Data/Users/DefaultAccount/AppData/Local/DevelopmentFiles/Template3DVS.Debug_Win32.Salman/Data/UnitySubsystems
GfxDevice: creating device client; threaded=1
[8.129256 / 8.129256] - OnActivated event.
[0.069105 / 8.198361] - OnCoreWindowSizeChanged event (0.00, 0.00, 853.00, 480.00), m_Initialized=False.
[0.001614 / 8.199975] - OnVisibilityChanged event - Visible.
[0.043964 / 8.243939] - OnWindowActivated event - CodeActivated.
Successfully created d3d11 device with debug flag.
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: Microsoft Virtual Render Driver (ID=0x5921)
Vendor: (null)
VRAM: 3967 MB
Initialize engine version: 2019.2.21f1 (9d528d026557)
[AudioManager] InitNormal(tryDeviceDefaults = false, preferredOutputType = FMOD_OUTPUTTYPE_AUTODETECT) attempt with hardAudioDisable: false
[AudioManager] Setting output to FMOD_OUTPUTTYPE_AUTODETECT
[4.750430 / 12.994369] - OnCoreWindowSizeChanged event (0.00, 0.00, 853.00, 480.00), m_Initialized=False.
[AudioManager] InitNormal succeeded with output "FMOD_OUTPUTTYPE_WASAPI". Driver name is "Speakers (Null Audio Driver)". Speaker mode is "FMOD_SPEAKERMODE_STEREO"
The thread 0x1068 has exited with code 0 (0x0).
The thread 0x142c has exited with code 0 (0x0).
onecoreuap\xbox\devices\api\winrt\pnpapiwrapper.cpp(385)\Windows.Gaming.Input.dll!661DF669: (caller: 661E24EF) ReturnHr(1) tid(5a4) 8685C003 [0.000928 / 16.034495] - AppCallbacks::SetupInputEvents
onecoreuap\drivers\mobilepc\sensors\convergence\common\pnpmanager\pnpmanager.cpp(260)\Windows.Devices.Sensors.dll!66152250: (caller: 66152320) Exception(1) tid(1110) 80070490 Element not found.
Exception thrown at 0x77C33E02 in Hololens 2.exe: Microsoft C++ exception: wil::ResultException at memory location 0x021CDA88.
Exception thrown at 0x77C33E02 in Hololens 2.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.
Exception thrown at 0x77C33E02 (KernelBase.dll) in Hololens 2.exe: WinRT originate error - 0x80070490 : 'Element not found.'.
The thread 0x1230 has exited with code 0 (0x0).
onecoreuap\shell\twinapi\windowingenvironment\lib\displayregion.cpp(203)\twinapi.appcore.dll!76A12A30: (caller: 76AC74BD) ReturnHr(1) tid(1110) 80070490 Element not found.
onecoreuap\drivers\mobilepc\sensors\convergence\api\winrt\public\internal\simpleorientation.cpp(127)\Windows.Devices.Sensors.dll!6614B9F3: (caller: 661425E8) Exception(2) tid(1110) 80070490 Element not found.
Exception thrown at 0x77C33E02 in Hololens 2.exe: Microsoft C++ exception: wil::ResultException at memory location 0x021CDD28.
Exception thrown at 0x77C33E02 in Hololens 2.exe: Microsoft C++ exception: [rethrow] at memory location 0x00000000.
onecoreuap\drivers\mobilepc\sensors\convergence\api\winrt\public\internal\sensorserver.cpp(68)\Windows.Devices.Sensors.dll!6613E1CB: (caller: 6613B5FA) ReturnHr(1) tid(1110) 80070490 Element not found.
onecoreuap\drivers\mobilepc\sensors\convergence\api\winrt\public\lib\simpleorientationsensor.cpp(160)\Windows.Devices.Sensors.dll!6612BAA6: (caller: 66129763) ReturnHr(2) tid(1110) 80070490 Element not found.
[0.498514 / 16.533405] - AppCallbacks::SetupOrientationSensorEvents
[1.605693 / 17.290356] - AppCallbacks::Load
[4.326316 / 17.320685] - Starting first scene loading
The following GlobalManagers were stripped from the build (Either because they're not used or not supported on this platform):
ClusterInputManager
[0.126562 / 17.447248] - OnCoreWindowSizeChanged event (0.00, 0.00, 1440.00, 936.00), m_Initialized=True.
Created eye textures with a "texture array" layout. The "single-pass instancing" stereo mode will be used.
[4.957320 / 22.404567] - Finishing first scene loading
[0.019790 / 22.424357] - First level loaded
[0.018120 / 22.442477] - PerformUpdateAndRender started
Windows Mixed Reality spatial locatability state changed to Active.
(Filename: C:\buildslave\unity\build\Modules/VR/HoloLens/HoloLensWorldManager.cpp Line: 324)
End showing splash screen.
Exception thrown at 0x77C33E02 in Hololens 2.exe: Microsoft C++ exception: Cn::XH at memory location 0x0797FA54.
onecoreuap\windows\moderncore\inputv2\inputhost\components\devicewatcher\lib\inputdevicewatcher.cpp(100)\InputHost.dll!7442FA78: (caller: 670B4732) LogHr(1) tid(15f4) 87B20809 [10.309595 / 32.752072] - OnWindowActivated event - Deactivated.
[0.017715 / 32.769787] - OnVisibilityChanged event - Hidden.
[1.026859 / 33.796646] - OnSuspending event.
Trimming D3D resources.
UnloadTime: 6.003500 ms
The thread 0x119c has exited with code 0 (0x0).
The thread 0x1180 has exited with code 0 (0x0).
The thread 0xe60 has exited with code 0 (0x0).
The thread 0xb8c has exited with code 0 (0x0).
The thread 0x15b8 has exited with code 0 (0x0).
The thread 0xc98 has exited with code 0 (0x0).
The thread 0x111c has exited with code 0 (0x0).
The thread 0x1118 has exited with code 1 (0x1).
The thread 0x1110 has exited with code 1 (0x1).
The thread 0x15f4 has exited with code 1 (0x1).
The thread 0x165c has exited with code 1 (0x1).
The thread 0x1178 has exited with code 1 (0x1).
The thread 0x147c has exited with code 1 (0x1).
The thread 0x1198 has exited with code 1 (0x1).
The thread 0x12d0 has exited with code 1 (0x1).
The thread 0x5a4 has exited with code 1 (0x1).
The thread 0xae8 has exited with code 1 (0x1).
The thread 0xce8 has exited with code 1 (0x1).
The thread 0x16d4 has exited with code 1 (0x1).
The thread 0x1498 has exited with code 1 (0x1).
The thread 0xcfc has exited with code 1 (0x1).
The thread 0x155c has exited with code 1 (0x1).
The thread 0x5a8 has exited with code 1 (0x1).
The thread 0xcac has exited with code 1 (0x1).
The thread 0x8d0 has exited with code 1 (0x1).
The thread 0x16c4 has exited with code 1 (0x1).
The thread 0x149c has exited with code 1 (0x1).
The thread 0xe74 has exited with code 1 (0x1).
The thread 0x1108 has exited with code 1 (0x1).
The thread 0xf38 has exited with code 1 (0x1).
The thread 0x1114 has exited with code 1 (0x1).
The thread 0x17ac has exited with code 1 (0x1).
The thread 0xdf8 has exited with code 1 (0x1).
The thread 0x998 has exited with code 1 (0x1).
The thread 0x840 has exited with code 1 (0x1).
The thread 0xa3c has exited with code 1 (0x1).
The thread 0x374 has exited with code 1 (0x1).
The thread 0x638 has exited with code 1 (0x1).
The thread 0x14d4 has exited with code 1 (0x1).
The thread 0x1170 has exited with code 1 (0x1).
The thread 0x870 has exited with code 1 (0x1).
The thread 0xe9c has exited with code 1 (0x1).
The thread 0x12b0 has exited with code 1 (0x1).
The thread 0xd74 has exited with code 1 (0x1).
The thread 0x1220 has exited with code 1 (0x1).
The thread 0x1314 has exited with code 1 (0x1).
The thread 0x644 has exited with code 1 (0x1).
The thread 0x9b8 has exited with code 1 (0x1).
The thread 0x6fc has exited with code 1 (0x1).
The thread 0xe68 has exited with code 1 (0x1).
The thread 0x12a8 has exited with code 1 (0x1).
The thread 0xcec has exited with code 1 (0x1).
The thread 0xcf8 has exited with code 1 (0x1).
The program '[6036] Hololens 2.exe' has exited with code 1 (0x1).
Is my configuration correct or Is there any issue with the compatibility of the version of the tools. Any help is appreciated.
Thank you in advance.
I am having the same problem, also the app deployed to the emulator but nothing happens after that, then the app exited with code (1).
I thought my problem is because I am using Windows 10 pro on bootcamp under a Mac machine, are you running on a Windows machine or a Mac machine?
Related
Kazoo pusher apns not start with reason {'function not exported',{string,lowercase,1}}
I'm new in Erlang and telefony stuff. I'm trying to wake up an iOS app by a push notification sent by Pusher, a Kazoo module that use apns4erl to do the job.
When Pusher try to send a notification, It should start the apns but it get this error:
10:44:22.756 [error] |0000000000|Undefined:Undefined(<0.29186.843>) gen_statem 'apns_com.test.viavoip' in state connected terminated with reason: {'function not exported',{string,lowercase,1}} in gun:normalize_headers/1 line 661
10:44:22.756 [error] |0000000000|string:Undefined(<0.29186.843>) CRASH REPORT Process 'apns_com.test.viavoip' with 0 neighbours crashed with reason: call to undefined function string:lowercase(<<"apns-topic">>)
10:44:22.756 [error] |0000000000|Undefined:Undefined(<0.26408.843>) Supervisor apns_sup had child apns_connection started with {apns_connection,start_link,undefined} at <0.29186.843> exit with reason undef in context child_terminated
10:44:22.760 [error] |0000000000|Undefined:Undefined(<0.31997.843>) gen_server pm_apple terminated with reason: {undef,{gen_statem,call,[<0.29186.843>,{push_notification,<<"ac79eb0d7f28ee04d3539b80a3b6f519cc3db78e7b3840f18b497fadcedc5264">>,<<"{\"aps\":{\"alert\":{\"loc-args\":[\"1089 - Dario Test3\"],\"loc-key\":\"IC_SIL\"},\"call-id\":\"2d25fee2-74d9-43c7-9bfe-90a167f5941a\",\"sound\":\"ring.caf\"},\"call-id\":\"2d25fee2-74d9-43c7-9bfe-90a167f5941a\",\"caller-id-name\":\"Dario Test3\",\"caller-id-number\":\"1089\",\"proxy\":\"sip:94.138.35.201:5060\",\"registration-token\":\"4ad4ad69-6939-4f04-ada6-e827983a4b23\",\"utc_unix_timestamp_ms\":\"16...">>,...},...]}} in gen:do_call/4 line 177
10:44:22.760 [error] |0000000000|Undefined:Undefined(<0.31997.843>) CRASH REPORT Process pm_apple with 0 neighbours exited with reason: {undef,{gen_statem,call,[<0.29186.843>,{push_notification,<<"ac79eb0d7f28ee04d3539b80a3b6f519cc3db78e7b3840f18b497fadcedc5264">>,<<"{\"aps\":{\"alert\":{\"loc-args\":[\"1089 - Dario Test3\"],\"loc-key\":\"IC_SIL\"},\"call-id\":\"2d25fee2-74d9-43c7-9bfe-90a167f5941a\",\"sound\":\"ring.caf\"},\"call-id\":\"2d25fee2-74d9-43c7-9bfe-90a167f5941a\",\"caller-id-name\":\"Dario Test3\",\"caller-id-number\":\"1089\",\"proxy\":\"sip:94.138.35.201:5060\",\"registration-token\":\"4ad4ad69-6939-4f04-ada6-e827983a4b23\",\"utc_unix_timestamp_ms\":\"16...">>,...},...]}} in gen_server:terminate/7 line 812
10:44:22.761 [error] |0000000000|Undefined:Undefined(<0.30380.843>) Supervisor pusher_module_sup had child pm_apple started with pm_apple:start_link() at <0.31997.843> exit with reason {undef,{gen_statem,call,[<0.29186.843>,{push_notification,<<"ac79eb0d7f28ee04d3539b80a3b6f519cc3db78e7b3840f18b497fadcedc5264">>,<<"{\"aps\":{\"alert\":{\"loc-args\":[\"1089 - Dario Test3\"],\"loc-key\":\"IC_SIL\"},\"call-id\":\"2d25fee2-74d9-43c7-9bfe-90a167f5941a\",\"sound\":\"ring.caf\"},\"call-id\":\"2d25fee2-74d9-43c7-9bfe-90a167f5941a\",\"caller-id-name\":\"Dario Test3\",\"caller-id-number\":\"1089\",\"proxy\":\"sip:94.138.35.201:5060\",\"registration-token\":\"4ad4ad69-6939-4f04-ada6-e827983a4b23\",\"utc_unix_timestamp_ms\":\"16...">>,...},...]}} in context child_terminated
It seems that the apns cannot start because of this: string:lowercase(<<"apns-topic">>).
In erl console this command works fine, maybe there is few dependences with a wrong version or some wrong comfiguration.
Any advise?
IOS Simulator quit unexpectedly Xcode 10.1
After running automation tests via Appium in parallel (8 concurrent IOS simulators) I can't run simulator anymore. Reason still is not clear. I tried to reinstall Xcode (v10.1 v9.4), recovered Mac OS, used killall -10 com.apple.CoreSimulator.CoreSimulatorService . When I run simulator there it error message: Simulator quit unexpectedly Process: Simulator [1439] Path: /Applications/Xcode.app/Contents/Developer/Applications/Simulator.app/Contents/MacOS/Simulator Identifier: com.apple.iphonesimulator Version: 10.1 (877) Build Info: Indigo-877000000000000~218 Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: Simulator [1439] User ID: 502 Date/Time: 2019-01-12 16:19:15.922 +0300 OS Version: Mac OS X 10.14.2 (18C54) Report Version: 12 Bridge OS Version: 3.3 (16P53132a) Anonymous UUID: 746485C4-4AA2-44F7-C299-5A58EB4FD0C5 Time Awake Since Boot: 170 seconds System Integrity Protection: enabled Crashed Thread: 7 Dispatch queue: com.apple.iphonesimulator.deviceCoordinatorQueue.457B5DF1-903C-41E0-A9B7-42D97AC96569 Exception Type: EXC_BAD_ACCESS (SIGBUS) Exception Codes: KERN_PROTECTION_FAILURE at 0x000070000b351fe8 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Bus error: 10 Termination Reason: Namespace SIGNAL, Code 0xa Terminating Process: exc handler [1439] VM Regions Near 0x70000b351fe8: Stack 000070000b2cf000-000070000b351000 [ 520K] rw-/rwx SM=COW thread 6 --> STACK GUARD 000070000b351000-000070000b352000 [ 4K] ---/rwx SM=NUL stack guard for thread 7 Stack 000070000b352000-000070000b3d4000 [ 520K] rw-/rwx SM=COW thread 7 Interesting point: when I run Appium test there is still the same error but test is passed as it looks like Simulator still works in headless. Approximately same issue I have found there but it is a little bit different https://shirome9.wordpress.com/2016/11/27/xcode-quit-unexpectedly/ Do you have any idea ?
I don't know the real cause of the issue, but I got resolved by restarting and opening with different simulator.
iOS Simimulator error DTAssetProviderService could not start and restart not helping
I recently upgraded my MBP to El Capitan and XCode 7.3.1 but when I try to run my project in Simulator I get "DTAssetProviderService could not start" error. I've tried clean, restart both tools, and restart my machine, but the issue persists. In /var/log/system.log here is the pertinent logs around that time:
May 18 10:00:38 lsacco-mac kernel[0]: com.apple.dt.Xco[6277] triggered unnest of range 0x7fff92800000->0x7fff92a00000 of DYLD shared region in VM map 0x3ab4b61dbef
May 18 10:00:44 lsacco-mac kernel[0]: xpcproxy[6300] triggered unnest of range 0x7fff8f200000->0x7fff8f400000 of DYLD shared region in VM map 0x3ab4b61dbe725e15. While not abnormal for debuggers, this increases system memory footprint until the target exits.
May 18 10:00:44 lsacco-mac kernel[0]: AMFI: com.apple.dt.ins(pid 6300) - [deny-mmap] mapped executable file has no team identifier in its signature: /usr/local/lib/libwep
May 18 10:00:44 lsacco-mac com.apple.xpc.launchd[1] (com.apple.dt.instruments.dtarbiter.xpc[6300]): Service exited due to signal: Trace/BPT trap: 5
May 18 10:00:44 lsacco-mac DTServiceHub[6299]: dtarbiter XPC call failure (register_client_with_singleton): (os/kern) failure
May 18 10:00:44 lsacco-mac Xcode[6059]: +[DTServiceHubClient localConnectionWithAuthorization:returningServerPid:]: failed to establish connection with DTServiceHub service '/Applications/Xcode.app/Contents/SharedFrameworks/DVTInstrumentsFoundation.framework/Resources/DTServiceHub'
May 18 10:00:44 lsacco-mac Xcode[6059]: iPhoneSimulator: Unable to connect to "com.apple.instruments.deviceservice.lockdown" (Error Domain=DTServiceHubClient Code=-11 "unable to contact local DTServiceHub to bless simulator connection" UserInfo={NSLocalizedDescription=unable to contact local DTServiceHub to bless simulator connection})
May 18 10:00:44 lsacco-mac kernel[0]: xpcproxy[6301] triggered unnest of range 0x7fff8f200000->0x7fff8f400000 of DYLD shared region in VM map 0x3ab4b61dd3a83ab5. While not abnormal for debuggers, this increases system memory footprint until the target exits.
May 18 10:00:44 lsacco-mac com.apple.xpc.launchd[1] (com.apple.ReportCrash[6301]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.ReportCrash
May 18 10:00:44 lsacco-mac ReportCrash[6301]: Saved crash report for com.apple.dt.instruments.dtarbiter[6300] version ??? to /Users/lsacco/Library/Logs/DiagnosticReports/com.apple.dt.instruments.dtarbiter_2016-05-18-100044_lsacco-mac.crash
The crash file simply had this:
Process: com.apple.dt.instruments.dtarbiter [6300]
Path: /private/var/run/*/com.apple.dt.instruments.dtarbiter
Identifier: com.apple.dt.instruments.dtarbiter
Version: ???
Code Type: X86-64 (Native)
Parent Process: ??? [1]
User ID: 0
Date/Time: 2016-05-18 10:00:44.332 -0700
OS Version: Mac OS X 10.11.5 (15F34)
Report Version: 11
Anonymous UUID: D0D71B50-8DA8-77BD-34D9-F97A39EE7F20
Sleep/Wake UUID: 1F71874E-C351-4020-AAF2-D5B9BE9992B9
Time Awake Since Boot: 5400 seconds
Time Since Wake: 2000 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: /usr/local/lib/libwep
Referenced from: /private/var/run/*/com.apple.dt.instruments.dtarbiter
Reason: no suitable image found. Did find:
/usr/local/lib/libwep: mmap() error 1 at address=0x10E599000, size=0x00008000 segment=__TEXT in Segment::map() mapping /usr/local/lib/libwep
Binary Images:
0x7fff6ccff000 - 0x7fff6cd3625f dyld (360.22) <A468D85E-D8D6-3461-8C99-49D3B9ACFC63> /usr/lib/dyld
0x7fff8721b000 - 0x7fff87586657 libobjc.A.dylib (680) <D55D5807-1FBE-32A5-9105-44D7AFE68C27> /usr/lib/libobjc.A.dylib
0x7fff92f8c000 - 0x7fff93402fff com.apple.CoreFoundation (6.9 - 1258.1) <943A1383-DA6A-3DC0-ABCD-D9AEB3D0D34D> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff93c2e000 - 0x7fff93f82fff com.apple.Foundation (6.9 - 1259) <71A9D3A0-0B1F-3E3A-86F3-1486365A6EF2> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff9cb24000 - 0x7fff9cb25ffb libSystem.B.dylib (1226.10.1) <C5D09FE1-CC70-383E-AC27-18602F2EDEC4> /usr/lib/libSystem.B.dylib
This post references several fixes relating to restarting and cleaning different things but none worked for me. Any other ideas?
This turns out to be an issue with having WebSense installed by my IT department. It is known to inject libraries into other processes such as Simulator. Once removed, it was working again.
How to debug an assertion when building for Debug-iphoneos
I'm developing a SDK for iOS and i put some assert() in the code to help me catching the bugs. It's working great when using the simulator but if I build my App (Debug-iphoneos) on a device, unplug it from my mac and leave it for testing, the crash log I get from an assertion failure is impossible to understand. real sample from a basic nil assertion failure: Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000001, 0x00000000e7ffdefe Triggered by Thread: 0 Filtered syslog: None found Global Trace Buffer (reverse chronological seconds): 10.153264 CFNetwork 0x0000000021bb897d TCP Conn 0x14dbd8c0 complete. fd: 9, err: 0 10.154690 CFNetwork 0x0000000021bb9a7f TCP Conn 0x14dbd8c0 event 1. err: 0 10.288093 CFNetwork 0x0000000021bb9afd TCP Conn 0x14dbd8c0 started 10.293561 CFNetwork 0x0000000021bff26f Creating default cookie storage with default identifier 10.293562 CFNetwork 0x0000000021bff24b Faulting in CFHTTPCookieStorage singleton 10.293562 CFNetwork 0x0000000021c418f7 Faulting in NSHTTPCookieStorage singleton 10.514965 CFNetwork 0x0000000021bb897d TCP Conn 0x14d88140 complete. fd: 4, err: 0 10.514965 CFNetwork 0x0000000021bb9a7f TCP Conn 0x14d88140 event 1. err: 0 10.789507 CFNetwork 0x0000000021bb9afd TCP Conn 0x14d88140 started Thread 0 name: Dispatch queue: com.apple.main-thread Thread 0 Crashed: 0 libswiftCore.dylib 0x00509e10 0x3af000 + 1420816 1 MyFramework 0x002ddfec 0x24f000 + 585708 Any chance I can get more information from the crash log ? I tried atos -arch armv7 -o MyApp.app/MyApp 0x24f000 without any success (returning 0x24f000)
Solved with this post Atos does not symbolicate system frameworks/libraries properly here I had to extract my framework from the .app and do xcrun atos -arch armv7 -o MyFramework.framework/MyFramework -l 0x24f000 0x002ddfec (notice the reverse order of memory adresses)
Failed to upgrade the iOS application while app is doing network operations using sockets
When I am trying to update the application using iTunes, I am getting a error pop-up - Unable to download application. I am running into this error only when my app is doing network operations using sockets. In other scenarios where app is either not running or is idle, it works correctly. From the console logs, I got following error message - 2013-04-18 10:11:39 AM GMT+07:00 backboardd <Warning>: pid_suspend failed for [7104]: Unknown error: -1, Unknown error: -1 2013-04-18 10:11:39 AM GMT+07:00 backboardd <Warning>: Could not set priority of [7104] to 4096, priority: No such process 2013-04-18 10:11:39 AM GMT+07:00 backboardd <Warning>: Application 'UIKitApplication:com.avaya.AVSIPiPhoneCFE[0xe6ed]' exited abnormally with signal 9: Killed: 9 Any idea why this would happen?
This question addresses a similar problem. In short, iOS automatically restarts an app that crashes or exits abnormally, if it has a background execution flag set. It seems that this leads to iTunes being unable to overwrite the old binary with the new one, because it's still running.