Develop Reference

Issue with importing a code in Android Studio [closed]

Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 1 year ago.
Improve this question
I am working on someone's else app, which I have cloned from another repository. While running the application, I keep on getting an error message.
The error message which I get is the following:-
Invalid injected android support version '202.7660.26.42.7351085',
expected to be of the form 'w.x.y.z'
The system is running on OpenJDK version "1.8.0_292"
The Android Studio is currently on its version 4.2.1
I tried upgrading the Android Studio, to the Canary Channel, but the problem seems to still exist.
Update
The problem is solved, just upgrade to Arctic Fox(2020.3.1) and it works like a charm. The problem was, the file had dependencies, which were incompatible with my machine. So it didn't work out well initially.

I think maybe that android project is using some feature that is still under development and not released yet

Try to Update Android Studio, this problem appear on older versions. hope this will work

When i tried to add the library it gives an error of versions .. help me to solve it please [closed]

Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 5 years ago.
Improve this question
When i execute the library it gives an error of versions .. help me to solve it please!

this is not an error in fact.
It is a warning telling that you are using one version of android support library (26.1.0), and your library is using another version (27.0.2)
To solve this warning you should use version 27.0.2 too. But it might be not required. You may try building the app as it is now.

Confusions in NDK samples [closed]

Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I am a beginner to Android NDK with Android Studio. While trying to grasp the ideas through tutorials I got my self very confused. Mainly I am confused about the building method of native project.
For example while following this tutorial, when I build the project there is no file created inside libs project. Moreover, there is no need of Android.mk and Application.mk make files also.
However, second tutorial deals with the make file.
Can anyone please explain to me step by step explanation of build steps. I am not sure how hard it is for Android team to make a simple tutorial explanation one version of built.

Not sure, if by the time of this writing (2016/02/01 - Android Studio 2.0 Preview 9) NDK is officially supported yet, but it's surely been under development. That's the reason of using Eclipse+ADT+NDK in the official guide as you can see in the Setup section. I believe, once the process is done, the documentation will be updated.
You're free to choose which approach to use:
Eclipse+ADT+NDK or
Android Studio + Gradle + NDK
With the second approach Gradle generates *.mk files automatically, although you can use your own files by preventing the auto-generation as per The new NDK support in Android Studio by ph0b.

Android application stops unexcepetdly after importing and working in Android Studio? [closed]

Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 8 years ago.
Improve this question
After I have moved to the Android Studio, Projects which are imported from Eclipse are force stopping when build and running on emulator and on device. When they are build and running from eclipse its working smoothly.
I have tested on emulator all versions above 2.3., All are showing same problem.
And also tested on Samsung galaxy ace, Galaxy Core, Xperia and some Microamx devices.
Is there any options to be set for the android studio?

First Of all Go through this Documentation and check the new build system
and some useful blogs
Blog1 Blog2
They might Help you

I would suggest you to go through this link and cross-verify what wrong you may be doing to import your eclipse project to android studio :
MigratingToAndroidStudio

Eclipse and Android Studio's Folder Structure is Different...
If you Export android project and Directly Import to Android Studio, That will not Working..

Latest Eclipse update causes errors? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions concerning problems with code you've written must describe the specific problem — and include valid code to reproduce it — in the question itself. See SSCCE.org for guidance.
Closed 9 years ago.
Improve this question
today I've updated my Eclipse (Win7 x86_64) with latest android updates and it caused some errors. First of all, after cleaning project Eclipse didn't generate R files. I've tried to find any possible error in my xml files, although - there was none. I've copied my project and opened it with Eclipse without latest updates on Arch Linux - Eclipse generated R file and everything was OK. I think that's also important to mention, that after updating Eclipse on Windows the new code, that I've written didn't work - worked perfectly on Linux's instance. I've copied all R files and folders to Windows, yet couldn't run app, because my apk was missing and after that I've just gave up.
Anyone had similar problems or is there any possible solution?

i had experienced the same. For the new SDK(ver 22.0.1), we need to install a new tool Android SDK Build Tools.
After that, update the eclipse ADT.
Restart the eclipse.
Then clean and run the project.

I had a similar experience some versions back. The work-around I found was to setup an entirely new and separate IDE instance including a different SDK folder location. Install from scratch! Good luck ...