In my iOS app crash log I found this statement:
HW kbd Failed to set (null) as keyboard focus ios
Does anyone know what is this and how to resolve it?
I've just encountered this exception running a Xamarin app on the simulator. It started occurring after I toggled the software keyboard off while debugging the app. Given the exception mentioning the keyboard I think that's what caused it.
Uninstalling the app from the emulator, cleaning and rebuilding fixed the issue for me.
Unsure if this bug is on Apple's side or Xamarin's.
The only references I could find related to Xamarin was close, but the inverse of this - the app crashing on the simulator, but working on an actual device. The resolution in that forum post doesn't describe what the problem might be, but does suggest that cleaning the project and rebuilding may resolve it.
The specific message HW kbd Failed to set (null) as keyboard focus ios is related to the app crashing, but there's no additional information in the pastebin to really help pin down why it's crashing.
You might also consider adding logging statements in your code to see if you can isolate the issue.
Related
Since today I can't run a CN1 debug the app on my iPhone 4 (iOS 9.3.5). It crashes on startup.
I've made only minor changes:
Add a button which uses execute(URL) to open a URL.
and I've got this exception:
Library not loaded
/System/Library/Frameworks/UserNorifications.framework/UserNotifications
[...]
Reason: image not found.
Can you help me, please?
That's probably a regression due to changes that went in to implement https://github.com/codenameone/CodenameOne/issues/2208
It's probably due to this commit: https://github.com/codenameone/CodenameOne/commit/a3a70fadd7dbef661351d11dc35683be3d828eda
Can you please file an issue to keep track on this?
We're looking into it.
After working just fine on both iPhone and iPad for a month, my Xcode 9 app has consistently started crashing causing me the following fatal problem: When I build & run it on an iPhone (simulator or device) Xcode completes loading the app and then crashes too fast for me to copy/paste the error from the debugger. When I run on iPad it works fine leading me to believe this is a result of something related to the split master/detail view.
If I use either an exception breakpoint or an "all C++ exceptions" it will stop at the AppDelegate class and crash if I hit play. If I use only an "all Objective-C exceptions" it will crash as before.
In the debug view hierarchy I get the following errors as well:
Error: Unable to capture view hierarchy.
Details: Log Title: Data source expression execution failure.
Log Details: error evaluating expression “(id)
[[(Class)objc_getClass("DBGTargetHub") sharedHub]
performRequestWithRequestInBase64:#"...
Log Method: -[DBGDataSourceConnectionLibViewDebugger
_executeLLDBExpression:forRequest:onPotentialThread:iteration:]
_block_invoke_2
Method: -[DBGViewDebugger updateDebugHierarchy]_block_invoke_2
I have tested other apps and this issue is unique to the app I am working on. Any ideas or debugging tips for how to proceed? I might just have to redo this whole project again if I can't even find the root cause of this! Appreciate any help.
Quick solution: Reset Simulator Device
I managed to resolve the above issue thanks to some serious digging. First, to resolve the instantaneous crash problem, I set a breakpoint at every line in the app delegate. That allowed me to narrow the error to a memory handling problem. From there I started running the code on one of each device available, and realized the crash only occurred on devices I had used earlier in development. Resetting those devices solved the problem.
The core issue here is that when you clean/rebuild your xcode program, it updates the app code on the device, but not necessarily the data model information. So when I changed my data model by including new data and renaming old data it was not properly updated.
Many crashes happened below the iOS9.3 (which means devices with iOS10 are OK)..
The crash logs seem to show that it's not a problem about API that can only be used below iOS 9.3 .
But I have no idea about the crash logs. ( I'm sorry ...for I just start to study iOS development for only 2 month )
Could you please help me analyze the crash logs ?
Really Thanks !
crash log 1
crash log 2
AXE_BAD_ACCESS - this is problem with memory. One of function tried to use variable which already released. I think you need to check use your TableView and cells for this table.
Also to find problem with memory you can try to use zombies
Used to have the similar strange crashes in my app. And only in production, when testing from TestFlight. Building on device with ios 9 caused no problems.
Maybe it sounds strange, but try to convert all images you use in app to images with included sRGB color profile. For me it helped.
I'm working on an iOS app and it load images from an URL like this image it is working perfectly on all the test devices in my office(and on simulator as well). but client said that the app is crashing whenever any image comes, everything else working as expected.
Now the question is if there is any problem than how it is working on my side? Is there any way(any app or anything) by using them client can send crash report to me so i can check?
Note:- we are testing on the same iOS version(7.x)
EDIT:- Some how they get the log and send to me from that i got
May 20 22:48:47 iPhone-5S com.apple.launchd[1] (UIKitApplication:com.Ba-cha[0xfbd1][287]) <Warning>: (UIKitApplication:com.Ba-cha[0xfbd1]) Job appears to have crashed: Segmentation fault: 11
May 20 22:48:47 iPhone-5S backboardd[31] <Warning>: Application 'UIKitApplication:com.Ba-cha[0xfbd1]' exited abnormally with signal 11: Segmentation fault: 11
I searched for the same and tried NSZombieEnabled but in my device (iPhone 4 and iPhone5) it is working perfectly no log? And now the question is How can i reproduce the issue on my device?
This is hit and try solution(at least worked for me):- My app Was worked fine on iPhone4 and 5(32 bit) but crash on iPhone 5s i.e. 64 bit processor. From some research on stackoverflow and Apple official i come to know perhaps there may be some problem in conversion between NSInteger to int. so i use NSInteger every where instead int.
Also i'v to remove armv64 from my project and set NO for "Build Active Architecture Only" (debug and release)
That did the trick for me, I didn't really need any 64bit specific functionality on my app so I took it out. I know this is a hack and not a good solution but at least it works.
As Adam suggested, iTunes would work but it may be better to save your client the chore...
You could alternatively send them a new version of the app using something like HockeyApp or TestFlight (free) integrated, allowing you to automatically receive the crash logs as well as the wide range of other useful tools they provide such as easier installation by the client.
They can load Xcode, and connect the device. Device logs can be viewed in the Organizer window. Crashes are marked as such. The log text can be cut and pasted or the export button can just save the whole thing as text.
Crashlytics offers software and service to upload crash logs.
It is possible to build up the information that appears in a crash log, but you will need unix signal handlers, various exceptions handlers, and a server to upload to.
Segmentation fault 11 means memory allocation issue. You possibly have made a coding issue like: using weak/assign, instead strong on NSObject
I have an app I'm developing where setting a breakpoint in Xcode while the app is running causes it to crash. At least I assume it is a crash. There is nothing in the console saying what happened. The app just terminates.
Note that the break point is not being hit, just the act of setting it causes this.
I've developed many apps and this is the first to act like this. Does anyone have any ideas what could be happening or how to figure this out? It is really slowing down my debugging.
I'm assuming you're using Xcode 4.x. Try going into your scheme's settings and switch to a different debugger (GDB if you have LLDB currently set, or vice versa).
If that doesn't work, we need more info:
which version of Xcode and iOS are you using?
does the problem occur in the Simulator or on your device, or both?
have you tried placing a breakpoint in different places in your code?
As far as I can tell, it's a debugger issue. So your app does not actually crash, it's the debug session that crashes which causes the app to terminate. You can observe a similar effect when you hit Stop in Xcode or disconnect your device while an app is attached to the debugger in Xcode.
Might be an issue with mismatching Xcode and iOS versions. Please provide more info about your environment to help diagnose the problem.