Has anyone seen that their applications built against Android 2.0 (minSdkVersion="5") are not showing up at all in the market for 2.2 devices? Does anyone know a workaround (aside from building for 2.2).
Thanks,
Craig
Here's a good explanation of why this is happening:
"When an app is copy protected it causes this kind of behavior. Here is why. When an app is placed on the market the developer has the option to apply “Forward Locking”. This prevents the app from being pirated, and also prevents the app from being installed on a developer phone or an unreleased device.
Since Android 2.2 is not an “official” release yet the market gets a little unhappy because it doesn’t know what this OS/Device is that is trying to connect and thus applies the copy protection on these apps."
http://androidheadlines.com/2010/06/froyo-preventing-access-to-certain-apps-in-the-market.html
I think that protected and some paid app are not showing in 2.2
See Paul (ModaCo) twitter:
"It's entirely possible Google haven't 'flicked the switch' on the FRF50 build.prop yet, hence no paid apps until they do!"
edit: and I guess that protected app's are linked too.
There is a signature key for each Android build out there, including each manufacturer's inclusion of it in a device.
When you access the market, it checks this signature to see which applications you have permission to view.
In this case, Google have probably not enabled that signature to see certain applications, such as apps which are paid, protected or perhaps built for certain versions.
They still haven't enabled HTC Desire to view protected apps and it has been out for nearly two months -- there's even a bit of a furore over it on the internet, but Google don't seem to mind.
Related
We use a 3rd party SDK that crashes 100% of the time on Asus devices running Android 7.0 (we can't get rid of the SDK). The same device running 7.1 will not crash. I know I can block specific devices using the Google Play Developer Console, but I'd rather not block the devices since there's a chance that they either haven't updated to 7.0, or they have been updated to 7.1.
I asked Google Play support if there was something I was missing in the console, and they said it's not possible to block a manufacturer-API combination from the dev console. However, they said there was a way to do so using the manifest, but that they weren't qualified to tell me exactly how. I haven't been able to find any information on this. The docs mention how to declare restricted screen support using the manifest, but nothing about a manufacturer.
Does anybody know a way to accomplish this using the manifest?
I port my android apps for making bb10 builds . Since now from bb10.2.1 update blackberry has introduced a new concept wherein apk's can be directly installed and can be installed in BB10 devices if the manage apps in settings menu of the phone is made ON. My question is that I wanna restrict my users from doing so and not installing the apk's into bb10 . And take download my app only from appworld.
Has anyone faced and has fixed this issue kindly tell me on how to solve the same.
Based on the Android behaviour, I don't think you can restrict users from doing so.
I haven't tried it on BlackBerry but from what you say, that option sounds analogue to the Unknown sources setting under Security settings on Android. If the user enables the installation of applications from unknown sources on their phone, there is now way to prevent the direct install of the apk (by adding something to your apk or any other way).
There is no way to restrict it to BlackBerry World only. If they get the APK, they can load it directly this way. There may be other ways around it though.
If, for example, your app is for sale and people are side loading a pirated copy, you could change your app to be free, and put some advanced functionality in your app behind an in-app purchase. That way they'll be forced to go through the storefront at some point to pay. This takes bigger changes to your app though, and the IAP implementation is likely different between BBW and GPlay.
You could also put in a version check: when your app launches, it checks a special file on your web server to see what the latest version of the app is. If they don't have the latest version, it doesn't let them use the app until they upgrade. This won't prevent side loading or piracy outright, but you can put out updates often enough to make side loading very annoying. When they are roadblocked and told to get the new version, you can link directly to the storefront to encourage them to get the latest version there.
Thirdly, and lastly, if you port your app to a BlackBerry 10 native, cascades, or WebWorks app, the app file is fully protected and can't be pirated or extracted from BlackBerry World (since the platform is secure). That will 100% protect you from piracy on BlackBerry 10.
I hope this helps!
I found Google Keep from the Google Play on my device.
However, after reinstalling the Android system, I can not find Google keep from the Google Play and it shows that "Your device is not compatible with this version"
I am very confused for this searching result while the same device ran well with this app before.
I can understand there are several ways to install this app on my device again.
A couple of questions confuse me..
How can I check the features that this app may change in the new version? This may cause the reason why I can not find it in the Google Play.
Will that be any possibility to modify my device source code in order to find this app on the Google Play in my device?
Thanks
I just found that shouldnt the permission(feature) issue because I can find and install other apps which require more permissions than Google Keep.
The permissions that have anything to do with hardware are:
record audio (needs microphone)
precise location (GPS)
control vibration
If your phone has these features and runs Android 4.0 and up, it should be compatible.
I see two possible reasons:
After reinstalling you have an older version of Android. If this is the case, check for updates and after updating it should work
Your device model may have been blacklisted because of compatibility issues. In this case, Google may find a solution in the future and Keep will become available.
You can install Keep anyway, sideloading it. You just have to download the .apk from somewhere (Google it and be careful for malware).
i have my own app called Geoperks-rewards for you, the problem is i am not able to find my app from google play store for some handsets and even in tablet pc>Can anyone tell me what actually might be the reason behind this.I cannot specifically say for which models and OS versions, its appearing for random models.
The App compatibility depends on many factors, i.e. screen sizes, OS version, device hardware support, some features added in app, etc... All this information is provided on Android Developer website by Google. You can go through the topic Filters on Google Play and maybe revise the manifest.xml file of your app. You might get some idea why it is not compatible with several devices.
I published several free and paid app in the Market. I recently get
several complains from customers about not finding my app in the 2.1
Market. Even if they have bought them before, they can't find it in
the market or their download list after updating to 2.1.
Can anyone tell me what the problem is? My apps only require minimal SDK 3..
Thanks a lot!!
Update:
It looks like that they are not shown because they have copy protection enabled. Is this a bug in the Market?
I am having this difficulty also using my ROM OpenEclair (www.openeclair.org)
This only occurs on 2.1, but if it is a custom ROM - they may run into the trouble that the dev is using a Market from 1.6 instead of 2.1
Another possibility is using a 2.1 Market from a diff phone (such as the Droid Eris's Market on a Dream/Magic)
I think I found the answer and it has to do with recent changes in Google market filters on Jun 1st, 2010. Take a look at the following link:
http://developer.android.com/guide/appendix/market-filters.html
I found in my case that the app was hidden in some phones since I had included the following entry in my manifest:
It is because copy-protection is depreciated. Every build or release needs to be whitelisted by google as secure enough to have copy-protected apps. That way they can "ensure" it wont be copied.
From:
http://developer.android.com/guide/publishing/licensing.html
"Replacement for copy protection
Android Market Licensing is a flexible, secure mechanism for controlling access to your applications. It effectively replaces the copy-protection mechanism offered on Android Market and gives you wider distribution potential for your applications."
Use the licensing instead in order to hit a larger audience or customer base.