I changed something in my code (I'm not sure what), and now I get the following warning every time I run the emulator.
Database Inspector
For security reasons offline mode is disabled when the process being
inspected does not correspond to the project open in studio or when the
project has been generated from a prebuilt apk.
I haven't touched my gradle, nor built an APK. The only other thing that I can think of is that Android Emulator updated to 30.6.5 this morning, but I didn't have this occurring until around lunchtime. What does this actually mean, what might be causing it, and how can I make it go away?
Open "Database Inspector" window, click on the device name, and in drop-menu turn-off process.
I have written an Android app using Eclipse Mars. I would like to test it on Nexus 5X and Nexus 6P Emulators. These devices are not listed in the 'create AVD' dialog's drop-down list.
I tried the 'device' tab and entered the size and other parameters of the device. The 'create device' button was enabled, but nothing happened when I clicked it. I have tried it several times now, waited for half an hour after clicking, tried it on a different computer, but nothing happens. Any suggestions?
It's a bug in AVD Manager, you should look for an update to arrive and hope that it is solved.
I think Eclipse AVD throws a tantrum if there's a space in the name.
Does the new name you put for your AVD have a space? Remove that and I think you should be good.
See how my device's name doesn't have a space?
When I press Run on Xcode with other tasks already running, the following message appears:
Simulator in Use.
The Simulator can't be launched because it is already in use.
I checked with some friends and when they press run, Xcode automatically stop the tasks running and run the app you want. How can I configure this here?
Thanks in advance,
Quit the simulator and try again. if not working quit the Xcode and try again.
If you have two projects open in Xcode and one is running on the simulator, you can't run the other. Go through each project window and see if any are running, and if they are, press the "Stop" button on the top left:
In most cases Josh answer solves this problem. But just now happened to me to have only one project in Xcode and trying to clean and built it did nothing.
For me (this time) the solution was to:
Right click the simulator from dock and click Quit.
I did the same for Xcode (right click on Xcode in Dock and clicked Quit).
After that just re-open Xcode and voila!
It works!!!
If the issue is you have multiple projects open and running into Simulator conflicts, someone created a little Automator script that closes the current simulator and starts the next one. Kind of a work around but might work for you.
Check out the detailed answer here.
The over attached debugger syndrome
This happens to me when I switch simulator type (ios version or device type) without pressing the stop button (application was still running on it). To fix this, switch back to the old one (if you remember witch it was :P), run then stop the application, switch to the desired simulator configuration, run, tadaaaa: the error is gone.
This can also happen if you have two projects and one is running, and you try to run the other one. The solution is to stop the other one before starting the desired one.
This ca also happen if you had some kind of crazy bug and the simulator is unresponsive, in this case the debugger remains attached, crying over it's beloved simulator. You have to close the xcode simulator and sometimes restart for this one.
I have the latest xcode version at this time and got fustrated for a while. Now I'm free from restarting the simulator, xcode, coputer, router, going to sleep and waking up the next morning... :D
Hope this helps you guys apple has a lot of weird unclassified exceptions in xcode. They could least say that the debugger is still atached to something in the memory, we are programers not ordinary users, the more errors you give us the better we understand how to avoid them.
My personal favorite si when xcode puts absolute paths to your newly added famework that go nuts triing to find out why it doesn't work on an other computer (The project in wonderland syndrome).
(and rant rant rant irony rant.. you get the idea)
Quit the xcode and simulator ,and try to restart your mac
Quit the simulator and try again.
Your mac might be opening iPhone Simulator automatically, In order to stop this you can run Terminal, OSX's version of command prompt, by navigating to ~/Applications/Terminal.app
from there you can run these commands.
top -u This command shows the mac's processes, and some information about them, from there you can see whether iPhone Simulator might be open.
sudo killall iPhone\ Simulator Deconstructing this command for you, sudo puts you into superuser mode, by having you enter your login password, killall : This command kills all processes by the name specified. iPhone\ Simulator: This being the name of the app, and in order to have a space requires the \ (space) before the second word. By running this command you will kill all processes called iPhone Simulator.
If this doesn't help, then try rebooting.
If rebooting doesn't help try re-installing XCode.
If re-installing XCode doesn't help, then try re-installing your Operating System entirely.
Good Luck!
There are three solutions for this issue:
Right click the simulator on the Doc, quit and then re-run the application from the Xcode.
If this did not work, then -
Save your code, Right click the Xcode, restart the Xcode with your project and then run again. Remember to select simulator instead of device in the target.
If this also did not work, then,
Force Close - Simulator/Xcode - Restart your mac and then run Xcode again.
Most likely - the first step would be enough!!!
To get the simulator to stop whatever is running you need to check off the box "Do not show this message again".
Example:
And then click the box.
And then you can run the simulator even if a program had already been running.
I've been having this issue as well, but for me the problem doesn't have to do with XCode or Simulator.
The problem was in my code. A process was making the CPU run at 100%, and fixing the bug in my code fixed the simulator problem.
Force Quit both, iOS Simulator and Xcode, then reopen Xcode and run project.
Two Possibilities.
1)just quit the simulator,and run the application you want to run
2)just stop the application that using the simulator and run the application you want to run
Try these steps in increasing order of persistence of the problem:
Quit the Simulator.
Clean the project, Reset Simulator, Delete 'Derived Data'.
If nothing works, Force Quit Xcode and Simulator from the Mac Menu.
Force Quitting Xcode seems to always work for me.
It was one sticky Xcode bug indeed. Now it's solved, happy coding!
Solution: Why is Eclipse's Android Device Chooser not showing my Android device?
THis is getting annoying. My device shows up in eclipse on all
platforms.. Except when I am on my Ubuntu laptop.. when I "run
configurations" with it set to Manual.. I can see that there is an
Emmulator running that I can Install the App to.
Problem is, the Emulator is a pile of horse crap when it comes to
testing on real devices like my Samsung Captivate.
When the Captivate is plugged in via USB.. it shows via ICON, except
the ID is set to ??????????? and nothing else seems to be registering.
I can highlight it, but I can't launch it.
The captivate I am using is Rooted and running the LagFix Kernal..
However this has never hindered me on Windows or OSX.
Help.. I am trying to go completely Linux.. if it kills me.
See screenshot below: http://img265.imageshack.us/i/sdkbugeclipse.png/
UPDATE: Device is showing in the manager even when not connected?!?!
This has to be some weird Eclipse bug.. PLEASE HELP!
Solution (in case you missed my edit) need to add the correct Samsung Device ID when using the SDK with Ubuntu: link
I am having trouble launching Time Profiler in Xcode, both for Mac Applications and iPhone apps.
The steps I have tried are opening Time Profiler, Clicking the choose target drop down box, selecting my iPhone or Mac book. Choose target -> myApp. If I choose a Mac app then I hit the record button a big yellow warning pops up accross the window saying unable to configure sampling trigger for x. If I choose an iPod app then the record button stays greyed out and cannot be clicked.
Any ideas what I'm doing wrong here?
Have you tried starting Instruments via (in Xcode) Run -> Run with Performance Tool -> Time Profiler? That may help set up Instruments and get you running v. launching Instruments manually.
Also, I have had trouble in the past where the SDK used to build the iPhone app differed from that which Instruments was expecting. Check out the Instruments documentation on how to explicitly tell it which version of the iOS you are running to perform the benchmarking.
Sometimes Time profiler is greyed out because you dont have application install on simulator...if you have application installed on simulator and then you try Run with Performance Tool it shows Time profiler enabled.