I have been trying to run my android project on different devices but my Android Device Chooser doesn't seem to be detecting them. USB Debugging is enabled on my device. The Minimum API version is 10 and Target API version is 19.
I have tried all options listed in similar questions but none of them seems to work for me. Has anyone else faced this issue before?
Tried to Change targeted API from Google API to 19,20 or 21.
Related
I have migrated my app to the 5.0.0 version of the billing library, as it is adviced. However, I've found that it's not working properly on old devices in which the old library did work. I've tested it on Android 7 (Nougat API 24), Android 9 (Pie API 28) and Android 12 (S API 31). The only one in which it's not working it's on the Nougat one and I would like to know if it's somewhere in the documentation reported which API levels are supported and which don't.
The "error" I'm getting is SERVICE_UNAVAILABLE as response code when calling queryProductDetailsAsync.
I'm also assuming it's a sdk version issue, as I can't find other cause (the Play Store is updated, the wifi is on and my Google account logged in).
Something must be misconfigured in the phone. I tested on an Android 6 and it worked, so I tried completely restoring my Android 7. Now it works.
However, I still wonder why the old library worked and the new one didn't.
I've built an app that successfully runs on all sorts of Android devices. It was compiled for Android 8, but the device it's running on is Android 9.
Every time I open it on this Huawei P20 Pro, I get a crash. The only sensible error I can see is:
No implementation found for android.content.Context md5c497ac42f3138c67aed930c79af470d4.MainApplication.n_getApplicationContext() (tried Java_md5c497ac42f3138c67aed930c79af470d4_MainApplication_n_1getApplicationContext and Java_md5c497ac42f3138c67aed930c79af470d4_MainApplication_n_1getApplicationContext__)
I never call the get Application Context at any point, so I'm really not sure what is going on here.
Any helpful tips on debugging an issue like this?
If you compiled it with SDK 27 as max API (version 8) why would you run it on SDK 28, Compile with max version available 28 or 29 and then try running
In manifest make it android:targetSdkVersion="28" and compile using latest
First of all, I believe that the issue lacks enough details to make any assumptions about the possible causes. One of the possible causes is setting the target SDK version incorrectly. You can attempt to set to a correct one for the app as Ross Vernal suggested. It may can solve your problem.
Based on what I read from the official Android documents about the targetSdkVersion property, setting the version lower than the API level of a mobile device means that some additional compatibility behavior may be required when the app runs.
But this does not mean that the app cannot run on the devices with higher API levels. Whether the compatibility behavior is required depends on the app itself.
Therefore, it's possible that a feature or something else that you have decided to use in your app caused the issue on the device.
Additionally, I tested these conditions on my Huawei device that runs on Android 9 (SDK 28) with a sample Xamarin.Forms app under a target SDK of 27.
The app launched successfully. This supports the possibility mentioned above.
I have a Visual Studio 2010 Professional.I've installed NVIDIA AndroidWorks.I have a tablet with Android 4.1.1 also.I`ve been tried to debug simple android NDK application in Visual Studio 2010 Professional on my device, but I received some error 'Failed to attach: Android 4.1(API level 16) devices are not currently supported'.
Сan I somehow solve this problem or debugger really currently does not support Android 4.1 device?If not supported, are there plans for this in future versions NVIDIA AndroidWorks?I do not have the ability to upgrade the operating system on my tablet.
In General, wrote on the NVIDIA forum and got the answer, maybe someone will be useful:"There is a bug pertaining to API level 16 devices that makes debugging native code on them impossible. We've decided to fail earlier with an error message instead of letting people get to the buggy behavior.
So, unfortunately, you can't debug on a Android 4.1 device. As a workaround, you could try downgrading the device to API level 15 or installing a custom firmware (such as CyanogenMod) that is based on a later API level than 16."
I created a project to implement USB accessory. The accessory mode is supported for Google API level 10 which works on Android 2.3.4.
Now my project works on AVD which has target device as Google APIs level 10 but does not work if I change the target to 2.3.3 ( Since 2.3.4 target is not there on eclipse).
In short I want to run a project that uses Google API level 10, on an android phone. How to do this?
I tried copying the .apk file but that was of no use. I also tried to copy the complete project but this is also not working for me.
Please assist...
I guess the obvious answer (though not the one you're looking for, I suspect) is that you'll need to get a device that's running 2.3.4 or higher (my current RAZR MAXX is at 2.3.6). A device that's running a version lower than 2.3.4 can't be asked to run an app compiled for versions 2.3.4 and higher.
and this may (or may not) be helpful to clear things up as well:
Can't find android sdk 2.3.4 in SDK manager
Welcome to Stack!
You are right, USB accessory does not work with 2.3.3, only with 2.3.4 and up. (And it does only work on selected phones, of course.)
I've an app that uses Android accounts - GoogleLoginService on (< 2.1) and AccountManager on 2.1 or greater. the app works fine on phones, but doesn't work on any of the emulators.
When I try adding accounts in emulator, it fails. In 1.6, option doesn't even exist.
Is there a workaround? I heard that there is a custom system.img that has Accounts inbuilt, but cant find one. I need it for 1.6, 2.1, 2.2
Are your emulators using the Google APIs versions of Android? If not, use the SDK manager to get those versions of Android, and create a new emulator with one of them as the target.