Android eclipse run program causes Installation error: 0 - android

I have an Android application. In the latest version I've moved some code from it into separate Android Library projects (two). One library depends on another and project depends on both libraries. So, as I understand, one library includes into final application "twice" (or something similar to twice).
On the first launch of application I receive following in Console (I am using Eclipse):
Installation error: 0
Please check logcat output for more details.
Launch canceled!
Can anybody help?
Thanks!
EDIT
On the second launch program starts normally.
EDIT
I tried to reproduce error on the emulator and other device, it didn't reproduce! Can a problem be on my device? May be on file not deleted or something else?

I've reinstalled Android on my phone and problem solved :) Not a good solution, but works.

Related

confusion on an error in Android studio

Recently i made an app for android through android studio, a very simple app.
But when i started the emulator to test the app i received an unusual error.
This is what the error looks like in a general form :-
WARNING:./android/base/files/IniFile.cpp:155:Failed to process .ini file C:\Users\xxxxxxx.android\avd\Nexus_5_API_23.ini for reading.
My question is,
1) What is the meaning of this error ?
2) And how do i solve this error ?
Have you recently updated the SDK tools. It sounds like it might be some compatibility issue with the tools and the emulator. Try going into the AVD manager and see if there is an update, and/or delete the emulator and re-create and see if that solves the issue.

Android IntelliJ IDEA 14.1: No main class for module

I previously had a working android project when I was using IntelliJ IDEA 14. I could run the project by pressing the play button, and it would install and start the application on my device.
I recently updated to 14.1. The code still appears to compile fine, I can see that it generates an APK and I can view it in the output folder (out/production/myapp/myapp.apk), but now I get an error when I attempt to run the project:
Error:No main class for module: app
I've tried creating two new projects, one based on the Android->Application Module template and another based on the Android->Gradle: Application Module template, and both have the same issue - they spit out the error above with the default configuration.
I assume that this must work on other users boxes, particularly because I haven't found anything online or any bug reports about it, but I guess there is a very minute possibility that I'm the first one to find this.
Is this an issue with IntelliJ IDEA 14.1 or just my box? Any ideas on how to fix it or where to start would be greatly appreciated.
I was having similar issue.
Do you have haxe plugin installed? Try to uninstall and try after that and it should work.

android studio "Activity class does not exist"

After importing my eclipse android app into android studio(Importing Non-Android-Studio project), I've tried to run the app on my phone.
No I'm facing:
Error type 3
Error: Activity class {com.abc.appname/com.abc.appname.MainActivity} does not exist.
I've searched and I've read every single article about this topic but couldn't resolve my problem.
Somehow android studio tries to find my package inside the package.
I've specified the launch activity in the run configuration by going trough the projects directory.
If I specify only the activity name as MainActivity it doesn't works because it request the whole package path.
The other stuff as modules and so on was autogenereted, but I couldn't find anything usefull in there.
Thanks in advance.
Same Problem for me was solved by lowering Compiling SDK from "M preview" to API 22 in Project Structure.
But first try uninstalling app in the emulator or device you are using.
I've also seen this when the app was already installed, but under a Work Profile. Deleting the app from the Work Profile first fixed it.

Unity Android Debugging Tips

Today I finally managed to build my first android application in Unity. It works nice in the editor but it doesn't work on some real android devices so I used adb logcat to try to find the root of the problem. Here is the log: http://pastebin.com/uHAE3BTb.
I'm rather noobish in Unity, don't really know android java specific functions, I'm quite fond of debugging and I don't know where to start so I need your help for this one.
How do I find where my app fails from adb logcat? Is it possible or should I start commenting lines of code, rebuild and see if it fails every time? Is there another way of doing this?
You just have to be smart about reading the logs. This (I'm sure you know this already though) is the problem:
E/AndroidRuntime( 4994): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.Vali.Atomic/com.unity3d.player.UnityPlayerNativeActivity}: java.lang.IllegalArgumentException: Unable to find native library: main
Looks to me like Unity is not building it's jar file correctly for you. Ensure the android sdk is installed correctly and properly setup within Unity. Also, ensure that the 32 bit version of JDK is also installed and is being used by Unity when compiling

Application crashes in emulator when loading native shared library, but works fine on a physical device

The header pretty much explains the issue. I'm getting "Unsatisfied link error" on emulator. What could be the cause and what are the possible solutions?
Some time ago, when we started developing the app, it did work fine on emulator, and one day just stopped. It happened on at least two independent machines.
Ideas, anyone?..
Update: created a new emulator - same thing.
Problem solved! it appears, Android QUEMU emulator only supports ARM5 (APP_ABI:=armeabi), and my library was compiled with armeabi-v7a.
Update: the problem no longer exists.
You should check the following :
Using adb shell go in to the sys/lib/ folder and check if your library was copied there
Did you change the package of your class or did some refactoring? If you did and didn't updated the .cpp file this is causing the unsatisfied link error.
You can also try to manually load your library using System.loadLibrary("myLib");
You could also try to create a new emulator, maybe it got messed some how. Happens a lot.

Categories

Resources