Unfortunately App has stopped but colud not find the logcat - android-studio-3.0

logcat
Unfortunately app has stopped. When i checked the logcat there is no information displayed related to this issue. how i could fix this. please help me

Related

Xcode debugger not giving any output

I have a stumper. How can I get my Xcode debugger to provide an output under the following circumstances?
I tried restarting my iMac. I tried restarting Xcode. I tried restarting my simulator.
I am looking at the proper debugger panel:
I have tried "activating the debugger."
I do have code that should produce an output as well.
The app does run in the simulator.
No crash report or popover warningis provided.
Just tried running on a device. This is a partial answer/fix. The debugger works when running on the device.

IOS 9 App Freeze(Button no response) with “BKSendHIDEvent” error in Ionic

I have read some articles like app freeze with BKSendHIDEvent error:
iOS 9 App freeze with console log "BKSendHIDEvent", but my problem is slightly different from this one. Since I use ionic to build the ios app, I don't know how to trouble shoot the detailed error in xCode.
My problem is that when the app first runs within the xcode, everything works fine, but if I stop the debug and reopen the app from the simulator, no button responses at all. The whole app stucks at this stage.
I checked the simulator system log, it shows this:
BTW, when I kill the app(flick up the app) while it is still debugging, the xcode says this, I don't know if this was the issue:
I have also tried to get further information from the web inspector, but this does not response either. I could not reload the page by
window.location.reload();
There are no window object at all...:
So I'm totally lost here. I don't know how to further trouble shoot this error. Can anyone please point me to a correct direction? I have no idea why the web inspector shows nothing here and how to get the detailed error info in xCode.
Thanks in advance!
After several search, here is the fix:
App Freeze
But I still do not know how to trouble shoot, in the issues above, they mentioned race condition, how to debug this?

Xcode not showing logs after exiting the app and come back

I'm using Xcode 6.1 and running an app on the Simulator. When the app exits by double-tap home button, no logs show any more from Xcode console when I come back to the app. Anyone knows what's going on. Appreciate
You need to launch (run) the app from Xcode into the simulator in order to get Xcode's debugger to attach and stream the simulator's console output into the debugger window.
You can also view the Simulator console output by looking at a system log file, details for which can be found in this related question.

Error launching remote program: launch or suspend in progress

I'm suddenly getting this error when launching my app on an actual device but not on the simulator, where it appears to run fine.
I've tried deleting the app from the iPad. I've also tried clearing out ~/Library/Developer/Xcode/DerivedData as suggested in questions on here for similar (but not identical) error messages.
Anyone have any other ideas?
When I've had this its normally because the iPad's locked up (and not because of anything on my Mac). Have you tried rebooting the iPad by holding the power and home buttons?
It's probably happening because you interrupt a build that's going on. To fix it, clean your project and re-run it. If your device is still stuck, then do a hard reboot.

problem loading blackberry application on playbook

i successfully created the .bar file and deployed in playbook simulator. i could see the icon of my application in the playbook simulator but when i click to open the application in playbook simulator it show a loading screen with white background and after a moment the player freezes without and error or warning. Did anyone faced the same problem and resolved the issue???? Please reply if anyone got the solution
That's an inadequate description of the problem. The "player freezes"... where? On the loading screen? After your main class displays? Between the two somehow?
Also, you can compile with debug mode enabled and deploy while running the debugger. Then you're very likely to see a traceback showing the specific error, instead of whatever this "freeze" is showing you.

Resources