2026-10-08 · Permissions & API

Google Play 后台位置权限声明(Background Location Access Declaration)——为何 ACCESS_BACKGROUND_LOCATION 必须提交权限声明表并获批、什么才算法定「核心功能」、只能声明一个功能的原则、必需的 30 秒以内视频演示、显著的应用内披露文案(含 Google 明确接受的措辞)、以「前台服务」作为首选替代方案、Android 11+ 的运行时变化,以及 2026 年「最小范围(Minimum Scope)」新规如何让定位按钮在 Android 17+ 成为强制项

1. 后台定位是「声明门禁」权限。Google Play 把后台位置视为敏感数据:"that access location in the background must be approved via the permission declaration process in the developer console. Without that approval, app updates may be blocked and your app may be removed from Google Play."(https://support.google.com/googleplay/android-developer/answer/9799150)仅把 ACCESS_BACKGROUND_LOCATION 写进 manifest 就直接上架是不行的。

2. 什么算「后台」。原文:"Access to the location in the foreground happens while an app is open and visible to the user. If the access happens after a user closes the app or uses the home button to return to their main screen, then the app's access to the location is in the background." 也就是说,只要用户在界面不可见时读取位置,就属于后台访问——包括通过前台服务进行的位置读取。

3. 只有核心功能才够格。原文:"Background location may only be used when it provides a significant benefit to users and is relevant to the core functionality of the app." 「核心功能」指应用的主要用途,且 "the core feature(s) must all be prominently documented and promoted in the app's description"。如果某功能不是必需(没有它应用并不会损坏、不可用),声明基本会被拒。

4. Google 点名了「本可前台实现」的功能。政策列举了宜用前台实现的场景:仅在应用内建议附近好友/玩家;在应用关闭时无任何提醒/功能的内容个性化(本地新闻、歌单);基于地区的 DRM;面向用户(而非司机)的配送/订单跟踪;逐向导航(除非在应用外也做被动路线/步数跟踪);聚合位置显示路况/网速。原文:"If your app only has functionalities such as those above that require the use of location in the background, consider using access to location in the foreground instead."

5. 广告与分析绝不能作为理由。同一篇文章两句硬性规定:"You should never request location permissions from users for the sole purpose of advertising or analytics";"Access to the location in the background solely for the purpose of ads will be denied." 若确因广告使用位置,还须符合 Use of Location Data for Ads 政策,并在披露中如实写明。

6. 声明表只能描述「一个」功能。Play Console 路径:App content > Sensitive app permissions > Location permissions。必须 "Tell us about one location-based feature only in your app that requires access to location in the background and explain why it can't be implemented without this access."。规则很硬:"We can only evaluate one feature at a time. The inclusion of multiple features will result in an app's rejection." 批准是针对整个应用,而非该单一功能,所以要挑最有说服力、对用户最有价值的那一个。

7. 哪些 manifest 会触发表单。"targets Android 10 or newer (SDK level 29 or higher) and contains ACCESS_BACKGROUND_LOCATION permission in the manifest, you'll be directed to complete details on location usage.";而 "targets Android 9 or older (SDK level 28 or lower) and contains either ACCESS_COARSE_LOCATION or ACCESS_FINE_LOCATION, you will need to indicate your intention to access location in the background and then you'll be directed to complete details on location usage."

8. 视频演示要求。需提供一段短视频,"clearly demonstrates the location-based feature being used in your app... Be sure to include in your video the prominent disclosure dialog that gets shown to users."。要展示应用未在使用(后台)时功能被激活、如何启用该功能、显著的应用内披露弹窗以及运行时(runtime)授权弹窗。"Aim for a video duration of 30 seconds or less. The preferred format is a YouTube link, but Google Drive storage links to an MP4 or other common video file formats are also supported.",且必须 "reflect your app's behavior on an Android device. For example, don't submit a video of your iOS app."。

9. 显著应用内披露的措辞(务必照抄要点)。披露必须位于应用内、在日常使用路径中(不能藏在菜单/设置里);须说明访问/收集的数据内容与用途/共享方式;不能只放在隐私政策或服务条款里;也不能与无关的个人/敏感数据披露混在一起。用词必须包含 "location",并含以下短语之一:"background" / "when the app is closed" / "always in use" / "when the app is not in use",并列出所有使用后台定位的功能。Google 推荐模板:"[This app] collects location data to enable [\"feature\"], [\"feature\"], and [\"feature\"] even when the app is closed or not in use."(仅当确实用于广告时,才追加 ", and it is also used to support advertising"。)

10. 四份材料,隐私政策要放两处。审批材料为:(a) Permissions Declaration Form;(b) 视频演示;(c) 显著应用内披露;(d) "Privacy policy both in your app and on its store listing page."。此外还要在商店页面本身传达后台定位信息(描述,最好附一张显示地图/用户位置或带地理标记内容的截图;标题/图标措辞为可选)。

11. 前台服务是可行的替代方案,但有条件。改用前台服务(FGS)会被单独审核:其使用 "must be initiated as a continuation of an in-app, user-initiated action",且 "must be terminated immediately after the application completes the intended use case of the user-initiated action"。关键在于:"if an app's use of device location via foreground service is equivalent to ACCESS_BACKGROUND_LOCATION (or otherwise 'location in the background'), the app will be subject to location in the background permissions requirements."。参见 Permissions for Foreground Services 政策(https://support.google.com/googleplay/android-developer/answer/13392821)。

12. Android 11+ 的运行时变化与 2026 年「最小范围」新规。Android 10 的系统弹窗含 "Allow all the time";但 "On Android 11 (API level 30) and higher, however, the system dialog doesn't include the Allow all the time option. Instead, users must enable background location on a settings page."。应结合 shouldShowRequestPermissionRationale() 与 getBackgroundPermissionOptionLabel() 做引导页,始终提供「拒绝」路径,并保证无该权限时应用仍可用。若用户在前台只授予「大致位置」,"your app has only approximate location access in the background as well."。(https://developer.android.com/develop/sensors-and-location/location/permissions/background)另外,2026 年 4 月的政策更新——《Minimum Scope: Foreground Location Access and the Location Button》(https://support.google.com/googleplay/android-developer/answer/17033915)与敏感权限预览(https://support.google.com/googleplay/android-developer/answer/16909972,2027-01-27 生效)——把 Android 定位按钮定为面向 Android 17(API 37)及以上应用的「事务性精确位置」最小范围强制方式,并对使用 ACCESS_FINE_LOCATION 的开发者强制要求声明。若确实不需要后台定位,被拒后的正解是:从 manifest 与相关源码中移除该权限,覆盖所有 APK 与所有轨道(含内测/公开)。

需要专家帮助?联系KappS获取专属解答 →
← 返回FAQ列表