Flutter IOS 提交AppStore 审核失败(2)，android界面开发基础

最新推荐文章于 2024-04-15 16:47:44 发布

2401_84149496

最新推荐文章于 2024-04-15 16:47:44 发布

阅读量639

点赞数 25

分类专栏：程序员文章标签： ios flutter android

本文链接：https://blog.csdn.net/2401_84149496/article/details/137483627

版权

程序员专栏收录该内容

287 篇文章 0 订阅

订阅专栏

1.应用根本不需要定位功能。

2.应用需要定位功能，但是只需要短暂的获取少数的用户的位置，比如美团，新闻类的应用需要获得当前用户的所在城市，却使用了后台定位模式。

3.应用确实需要使用后台定位，比如打车类软件，但是应用中却没有任何界面展示这些定位数据。

解决方案：

4.如果你的应用根本不需要定位功能，但是还是在info.plist里面添加了location in theUIBackgroundModes key ，那么在plist文件里面移除UIBackgroundModes key就可以，这中情况较少，新手小白会犯这种错误。

5.如果只是简单获取位置不需要使用后台定位，只需要去掉info.plist 的文件中的 UIBackgroundModes 即可。

6.这种情况比较复杂，推荐的做法是通过表格或者轨迹展示出后台定位的数据，再提交审核的时候告诉苹果那个功能需要后台定位，具体展示后台定位的数据在那个界面,最后需要 Continued use of GPS running in the background can dramatically decrease battery life加到 App 描述里面，可以参考滴滴出行的描述，否则也会被拒绝。

info.plist 权限配置被拒

iOS 10 之后如果需要调用相机，蓝牙等设备时，需要在 info.plist 文件中进行相应的配置，否则应用会直接崩溃，在 iOS 10 之前则是无法访问。另外，如果在 info.plist 中调用了配置了权限在应用中却没有使用到也是会被拒的。

解决方案：

一定要注意自己的 App 在使用中用到了哪些权限，不要添加无用的权限，也不要缺少必要的权限。

应用提示更新被拒

应用内不能有任何提示更新应用的字样，且应用的更新只能通过 AppStore。因为苹果对于应用的更新有自己的一套策略，所以禁止应用本身提供更新方式，只要应用内出现。

解决方案：

如果不是很必要的话，尽量将应用内涉及到应用更新的部分去掉。如果真的需要使用应用更新，推荐的方法是应用启动的时候获取下应用在 AppStore上面的版本号，与自己的版本号进行比较，当自己的版本号小于 AppStore 上面的版本号时，提示更新，否则的话不显示更新相关的内容。

隐私条款问题被拒

在未获得用户事先允许，或未告知用户信息将被如何，在哪里使用的情况下，应用不可以传输用户数据。

解决方案：

《网站服务协议》《隐私条款》这些都不要少，注册时候让用户可勾选。另外注明需要的用户信息用来做什么。

未通过 HTTPS 访问被拒

App Transport Security(ATS) 是 Apple 为增强 iOS App 网络通信安全提出的安全功能，适用于iOS App 和 App Extension;在启用 ATS 之后，它会强制应用通过HTTPS(而不是 HTTP )连接网络服务。 WWDC 2016上提出，2016年底或2017年初，具体时间未定。App Store上架审核加强对ATS 配置的review，即强制应用必须通过HTTPS连接网络服务，而不是随手将NSAllowsArbitraryLoads置为 YES，否则审核不予通过。

解决方案:

ATS 的提出，是为了在系统层面保障iOS APP 网络通信的安全;Apple 只所以加强对ATS 配置的审核，是为了防止开发者们遇到ATS相关的场景时，只是简单地将 ATS完全关闭(只要没有强制性措施，开发者会这么做);在此基础上，App审核同样会遵循原则：App Review will require “reasonable justification” for most ATS exceptions。

Apple 官方给出的可以通过审核的声明 demo 如下：

1.必须使用第三方提供的服务，但是其没有支持 HTTPS;

2.必须通过域名连接到设备，但该设备不能支持安全连接;

3.必须展示不同来源的网页内容，但是不能基于 NSAllowsArbitraryLoadsInWebContent支持的类(UIWebView / WKWebView)实现;

4.载入加密的媒体资源并且其中不涉及个人信息。

由于 Apple 官方并没有给出 ATS 审核的完整说明，ATS 审核时什么才是合适合理的声明也没有明确的客观定义，以上 demo 描述仅能作为参照。

/ AppStore上架提示被驳回案例一 /

Dear Developer,

We identified one or more issues with a recent delivery for your app, “应用名称” 1.0.0 (1). Please correct the following issues, then upload again.

ITMS-90683: Missing Purpose String in Info.plist - Your app’s code references one or more APIs that access sensitive user data. The app’s Info.plist file should contain a NSMicrophoneUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn’t contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).

Though you are not required to fix the following issues, we wanted to make you aware of them:

ITMS-90078: Missing Push Notification Entitlement - Your app appears to register with the Apple Push Notification service, but the app signature’s entitlements do not include the ‘aps-environment’ entitlement. If your app uses the Apple Push Notification service, make sure your App ID is enabled for Push Notification in the Provisioning Portal, and resubmit after signing your app with a Distribution provisioning profile that includes the ‘aps-environment’ entitlement. Xcode does not automatically copy the aps-environment entitlement from provisioning profiles at build time. This behavior is intentional. To use this entitlement, either enable Push Notifications in the project editor’s Capabilities pane, or manually add the entitlement to your entitlements file. For more information, see https://developer.apple.com/library/content/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/HandlingRemoteNotifications.html#//apple_re

审核错误提示

需要在Info.plist 文件下面添加麦克风权限

NSSpeechRecognitionUsageDescription

App需要您的同意,才能访问语音识别

或者在Xcode工具里面进行添加

应用注册并申请了通知服务

需要在用Xcode打开的工程文件Runner.entitlements文件下配置 aps 环境

<?xml version="1.0" encoding="UTF-8"?>

aps-environment

development

配置完成后在Xcode编辑区域将会出现Push Notificaitions选项

/ AppStore上架提示被驳回案例二 /

App Store Connect

Dear Developer,

We identified one or more issues with a recent delivery for your app, “应用名称” 1.0.1 (2). Please correct the following issues, then upload again.

ITMS-90683: Missing Purpose String in Info.plist - Your app’s code references one or more APIs that access sensitive user data. The app’s Info.plist file should contain a NSContactsUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn’t contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).

ITMS-90683: Missing Purpose String in Info.plist - Your app’s code references one or more APIs that access sensitive user data. The app’s Info.plist file should contain a NSCalendarsUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn’t contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).

ITMS-90683: Missing Purpose String in Info.plist - Your app’s code references one or more APIs that access sensitive user data. The app’s Info.plist file should contain a NSBluetoothPeripheralUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn’t contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).

ITMS-90683: Missing Purpose String in Info.plist - Your app’s code references one or more APIs that access sensitive user data. The app’s Info.plist file should contain a NSHealthShareUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the library or SDK and request they release a version of their code that doesn’t contain the APIs. Learn more (https://developer.apple.com/documentation/uikit/core_app/protecting_the_user_s_privacy).

ITMS-90683: Missing Purpose String in Info.plist - Your app’s code references one or more APIs that access sensitive user data. The app’s Info.plist file should contain a NSHealthUpdateUsageDescription key with a user-facing purpose string explaining clearly and completely why your app needs the data. Starting Spring 2019, all apps submitted to the App Store that access user data are required to include a purpose string. If you’re using external libraries or SDKs, they may reference APIs that require a purpose string. While your app might not use these APIs, a purpose string is still required. You can contact the developer of the libra

审核错误提示

需要在Info.plist 文件下面添加麦克风权限

NSContactsUsageDescription 通讯录权限

NSCalendarsUsageDescription 日历权限

NSBluetoothPeripheralUsageDescription 蓝牙权限

NSMicrophoneUsageDescription 麦克风权限

NSHealthShareUsageDescription 健康分享

NSHealthUpdateUsageDescription 健康更新

自我介绍一下，小编13年上海交大毕业，曾经在小公司待过，也去过华为、OPPO等大厂，18年进入阿里一直到现在。

深知大多数初中级Android工程师，想要提升技能，往往是自己摸索成长或者是报班学习，但对于培训机构动则近万的学费，着实压力不小。自己不成体系的自学效果低效又漫长，而且极易碰到天花板技术停滞不前！

因此收集整理了一份《2024年Android移动开发全套学习资料》，初衷也很简单，就是希望能够帮助到想自学提升又不知道该从何学起的朋友，同时减轻大家的负担。

既有适合小白学习的零基础资料，也有适合3年以上经验的小伙伴深入学习提升的进阶课程，基本涵盖了95%以上Android开发知识点，真正体系化！

由于文件比较大，这里只是将部分目录截图出来，每个节点里面都包含大厂面经、学习笔记、源码讲义、实战项目、讲解视频，并且会持续更新！

如果你觉得这些内容对你有帮助，可以扫码获取！！（备注：Android）

总结

【Android 详细知识点思维脑图（技能树）】

我个人是做Android开发，已经有十来年了，目前在某创业公司任职CTO兼系统架构师。虽然 Android 没有前几年火热了，已经过去了会四大组件就能找到高薪职位的时代了。这只能说明 Android 中级以下的岗位饱和了，现在高级工程师还是比较缺少的，很多高级职位给的薪资真的特别高（钱多也不一定能找到合适的），所以努力让自己成为高级工程师才是最重要的。