Good afternoon.
I have a project in which I use the Google Maps library. The project is realized with Eclipse and I never had any problems. Two weeks ago I installed the Android Studio and migrated my project. Since then, when I make the call to the map I get an error "java.lang.NoClassDefFoundError". At compile time everything goes perfectly but when I run it on the phone is when the error arises.
Thank you.
Try to create a new Android Application Project and copy the folders required from your previous project and run the application.
I too was facing a similar issue on Eclipse itself, and received Trgaet InvocationException and NoClassDefFoundError, for the same code which was correctly working for weeks.
Hope it works, although it is not a permanent solution.
Related
When I got the build from the project, the game worked fine on all Androids. But the game crashes on Android 13! And it says that the program has stopped.
First, I said that the problem might be with the SDKs. I downloaded all the new SDKs, but the problem was not solved.
Then I said that maybe the project had a problem, and I created a new project and got the same build, but the problem was still not solved.
Then I said that maybe the problem was due to the Unity version, so I downloaded the latest version of Unity and made a build with it, but the game crashed again.
Then I said that maybe Unity couldn't build correctly, so I exported the project and built it in Android Studio. First, the apk size increased, but the game crashed again!
The project builds without errors, only when I enter the player settings and other settings; in the part that wants to load the maximum API and target, it says "getting API level..." When the API is loaded, several warnings are given in Unity! I think this could be the problem, but I haven't found any way to fix these warnings. I am posting here the screenshot of these warnings and the downloaded SDKs.
I would be grateful if someone could help me to solve this problem.
I am using Unity 2021.3.8.
Try out this one:
https://www.youtube.com/watch?v=fP1moOOWhrY,
It should solve your problems.
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.
After creating a new app engine connected android project it immediately generates errors in the build path of the generated client libraries. It suddenly happened in my other main project (that project has been working for quite some time) and after failing to solve it I created a new test project which has the same error from the start. I have tried cleaning the project, restarting Eclipse, even re-installing Eclipse... Any ideas?
Regards
See screenshots here:
(source: osmoel.se)
And
(source: osmoel.se)
It seems that Google has some issues with Cloudendpoints today after the release of the appengine sdk 1.7.7. There was another problem described here where cloudendpoint users could not see their APIS in the api-explorer (https://developers.google.com/apis-explorer/)
https://code.google.com/p/googleappengine/issues/detail?id=9167
Endpoints stopped working with proxy.html error
I believe this is the relevant issue:
https://code.google.com/p/google-plugin-for-eclipse/issues/detail?id=117
I have an android project where I am using the generated client libraries for google app engine. IT was working great until suddenly I am getting an error marker on the endpoint-libs folder. inside the folder there is no specific file with an error market on it, but It wont let me launch the application. I get no error in the console, and I did absolutely nothing to the code. It simply just stopped working. Does anyone know what might have caused this? I appreciate any responses because i'm clueless.
When Eclipse shows the error indicator, but doesn't indicate which file has the error, look at Windows -> Show View -> Error Log or Problems (can't remember which of these it is).
(Often it is often a build or build path error in this case.)
Also, it is good to refresh and clean your project (project menu -> clean) in a situation like this
If those don't help, had you recently generated a new endpoints client library? Or updated one of the SDK's?
I seem to have more success running my Android Cloud Endpoints application in the BlueStacks emulator versus the regular emulator. The regular emulator seems to be unsuccessful at running query operations frequently whereas Blue Stacks works quickly.
In my osmdroid project, the error below is what used to happen when I was missing the library slf4j-android-1.5.8.jar
java.lang.NoClassDefFoundError: org.slf4j.LoggerFactory
I added that library, and the app runs perfect the first time. But when I close the app and re-open it, I again get the error on start-up.
I have to reinstall the app every time I want the app to open successfully.
Edit: I now have the android specific version of slf4j, but that does not seem to fix the issue
I think what you need is the Android specific version of sl4fj. I use slf4j-android-1.5.8.jar with no problems. There is a later candidate for release. Both jars may be downloaded from this page