In my application there is 1 functionality for sharing the my application link from markrt.
But problem is that how could i get the link of my application on android market before
submiting the my application to the market...
Its very much easy, just look at below link:
https://market.android.com/details?id=YourPackageName
Where YourPackageName is the name of package of your application.
FYI, Generally android application is uploaded on market with the package name, which must be unique in any case.
For example:
https://market.android.com/details?id=com.facebook.katana , here com.facebook.katana is the main package declared in the AndroidManifest.xml file with package:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.facebook.katana"
android:versionCode="1"
android:versionName="1.0" >
Usually the android market follows the app link as with what you've mentioned in your android manifest.xml
For Eg.
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.company.testing.app"
android:versionCode="1"
android:versionName="1.0"
>
will be like this. But ensure the package you ve chosen is available in android market.
https://market.android.com/details?id=com.company.testing.app&hl=en
Related
i have written an android app with xamarin.android in visual studio and compiled a release build for android 4.1 and higher. testing directly with my devices works without problems.
after building an apk and uploading it in the play store for a beta test, it says: "app not compatible with your devices". i am pretty sure, that my test devices are not the problem. what could it be??
here is my manifest file:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="xxx" android:versionCode="1" android:versionName="1.1" android:installLocation="auto">
<uses-sdk android:minSdkVersion="14" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<application android:label="alone" android:icon="#drawable/Icon"></application>
</manifest>
on developer interface it says 10106 supported devices:
any ideas? thanks for your help...
best regards from germany,
steven
I dont use xamarin , but using studio if your gradle hava a different min sdk it will overwrite whatever os on you manifest , check your gradle file .
I have an android Library that outputs an aar library. This library will be built into different projectFlavors of Mobile, TV and Wear apps. I think that each of these platforms' should be the ones that set variables like the app name, icon, and permissions through the manifest and productflavors.
Is there any way to build an AAR without requiring an AndroidManifest.xml and therefore drawables(for the icon)?
More information about what I'm doing can be found at my last question on the subject:
Android Studio Java Library Module vs. Android Library Module
Any android library needs to have an AndroidManifest.xml file, but a name or an icon is not required. It's only needed when there is an activity that is MAIN and LAUNCHER.
You simply could use this manifest and your library will work like a charm.
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="[your package]"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk android:minSdkVersion="[min supported version]" />
<application/>
</manifest>
You can go with the AndroidManifest.xml below if you don't need to setup any Android component like Activities or Services or add custom properties.
<?xml version="1.0" encoding="utf-8"?>
<manifest package="com.your.library.base.package" />
I uploaded an APK for alpha which is version 1.0 and published as alpha. I made some changes in application and want to change the previous apk but it says 1.0 already exists. I tried to upload 1.0.1 but it says the same. What should I do?
old manifist file
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.urlconnectionclass"
android:versionCode="1"
android:versionName="1.0.0" >
new manifest file
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.urlconnectionclass"
android:versionCode="2"
android:versionName="1.1.0" >
always increse the value of versioncode and versionname while uploding apk of same production
Two important rules from Google:
The Version Code needs to be greater than that current version. Learn more about versioning your applications.
Example:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.package.name"
android:versionCode="2"
android:versionName="1.1">
<application android:icon="#drawable/icon" android:label="#string/app_name">
...
</application>
</manifest>
The updated APK needs to be signed with the same signature as the
current version.
All rules and requirements: Update your apps
You change version in android manifest?
I've implemented all the necessary things for "Move To SD card" functionality and the app can be moved to the SD card when launched from Eclipse or if I manually install the .apk file on the phone. However, after I've uploaded the apk to the Market, I've downloaded the app and "Move To SD" button was disabled.
The app is called "[redacted]".
<manifest xmlns:android="http://schemas.android.com/apk/res/android" android:installLocation="preferExternal" >
...
<uses-sdk android:minSdkVersion="7" android:targetSdkVersion="8" />
What could be wrong with it?
Have you checked that the button isn't grayed out because the app already is on your SD card?
When you declare "preferExternal", you request that your application be installed on the external storage as the default.
set android:installLocation="auto" in manifest
Example
<manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.mamlambo.article.phrasebook" android:versionCode="2" android:versionName="1.0.1"
android:installLocation="auto">
set minimum sdk version as 8. Because this feature is supported in android 2.2
<uses-sdk android:minSdkVersion="8"
There are at least three things to check.
installLocation="auto" in AndroidManifest.xml as you stated above.
Set target sdk version to at least 8
Make sure Copy Protection is OFF in the Android Developer Console, under Product Details
I have two apps listed on the marketplace. One of them is a free demo application, and the second is a second key application that unlocks the full version of the first application. I received a report from a user that the demo installs on their Huawei, but the market lists they application as "incompatible". I haven't received any other reports of this, and can't find anything useful on Google. The two manifest xmls are below, the demo app first and the key app second. Could this be caused by the check license permission? In android market developer console, the "supported devices" section is the exact same for both apps:
Supported Devices [Learn More] This
application is only available to
devices with these features, as
defined in your application manifest.
Screen layouts: SMALL NORMAL LARGE
XLARGE
Required device features
android.hardware.touchscreen
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="..."
android:versionCode="3"
android:versionName="1.1">
<application ...>
</application>
<uses-sdk android:minSdkVersion="7" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
</manifest>
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package=...
android:versionCode="1"
android:versionName="1.0">
<uses-sdk android:minSdkVersion="7"/>
<uses-permission android:name="com.android.vending.CHECK_LICENSE" />
<application ...
</application>
</manifest>
One thing to do is download both apps from Market, pull them off the device (with "adb pull"), and then use "aapt dump badging " on each of them. This prints out the "badging" information for the app; it is the same thing that Market uses to determine filtering and other things about the app. If there is nothing different between these, then the problem is not in how you have built your apps.