![android emulator mac stackoverflow android emulator mac stackoverflow](https://miro.medium.com/max/6300/1*v8bwLdxBe4IF5ruvZlq3jQ.jpeg)
- #Android emulator mac stackoverflow apk
- #Android emulator mac stackoverflow install
- #Android emulator mac stackoverflow update
If I create a new one and I launch it it works until I close it, then I have to restart the Mac and create a new device. I moved to IntelliJ and I'm able to launch AVD manager but none of the "old" created devices work.
![android emulator mac stackoverflow android emulator mac stackoverflow](https://cdnk.c3dt.com/preview/5768740-bruno.stackrest.jpg)
#Android emulator mac stackoverflow install
Also it's not been able to download and install the m2e (maven to eclipse) plugin. After tweaking the memory limits on eclipse.ini file it throws random memory errors.
#Android emulator mac stackoverflow update
It used to work with the old AVD with some random crashes every now and then but since the last update to APi 17 it's a pain in the neck. Pkg: /data/local/tmp/ issue here, I'm running a mac mini with 8GB of RAM and MacOS Lion. Remote path: /data/local/tmp/ĭEVICE SHELL COMMAND: pm install -r "/data/local/tmp/" Local path: D:\dev\android-sdk-windows\samples\android-15\ApiDemos\out\production\ApiDemos\ApiDemos.apk
#Android emulator mac stackoverflow apk
Rebuild the project and run the tests, again, this time 2 separate apk files will be deployed, one for the main app and the second one for the tests, then tests will run: Waiting for device. Right now you need to correct it manually as shown on the screenshot:
![android emulator mac stackoverflow android emulator mac stackoverflow](https://i.stack.imgur.com/OTCWt.jpg)
Instead, the scope must be set to Provided and we'll fix it in the next update. By default IntelliJ IDEA sets the dependency scope for the application module inside test module to Compile, so that all the production and test classes get compiled into the single Test.apk. UPDATE: We did some research and found the source of the problem. Uninstall existing ApiDemos, then try to deploy and run ApiDemos from IntelliJ IDEA, then try to run the test configuration again. Verify that there is no pre-installed ApiDemos application in the emulator, or the signatures will not match. You can also try to restart adb with adb kill-server and start the emulator manually from AVD manager. Local path: D:\dev\android-sdk-windows\samples\android-15\ApiDemos\out\production\Tests\Tests.apk I've tried it with IDEA 11.0.1, 4.0.3 Android platform on Windows and it works fine: Waiting for device.
![android emulator mac stackoverflow android emulator mac stackoverflow](https://i.stack.imgur.com/TS113.png)
The only relevant thing I see in logcat is 01-21 16:36:22.047: WARN/ActivityManager(91): No content provider found for permission revoke: file:///data/local/tmp/.testsĬan you run normal apps in the emulator or USB device? Try to create the new emulator device and see if helps. Test running startedTest running failed: : device not found Installing .testsĭEVICE SHELL COMMAND: pm install -r "/data/local/tmp/.tests" Local path: /Users/rfzabick/IdeaProjects/ApiDemos/out/production/Tests/Tests.apk Users/rfzabick/android-sdk-mac_x86/tools/emulator -avd android4.0.3-api15 -netspeed full -netdelay none -wipe-data -no-boot-anim Users/rfzabick/android-sdk-mac_x86/tools/emulator -avd MyAvd0 -netspeed full -netdelay noneĪfter advice, I switched to android 4.0.3 (API 15). All I see in the output window in IntelliJ is Waiting for device. When I run tests, though, my emulator starts up, and then just sits there. I can run applications just fine in my emulator. Other tests, such as .view.Focus2AndroidTest, use android classes, and therefore need to run in the emulator, that is a problem. Some of the tests run as standard unit tests, no problem. I'm trying to run the sample unit tests for the sample code that ships with the android SDK.