Device compatibility issue on the Play Store(Play 商店的设备兼容性问题)
问题描述
我有一个关于在 Google Play 商店上发布 Android 应用程序的奇怪问题.问题是有 0 个设备兼容,因此我们无法发布它.
I have a weird issue regarding the publication of an Android application on the Google Play Store. The issue is that there are 0 devices compatible hence we can't publish it.
清单文件如下所示:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.xxx"
android:installLocation="auto"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk android:minSdkVersion="7" android:targetSdkVersion="15" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission android:name="android.permission.READ_CONTACTS" />
<supports-screens
android:largeScreens="true"
android:normalScreens="true"
android:xlargeScreens="true" >
</supports-screens>
<application
android:name=".application.xxx"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@android:style/Theme.NoTitleBar">
<!-- To use google maps -->
<uses-library android:name="com.google.android.maps" />
<!-- activities/services defined here -->
</application>
</manifest>
如您所见,这里没有什么特别之处.我什至尝试使用定义为 0 的权限发布应用程序,只是为了看看会发生什么,但我仍然遇到同样的兼容性问题.
As you can see there is nothing special in here. I have even tried to publish the app with 0 permissions defined just to see what would happen and I still got the same compatibility issue.
我要提几点:
- 我已尝试使用 0 权限发布,但仍然是同样的问题.
- 我尝试将
minSdkVersion
设置为 13,仍然是同样的问题. - 我正在使用
Ant
(ant clean release
) 构建.该应用程序可在我们的任何设备上正常运行(Galaxy SII with 2.3
、HTC Sensation with 2.3
、Galaxy Spica with 2.1
、NexusS 与 4.1.1
). - 在我的代码中的某个时刻,我正在使用特定于 API 13 及更高版本的功能,但我在运行时检查 API 级别并将该功能替换为与旧版本兼容的另一个功能.
- I have tried publishing with 0 permissions, still same issue.
- I have tried setting the
minSdkVersion
to 13, still same issue. - I am building using
Ant
(ant clean release
). The app runs fine on any of our devices (Galaxy SII with 2.3
,HTC Sensation with 2.3
,Galaxy Spica with 2.1
,Nexus S with 4.1.1
). - At some point in my code I am using features specific to API 13 and above but I am checking at runtime the API level and substitute that feature with another one compatible with older versions.
有什么想法吗?
谢谢!
编辑
aapt dump badging
的输出是:
package: name='com.myapp' versionCode='1' versionName='1.0'
sdkVersion:'7'
uses-permission:'android.permission.INTERNET'
uses-permission:'android.permission.WRITE_EXTERNAL_STORAGE'
uses-permission:'android.permission.ACCESS_FINE_LOCATION'
uses-permission:'android.permission.ACCESS_NETWORK_STATE'
uses-permission:'android.permission.READ_CONTACTS'
application-label:'MyApp'
application-label-fr:'MyApp'
application-icon-120:'res/drawable-ldpi/ic_launcher.png'
application-icon-160:'res/drawable-mdpi/ic_launcher.png'
application-icon-240:'res/drawable-hdpi/ic_launcher.png'
application-icon-320:'res/drawable-xhdpi/ic_launcher.png'
application: label='MyApp' icon='res/drawable-mdpi/ic_launcher.png'
uses-library:'com.google.android.maps'
launchable-activity: name='com.myapp.activities.SplashScreenActivity' label='MyApp' icon=''
uses-permission:'android.permission.READ_EXTERNAL_STORAGE'
uses-implied-permission:'android.permission.READ_EXTERNAL_STORAGE','requested WRITE_EXTERNAL_STORAGE'
uses-permission:'android.permission.READ_CALL_LOG'
uses-implied-permission:'android.permission.READ_CALL_LOG','targetSdkVersion < 16 and requested READ_CONTACTS'
uses-feature:'android.hardware.location'
uses-implied-feature:'android.hardware.location','requested a location access permission'
uses-feature:'android.hardware.location.gps'
uses-implied-feature:'android.hardware.location.gps','requested android.permission.ACCESS_FINE_LOCATION permission'
uses-feature:'android.hardware.touchscreen'
uses-implied-feature:'android.hardware.touchscreen','assumed you require a touch screen unless explicitly made optional'
uses-feature:'android.hardware.screen.portrait'
uses-implied-feature:'android.hardware.screen.portrait','one or more activities have specified a portrait orientation'
main
other-activities
other-services
supports-screens: 'small' 'normal' 'large' 'xlarge'
supports-any-density: 'true'
locales: '--_--' 'fr'
densities: '120' '160' '240' '320'
推荐答案
坦率地说,Google Play 搞砸了.我有三个已发布的应用程序,它们与 0 台设备兼容,但拥有数千名用户.更奇怪的是,Google Play 为我提供了这些应用的统计数据,显示了世界各地的用户.
Quite frankly, Google Play is messed up. I have three published apps which are compatible with 0 devices, and yet have thousands of users. Even weirder, Google Play gives me statistics for those apps, showing users all over the world.
所以我会说继续发布它.有时可能需要一段时间才能显示,但一旦显示,您应该能够将其安装在您的设备上并确认用户可以下载它,尽管控制台显示 0 个兼容设备.
So I would say go ahead and publish it. Sometimes it can take a while to show up, but once it does, you should be able to install it on your devices and confirm that users can download it, despite the console showing 0 compatible devices.
这篇关于Play 商店的设备兼容性问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持编程学习网!
本文标题为:Play 商店的设备兼容性问题
基础教程推荐
- 在 gmail 中为 ios 应用程序检索朋友的朋友 2022-01-01
- UIWebView 委托方法 shouldStartLoadWithRequest:在 WKWebView 中等效? 2022-01-01
- android 应用程序已发布,但在 google play 中找不到 2022-01-01
- Kivy Buildozer 无法构建 apk,命令失败:./distribute.sh -m “kivy"d 2022-01-01
- 当从同一个组件调用时,两个 IBAction 触发的顺序是什么? 2022-01-01
- Android:对话框关闭而不调用关闭 2022-01-01
- 如何在 iPhone 上显示来自 API 的 HTML 文本? 2022-01-01
- 如何让对象对 Cocos2D 中的触摸做出反应? 2022-01-01
- 如何在没有IB的情况下将2个按钮添加到右侧的UINavigationbar? 2022-01-01
- 如何在 UIImageView 中异步加载图像? 2022-01-01