踩坑記-Permission_handler

提交IOS時续挟,由于存在沒有使用到的權(quán)限代碼,導(dǎo)致APP上傳沒有通過系統(tǒng)檢查侥衬。

## 解決:

1诗祸,按照Permission handler 官方說明,修改Podfile中的 post_install轴总,禁用無用的權(quán)限代碼

2直颅,flutter clean

3,flutter build ios

=================================================

```

post_install do |installer|

? installer.pods_project.targets.each do |target|

? ? target.build_configurations.each do |config|

? ? ? config.build_settings['ENABLE_BITCODE'] = 'NO'

# Here are some configurations automatically generated by flutter # You can remove unused permissions here

? ? ? # for more infomation: https://github.com/BaseflowIT/flutter-permission-handler/blob/develop/ios/Classes/PermissionHandlerEnums.h

? ? ? # eg when you don't need camera permission, just add 'PERMISSION_CAMERA=0'

? ? ? config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= [ '$(inherited)',

? ? ? ## dart: PermissionGroup.calendar

? ? ? ? 'PERMISSION_EVENTS=0',

? ? ? ## dart: PermissionGroup.reminders

? ? ? ? 'PERMISSION_REMINDERS=0',

? ? ? ## dart: PermissionGroup.contacts

? ? ? ? 'PERMISSION_CONTACTS=0',

? ? ? ## dart: PermissionGroup.camera

? ? ? ? 'PERMISSION_CAMERA=0',

? ? ? ## dart: PermissionGroup.microphone

? ? ? ? 'PERMISSION_MICROPHONE=0',

? ? ? ## dart: PermissionGroup.speech

? ? ? ? 'PERMISSION_SPEECH_RECOGNIZER=0',

? ? ? ## dart: PermissionGroup.photos

? ? ? ? 'PERMISSION_PHOTOS=0',

? ? ? ## dart: [PermissionGroup.location, PermissionGroup.locationAlways, PermissionGroup.locationWhenInUse]

? ? ? ? 'PERMISSION_LOCATION=0',

? ? ? ## dart: PermissionGroup.notification

? ? ? ? 'PERMISSION_NOTIFICATIONS=0',

? ? ? ## dart: PermissionGroup.mediaLibrary

? ? ? ? 'PERMISSION_MEDIA_LIBRARY=0',

? ? ? ## dart: PermissionGroup.sensors

? ? ? ? 'PERMISSION_SENSORS=0' ]

? ? end

? end

end

```

=================================================

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 NSAppleMusicUsageDescription 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 NSMotionUsageDescription 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 NSSpeechRecognitionUsageDescription 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_ref/doc/uid/TP40008194-CH6-SW1.

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 NSLocationAlwaysUsageDescription 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 NSLocationWhenInUseUsageDescription 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).

Best regards,

The App Store Team

?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
  • 序言:七十年代末怀樟,一起剝皮案震驚了整個濱河市功偿,隨后出現(xiàn)的幾起案子,更是在濱河造成了極大的恐慌往堡,老刑警劉巖械荷,帶你破解...
    沈念sama閱讀 217,406評論 6 503
  • 序言:濱河連續(xù)發(fā)生了三起死亡事件,死亡現(xiàn)場離奇詭異虑灰,居然都是意外死亡养葵,警方通過查閱死者的電腦和手機(jī),發(fā)現(xiàn)死者居然都...
    沈念sama閱讀 92,732評論 3 393
  • 文/潘曉璐 我一進(jìn)店門瘩缆,熙熙樓的掌柜王于貴愁眉苦臉地迎上來关拒,“玉大人,你說我怎么就攤上這事∽虐恚” “怎么了谐算?”我有些...
    開封第一講書人閱讀 163,711評論 0 353
  • 文/不壞的土叔 我叫張陵,是天一觀的道長归露。 經(jīng)常有香客問我洲脂,道長,這世上最難降的妖魔是什么剧包? 我笑而不...
    開封第一講書人閱讀 58,380評論 1 293
  • 正文 為了忘掉前任恐锦,我火速辦了婚禮,結(jié)果婚禮上疆液,老公的妹妹穿的比我還像新娘一铅。我一直安慰自己,他們只是感情好堕油,可當(dāng)我...
    茶點故事閱讀 67,432評論 6 392
  • 文/花漫 我一把揭開白布潘飘。 她就那樣靜靜地躺著,像睡著了一般掉缺。 火紅的嫁衣襯著肌膚如雪卜录。 梳的紋絲不亂的頭發(fā)上,一...
    開封第一講書人閱讀 51,301評論 1 301
  • 那天眶明,我揣著相機(jī)與錄音艰毒,去河邊找鬼。 笑死搜囱,一個胖子當(dāng)著我的面吹牛丑瞧,可吹牛的內(nèi)容都是我干的。 我是一名探鬼主播犬辰,決...
    沈念sama閱讀 40,145評論 3 418
  • 文/蒼蘭香墨 我猛地睜開眼,長吁一口氣:“原來是場噩夢啊……” “哼冰单!你這毒婦竟也來了幌缝?” 一聲冷哼從身側(cè)響起,我...
    開封第一講書人閱讀 39,008評論 0 276
  • 序言:老撾萬榮一對情侶失蹤诫欠,失蹤者是張志新(化名)和其女友劉穎涵卵,沒想到半個月后,有當(dāng)?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體荒叼,經(jīng)...
    沈念sama閱讀 45,443評論 1 314
  • 正文 獨(dú)居荒郊野嶺守林人離奇死亡轿偎,尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內(nèi)容為張勛視角 年9月15日...
    茶點故事閱讀 37,649評論 3 334
  • 正文 我和宋清朗相戀三年,在試婚紗的時候發(fā)現(xiàn)自己被綠了被廓。 大學(xué)時的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片坏晦。...
    茶點故事閱讀 39,795評論 1 347
  • 序言:一個原本活蹦亂跳的男人離奇死亡,死狀恐怖,靈堂內(nèi)的尸體忽然破棺而出昆婿,到底是詐尸還是另有隱情球碉,我是刑警寧澤,帶...
    沈念sama閱讀 35,501評論 5 345
  • 正文 年R本政府宣布仓蛆,位于F島的核電站睁冬,受9級特大地震影響,放射性物質(zhì)發(fā)生泄漏看疙。R本人自食惡果不足惜豆拨,卻給世界環(huán)境...
    茶點故事閱讀 41,119評論 3 328
  • 文/蒙蒙 一、第九天 我趴在偏房一處隱蔽的房頂上張望能庆。 院中可真熱鬧施禾,春花似錦、人聲如沸相味。這莊子的主人今日做“春日...
    開封第一講書人閱讀 31,731評論 0 22
  • 文/蒼蘭香墨 我抬頭看了看天上的太陽丰涉。三九已至拓巧,卻和暖如春,著一層夾襖步出監(jiān)牢的瞬間一死,已是汗流浹背肛度。 一陣腳步聲響...
    開封第一講書人閱讀 32,865評論 1 269
  • 我被黑心中介騙來泰國打工, 沒想到剛下飛機(jī)就差點兒被人妖公主榨干…… 1. 我叫王不留投慈,地道東北人承耿。 一個月前我還...
    沈念sama閱讀 47,899評論 2 370
  • 正文 我出身青樓,卻偏偏與公主長得像伪煤,于是被迫代替她去往敵國和親加袋。 傳聞我的和親對象是個殘疾皇子,可洞房花燭夜當(dāng)晚...
    茶點故事閱讀 44,724評論 2 354

推薦閱讀更多精彩內(nèi)容