So I'm learning about updateApplicationContext the hard way here (mostly due to the fact that there it's extremely hard to debug what's happening on my phone app while running the watch app). The problem I have is this: If I say the following, I get regular updates:try self.session.updateApplicationContext([MessageKey.LocationCount.rawValue: String(self.receivedLocationCount)])(straight out of potloc)If however I try this, I get no updates. I assume something has crashed but there are no logs to let me know://currentLocation is a CLLocation try self.session.updateApplicationContext([MessageKey.LocationCount.rawValue: currentLocation])My understanding is that I should be able to pass any object to updateApplicationContext, but passing a CLLocation seems to break it, whereas passing a String is fine. Interestingly if I do this, the call does in fact work (though I don't get what I want on the other end, as I want a CLLocation object):try self.session.updateApplicationContext([MessageKey.LocationCount.r
Search results for
LLDB crash
29,559 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Had my app rejected because it crashed on these devices (essentially all) - iPhone 4S running iOS 8.3- iPhone 5C running iOS 8.3- iPhone 5S running iOS 8.3- iPhone 6 running iOS 8.3- iPhone 6 Plus running iOS 8.3- iPod Touch Fifth Generation running iOS 8.3.This is puzzling because I literally spent 4 hours creating all kinds of explicit App IDs and Provisioning Distribution Profiles for my app, embedded framework, and an action extension (because Automatic provisioning NEVER worked) to finally get the app to archived, validated, and successfully submitted. After I received the notice I reinstalled the app on my 5S with 8.3 and several of the simulators for the above devices, and they all work perfectly.The attached crash log was not helpful (to me at least - more of it follows below):Exception Type: EXC_CRASH (SIGABRT)Exception Codes: 0x0000000000000000, 0x0000000000000000I tried to follow the directions for creating an Ad Hoc ipa to be installed with iTunes (and not Xcode). The instruction
If you symbolicate that crash log it may provide more useful info. The line10 MYAPP 0x0000000100011ab0 0x100008000 + 39600should point to a line in your code to start looking. The fact that the previous stack frame was StoreKit is interesting. Perhaps your IAP product identifiers are coming back invalid or something, and your code doesn't handle it. Again, if you symbolicate that log you can tell what that callback was.
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
Lot's of great things coming out of WWDC, but here we are in 2015 and I feel like little has changed since the launch of iTunes connect. What's the deal apple? We both know there are plenty solutions to this problem. I'm trying to understand the resistance, because it definitely has nothing to do with security, and keeping the ecosystem safe. I've had apps that crashed on launch get pushed through, so we're definitely not talking about quality control here.The only reason I can come up with is that Apple knows/thinks that update velocity is detrimental to the end user, and app reviews are politically easier to implement. Did your app reviewers join some powerful union? Or maybe the internal team is overselling the value of app reviews up the chain of command? It doesn't even make sense. You're telling me if a developer who has had >5 submissions to the app store without prior problems has to wait 12 days to improve their software? You tell us “write quality code” yet you don’t even allow us to tes
I'm not 100% sure what's going on here but it looks like you have a problem with the matching dictionary in your KEXT that's causing the kernel's PCI bridge matching code to crash.Here's a semi-symbolicated section of the top of the stack during the crash.1 mach_kernel 0xffffff800cd2bda1 2 mach_kernel 0xffffff800ce17cc2 3 mach_kernel 0xffffff800ce34b73 4 mach_kernel 0xffffff800d311a93 5 com.apple.iokit.IOPCIFamily 0xffffff7f8d52c471 IOPCIBridge::matchKeys(...) 6 com.apple.iokit.IOPCIFamily 0xffffff7f8d52c556 IOPCIBridge::pciMatchNub(...) 7 com.apple.iokit.IOPCIFamily 0xffffff7f8d52c5ba IOPCIBridge::matchNubWithPropertyTable(...) ...Frame 5 is the critical one. This looks like the first call to strtoul in IOPCIBridge::matchKeys in the following file.<http://www.opensource.apple.com/source/IOPCIFamily/IOPCIFamily-239.1.2/IOPCIBridge.cpp>btw You might want to look at TN2063 Understanding and Debugging Kernel Panics.<https://developer.apple.com/library/mac/technotes/tn2063/_index.html#//apple_re
Topic:
App & System Services
SubTopic:
Core OS
Tags:
What is the crash message?
Topic:
Graphics & Games
SubTopic:
General
Tags:
The crash is below. Just to reiterate I have not modified the code in anyway. All I did was take Apple's autogenerated Metal code for their game application. I added another view in the nib and linked it to a new view controller. If I remove the second view it works fine.AMDMTLBronzeDriver`amdMtlBronzeCmdBufAddInternalResource(BronzeCmdBufInfoRec*, MTLIOAccelResource*) + 16, name = 'CVDisplayLink', stop reason = EXC_BAD_ACCESS (code=1, address=0x10) frame #0: 0x000000010271c8f5 AMDMTLBronzeDriver`amdMtlBronzeCmdBufAddInternalResource(BronzeCmdBufInfoRec*, MTLIOAccelResource*) + 16 frame #1: 0x00000001026dc555 AMDMTLBronzeDriver`BltMgrBase::AddHandle(ContextStatus*, void*, unsigned int, _VCOP_RESOURCE_TYPE, unsigned int, unsigned int, _UBM_ADDHANDLE_INPUT_FLAGS) + 101 frame #2: 0x00000001026fd1f5 AMDMTLBronzeDriver`SiBltDrawRegs::SetupAndWriteDepth(BltInfo const*) + 1013 frame #3: 0x0000000102702bef AMDMTLBronzeDriver`SiBltMgr::SetupAndWriteDrawBltSurfInfo(BltInfo*) + 63 frame #4: 0x0000000102705788 A
Topic:
Graphics & Games
SubTopic:
General
Tags:
Thanks. I finally figured out how to symbolicate the crash log by using Google since the links provided by the Review Team was from 2012 (https://developer.apple.com/library/ios/#technotes/tn2008/tn2151.html) and was not updated to Xcode 6 (or probably 5), did not mention I had to rename the crash log attached from the Review Team, that I had to connect my device, go to Organizer, view Device Logs, drag & drop, etc. (Filed a radar #21483079).Anyway, yes, the problem occurred with a custom object that handles the Store. I had this exact same error during development when for some reason iTunes Connect did not recognize my one upgrade product and so there were zero objects in the response from the store and trying to do anything with the response array crashed. I had to delete the test Sandbox user I was using and create a new one (for some reason) and eventually the store returned the one product and everything worked.I would *assume* that the Review Team would have to sign in wi
Topic:
App Store Distribution & Marketing
SubTopic:
App Review
Tags:
I submitted an app with a single non-consumable IAP upgrade. It crashed all the Review Teams devices (but works wonderfully on my devices).After I symbolicated the crash log (from the Review) the app crashed for them when my singleton Store handler (added as the Store observer in App Delegate didFinishLaunching) called requestStoreProductList (from my main view controller) and the delegate method productsRequest: didReceiveResponse: was called (in the custom object) but the response.products array was empty and when I tried to do anything with the array (e.g. objectAtIndex:0) the app crashes.This happened to me during development as I had put the wrong identifier in iTunes Connect, but that was corrected, but then my test Sandbox user still wouldn't recognize the change and the failed delegate method showed the corrected identifier as invalid. So, I deleted that test user and created a new one, and then everything worked (the product was returned). And it has worked for me ever sinc
I've been trying to run with Xcode 7's address sanitizer, and I'm having trouble understanding the problem flagged here. It looks to me like a problem inside of the newly annotated `vector::__swap_out_circular_buffer` at the end of a `push_back` operation.It's dying inside the allocation on line 4 just after `__annotate_delete()`.vector<_Tp, _Allocator>::__swap_out_circular_buffer(__split_buffer<value_type, allocator_type&>& __v) { __annotate_delete(); __alloc_traits::__construct_backward(this->__alloc(), this->__begin_, this->__end_, __v.__begin_); _VSTD::swap(this->__begin_, __v.__begin_); _VSTD::swap(this->__end_, __v.__end_); _VSTD::swap(this->__end_cap(), __v.__end_cap()); __v.__first_ = __v.__begin_; __annotate_new(size()); __invalidate_all_iterators(); }Here's the full error report.AddressSanitizer debugger support is active. Memory error breakpoint has been installed and you can now use the 'memory history' command. ================================================
running apple pay on xcode 7 and getting PassbookUIService quit unexpectedly.Process: PassbookUIService [60296]Path: /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator.sdk/Applications/PassbookUIService.app/PassbookUIServiceIdentifier: PassbookUIServiceVersion: 1.0 (1.0)Code Type: X86-64 (Native)Parent Process: launchd_sim [60138]Responsible: launchd_sim [60138]....Application Specific Information:*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSPlaceholderSet initWithObjects:count:]: attempt to insert nil object from objects[0]'terminating with uncaught exception of type NSExceptionabort() calledCoreSimulator 159 - Device: iPhone 6 - Runtime: iOS 9.0 (13A4254u) - DeviceType: iPhone 6
Just a quick follow-up to myself- this seems to be caused by latest Outlook Preview beta 15.11.Downgraded to 15.10 and everything works again.. Amazing that Outlook can crash the L2TP tunnel. Michael
Topic:
App & System Services
SubTopic:
Core OS
Tags:
When attempting to run an iOS 7 simulator from Xcode 6.3.2 (6D2105) I get the attached stack trace ever time when attempting to boot the simualtor.I've attempted to reinstall the iOS 7 simulator without any success, any ideas?Process: launchd_sim [1634] Path: /Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 7.1.simruntime/Contents/Resources/RuntimeRoot/usr/libexec/launchd_sim Identifier: launchd_sim Version: ??? Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: launchd_sim [1634] User ID: 501 Date/Time: 2015-06-22 11:53:02.396 -0400 OS Version: Mac OS X 10.11 (15A178w) Report Version: 11 Anonymous UUID: 31654C6B-0954-14CB-B651-0DE173746046 Time Awake Since Boot: 260 seconds 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_FALLBACK_LIBRARY_PATH=/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 7.1.s
I'm trying to profile an iOS app in Xcode 6.3, but I'm stopped by the error message:The document Activity Monitor.tracetemplate could not be opened.Repro Steps:1. In the menu bar, click Xcode, Open Developer Tool, Instruments2. The Choose Profiling Template window appears. Select Activity Monitor,3. Import Trace open dialog appears. Select Activity Monitor.tracetemplate4. The document “Activity Monitor.tracetemplate” could not be opened. popup appears.This occurs no matter what instrument I select.Alternatively if I go to the Instruments Preferences and select Supress template chooser I can open up instruments but when I try to drag on Activity Monitor I get a crash with the following error in the crash log:Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Application Specific Information: Assertion failed: (_coreSpace != nil), function -[XRTrace coreSpace], file /SourceCache/Instruments/Instrum
Install App w/Xcode 7ß, crashes iPhone w/iOS9ßIf I install my app with Xcode 7 to my iPhone 6+ w/iOS9 the phone freeze. I have to reboot (the iPhone), and then the App works, but I have had to reboot my phone like 15 times.This *****!I have tried quitting Xcode and being delicate unplugging and re-plugging, etc, it's annoying. Especially because I was working on debugging a networking issued, i.e. Simulator connected to iPhone.I finally fixed my bug, but not the install crash bug, oh and I tried with other Apps, I have written. They crash the iPhone as well.Well I guess I have to wait till the ß2 everyone has started talking about.Can anyone else confirm tho that they are experiencing similar install behavior?Thanks that's all I ask.