I realise that this question has been asked (and solved) here before, however the most frequent and obvious solution, which is to place
<uses-permission android:name="android.permission.INTERNET"/>
in the Android.Manifest.xml file, does not work for me.
I have double checked that I have not placed this within the manifest's
<application />
tag, yet it still doesn't work.
I'm running Android 9 (Pie) as the target version, but I can't find any breaking changes with that API which may give this error. I have also cleared the cache on my Google Chrome app, which the app is using as it's default Webview.
Solved
In the end this was nothing to do with Android. I eventually just disabled the Chrome app on my test phone (Samsung S8) and it now works.
Related
I found lots of questions about this but I have a different problem. The launch icon is not refreshing on a specific phone with Android 10. I tried to changed it and installing it again and does work. The good thing is that on another phone with Android 7 works perfectly fine, even changing the icon.
It's clearly a phone cache problem. The Same flutter app on two different devices present different icons.
This didn't worked:
Uninstalling the App
Shutting down the phone
Turning on the phone
Installing the app
Tried with Visual Studio Code, Android Studio and the Cmd console, it doesn't work. I hoped that the release installation will work but nope.
Any ideas?
Found the problem.
My Android manifest has:
android:icon="#mipmap/ic_launcher"
android:roundIcon="#mipmap/ic_launcher_round"
For Android 10 it was taking the ic_launcher_round, and for the Android 7 the ic_launcher. I would like to know if there is some kind of configuration to change this or it is an Android fixed thing.
I'm working on a libGDX application and based on this question I'm forcing portrait orientation in activity tag of AndroidManifest.xml like this:
android:screenOrientation="portrait"
android:configChanges="keyboard|keyboardHidden|orientation|screenSize">
This used to work fine on my devices until my Samsung Galaxy S4 got upgraded to Lollipop (5.0.1) from KitKat. Now it doesn't work on this device, while still working on others (with lower Android versions). On the S4 it just displays the application in landscape, ignoring rotation.
I was looking for differences in the 5.0 API that could explain this, but couldn't find anything.
Edit: I've just tried exporting my app to .apk and it displayed properly. Previously I was running it from Eclipse debug mode. It shouldn't be hard to pinpoint the issue, but I don't have time to investigate it at the moment.
Edit2: I've just tried running it from Eclipse on a different machine, where I have API 21 (so Lollipop) and it worked. However my working .apk has been exported on another machine, where I have API 20. It's really puzzling me. Might be something related to Android plugin versions, but I'm not sure if I will be able to pinpoint it.
try
android:screenOrientation="sensorPortrait"
I am not sure what your API level. But there was a google bug around this issue, which was fixed by API 16. If you are using anything earlier and if above line does not work, try
android:screenOrientation="sensorPortait"
instead.
i am trying to develop a application that uses Google maps API v2 but since i can't display it on emulator, i tried to use bluestack. it seem to have google play services installed but when i run it, it has an error. i forgot is what error as it is few days ago and did not take down the error. today i wanted to run it again but eclipse did not recognize the bluestack device. usually i make eclipse recognize bluestack is opening bluestack first but it did not work this time.
i believe it is due to this error where the blue stack emulator could not set the target API
. the pic is some time ago.
i can run on my real phone where it display the map with no problem but for presentation purposes i would prefer to display it on an emulator if possible. i can also test gps by sending it location.
You need to set android:targetSdkVersion on uses-sdk in the AndroidManifest.xml file.
As new versions of Android are released, some style and behaviors may change. To allow your app to take advantage of these changes and ensure that your app fits the style of each user's device, you should set the targetSdkVersion value to match the latest Android version available.
Example:
<uses-sdk android:minSdkVersion="4" android:targetSdkVersion="15" />
For more info, refer API Guides - <uses-sdk>
I recently posted about the Play store not letting me publish my app without a minSdkVersion, but whenever I set it to anything above "1" my app just doesn't work (minSdkVersion breaking program).
So this guy suggested to just set my minSdkVersion to 1, which worked. But now when I submitted my app even though the developer site says:
API level: 1-16+
Supported screens: normal-xlarge
OpenGL textures: all
But the app only shows it supports Android under 4.x, I developed it on my 4.0.4 device. I tried searching around and I found that some people have problems with services messing up the phones it supports, so I deleted all of my services, because I don't really need any for this version of the app to submit. And it still didn't work. So I don't know what else to do, here is my AndroidManifest.xml if it helps... I've been trying to figure out why my application isn't working for a week now, still nothing. I have tried setting a targetSdkVersion to something like 14, my application still breaks. I cleaned out my code, taking everything out of the already short, 200 lines, application, and it still isn't working. Is there something I can't use in an android application 4.0 that I am using in my application? or is it just my AndroidManifest? Thank you so much!
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.unparalleledsoftware.app.list"
android:versionCode="5"
android:versionName="2.02" >
<uses-sdk
android:minSdkVersion="1" />
<application
android:icon="#drawable/ic_launcher"
android:label="#string/app_name"
android:theme="#style/AppTheme" >
<activity
android:name=".MainActivity"
android:label="#string/title_activity_main" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
I should note,I am using the Theme.Holo.Light, but even if I change it to DeviceDefault it doesn't work.
Edit:
I googled the app on my friends Samsung Galaxy S3 (it didn't show up in the Play Store on his phone), when I installed by googling the app and hitting the "install" button on google and it opened in the Google Play store and was able to install. When I did the same on my phone, Galaxy Note, it opened in the Google Play Store, but then said "Not compatible." Why? They are both on the same version of OS. Why is mine not compatible, nor the One X compatible, but the Samsung Galaxy S3 worked...?
Edit: I get these errors/problems when compiling with a targetSdkVersion, http://pastebin.com/mxgWNLdM
It's showing up as "Requires Android 1.0 and up" on my end, and there's nothing wrong with your manifest either. It'll show up on all devices.
You should, however, avoid using Holo themes if you're targeting devices running versions of Android prior to 3.0. The best practice is to create two themes - one for API levels 1-10 and one for API level 11+, and make sure that the v11 one is using a Holo theme as the parent style.
Your Manifest file only has a minSdk setting which is odd/bad since according to the documentation if you don't set a targetSdk, it will default to the minSdk level.Android Manifest - Uses SDK element. The thing is that an API setting of 1 is really old and I wouldn't be surprised that Market/Play has issues. If you developed this on ICS, you should really have a targetSdk. Also if it was developed for API level 14, you should have a supports-screen element as well.
At worst, I would create a new project and copy over that manfest file for any missing elements. If you are still having issues with a targetSdk and supports-screens, turn on verbose build messages and see if anything looks wrong.
I you posted your complete Manifest file above, then I suggest adding <supports-screen> entry (above <applicaion>) to it, like this:
<supports-screens android:largeScreens="true"
android:normalScreens="true"
android:smallScreens="true"
android:anyDensity="true" />
Lack of it (if not intentional) causes application to be not available for any device it should, due to Play's filtering mechanism.
The app is Flash Cards Max on the Android market. I recently updated my app with a 1.6 only feature. However, I still want the app to work with those that have Android 1.5. I built it using Android 1.6 in Eclipse and I have the correct strings in the Android manifest file.
<uses-sdk
android:minSdkVersion="3"
android:targetSdkVersion="4"
/>
<uses-permission android:name="android.permission.INTERNET"></uses-permission>
<uses-permission android:name="android.permission.RECEIVE_BOOT_COMPLETED" />
Everything works in the emulator fine on 1.5 just want to be sure it shows up on the Android Market for those with 1.5. It does not. This is a market filtering question.
Please see this thread for info on what I changed and how I went about it thanks to several of your suggestions.
tl;dr
Why doesn't my app show up for 1.5 users?
Answer by a helpful user on Reddit.
"I had the same problem, solution was <supports-screens/>
Why?
Because
android:anyDensity
Indicates whether the application can accommodate any screen density. Older applications (pre API Level 4) are assumed unable to accomodate all densities and this is "false" by default. Applications using API Level 4 or higher are assumed able to and this is "true" by default. You can explicitly supply your abilities here."