I wanted to try and do some work with a module in trigger.io but seem to be running into some issues and the docs are well, not very good..
Anyhow I followed the step, the ones that were there anyhow and when I tried to run the project I'm getting an error message stateing
Running tests
Test running started
Test running failed: Unable to find instrumentation info for: ComponentInfo{io.trigger.forge.android.inspector/android.test.InstrumentationTestRunner}
Empty test suite.
I did not change anything just tried to import and run but no matter what I do I cant get it to work. Have looked all around but found nothing that would work so any help would be nice
Related
My Android Studio emulator is up and running yet when I run the code, I realize the emulator does not show the code I run.
I tried out some of the solutions like; Project Structure>Project and I chose the latest Android API there and then to Modules and did same thing, yet did not work.
Instead, after these changes, I got an error message saying IDE Error, that I should report the problem
How to understand what and why really happens behind Gradle: Build? There is no console or crashes, just endless building. Maybe there is network issue which happens again and again, but how can developer know it?
This is a sample of just new project:
From terminal everything works fine. So the question is not about how to solve particular problem, but more about generic solution when IDE doesn't show anything except "progress".
You can execute ./gradlew build manually in the terminal to see its logs. You can also add --debug or --stacktraceparameter to enable verbose logging.
I have a similar answer to Andre, but with a suggestion of some potential culprits.
If an issue is happening, Android Studio is just a GUI wrapper on the terminal. So just run the commands and see what the hold up or error is.
However, Often times when I see freezing up that takes a long time to fail it is network related items. Such as an internal Maven repo that is not resolving properly. So check your internal Maven repos as well that they exist and you set them up correctly.
You can also turn off the internet and start it up, it will load into offline mode and not attempt to load any internet items and offers popup to move to offline mode in gradle. This will give you a chance to make your corrections until Android Studio improves these issues.
Rather than Choosing Start a New Android Project, Open an Existing Project and then
goto file>>new >>new Project
If You create android project by following these steps , You can see every error of you gradle build in
logcat
I have made a PhoneGap/Cordova based application, that seems to work fine when tested with Chrome + Ripple.
When I'm trying to install it to my Android device(which is ADB configured, and shows up in Eclipse SDK), I get the INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES error.
By reading existing posts on the same issue, I understand that it has to deal with re-installation of the app.
But, this is the first time I am trying to run this app on any device, and I don't see how re-installing might solve the problem.
Any advice on resolving the error would be much appreciated.
Look for another app in settings->apps->downloaded that may have the same package name and uninstall it.
I'm having problems with Robotium being unable to find my app at runtime.
Just to be clear, I've seen a few similar questions on SO however, they seem to revolve around the Robotium Solo class not being found at runtime (or some other 3rd party lib). However, this is slightly different as my Robotium tests can't find the project under test.
The tests are in a separate project which has a dependency on my app project. There are no problems at compile-time but when I try to run the tests I get...
java.lang.RuntimeException: Exception during suite construction
at android.test.suitebuilder.TestSuiteBuilder$FailedToCreateTests
....
Caused by: java.lang.NoClassDefFoundError: com.myapp.mobile.activity.RegisterUserScreen
Where RegisterUserScreen is an activity in my app. This happens on the device and the emulator.
I'm building / running in IntelliJ 12.1.4, against Android 4.1.2 and I see the same result when I attempt to run the test from the command line.
Probably worth pointing out that running adb shell pm list instrumentation from the command line returns the correct instrumentation...
instrumentation:com.myapp.mobile.test.system/android.test.InstrumentationTestRunn
er (target=com.myapp.mobile)
Thanks in advance,
Neil.
In your device go to settings->apps and check whether in installed or running application list name of your testing application name is present. If you find it there then uninstall the testing app as well as your original app (which has to be tested). Many times it happens that either because of different versions/signature mismatch test-application fails to find the target application.
Create your run configuration as an "Android Tests" not as "JUnit"
I am having some very bizarre behaviour. I have a large number of test cases for my Android application, and they all work except for one. When I run this one I get a java.lang.NoClassDefFoundError: org.JUnit.test
Yes, I have the JUnit 4 library imported into the project, and my other JUnit tests are running without any problems. What is particularly bizarre is that before I hit this problem I had an error in my code- basically, I tried writing a file to a read only folder. When that occurred, the JUnitTest would execute up to the point where it would hit an IO exception for accessing a part of memory it cannot access. I fix this problem, and suddenly the Android emulator doesn't seem to know what org.JUnit.test is.
I have examined the run configuration for this test class, and it is the same as my others. It is in the same folder as the other tests as well. It also uses the same import statements. Any idea on what is going on?
I am using the Android 10 emulator, and eclipse version 3.7.2.
Edit: To clarify, the error I get appears on Logcat and not in my Eclipse project.