app-store

来源： https://stackoverflow.com/questions/60637731/uploading-flutter-app-to-appstore-gives-app-framework-does-not-support-the-minim

来源： https://stackoverflow.com/questions/61755334/screenshot-quality-on-google-play-store-via-app-getting-compressed-blurry-and

问题 I have many versions on TestFlight uploaded (e.g., 1.7.1, 1.7.2, etc.). Now I want to upload the app to App Store with version 1.0, so if I select the version from TestFlight, e.g. version 1.7.1, which version will appear on App Store? I am thinking that above the image description is valid when you directly upload the app from Xcode. But due to this, I got some confusion. 回答1: Make sure version of the build and version you are creating on App Store both are same. It will show with version

问题 In my Xamarin iOS project, Entitlements.plist has aps-environment set to development , for dev testing purposes. I'm using the Visual Studio Team Services Extension for the App Store to automate publishing builds to TestFlight. However, when it uses fastlane pilot to upload the app, I get this error: ERROR ITMS-90046: "Invalid Code Signing Entitlements. Your application bundle's signature contains code signing entitlements that are not supported on iOS. Specifically, value 'development' for

问题 This might have been asked lots of times, but still I couldn't find info on why are they needed. I use DEVELOPER prov profiles to test apps on my device, that makes sense. The Provisioning Portal explains prov profiles like this: A Provisioning Profile is a collection of digital assets that uniquely ties developers and devices to an authorized iOS Development Team and enables a device to be used for testing. By this logic they are only needed for testing, eg not for distribution. Do we need

问题 We are going to upload new version of our app to iOS App Store. For previos version CFBundleShortVersionString was "1.9.2" and CFBundleVersion was "1.92.0". For current version we are going to use CFBundleShortVersionString :"1.10" and CFBundleVersion :"1.100.0". But we afraid if App Store won't detect our 1.10 version as new. Won't it be recognized as older than previos version with CFBundleVersion:"1.92.0". In other words, is CFBundleVersion :"1.100.0" will be higher than CFBundleVersion :

问题 We are going to upload new version of our app to iOS App Store. For previos version CFBundleShortVersionString was "1.9.2" and CFBundleVersion was "1.92.0". For current version we are going to use CFBundleShortVersionString :"1.10" and CFBundleVersion :"1.100.0". But we afraid if App Store won't detect our 1.10 version as new. Won't it be recognized as older than previos version with CFBundleVersion:"1.92.0". In other words, is CFBundleVersion :"1.100.0" will be higher than CFBundleVersion :

问题 I'm having a hard time finding any info on this. Android themselves mention code obfuscation as something to do before submitting to their store. But I see nothing about this from Apple or from any "third party" before-submission checklists. The only similar question I could find was one 5 years ago about Objective-C, and I only can find 1 github library about iOS obfuscation. Is it a common practice to obfuscate Swift code when submitting to the Apple App Store? Especially to hide any

问题 I'm having a hard time finding any info on this. Android themselves mention code obfuscation as something to do before submitting to their store. But I see nothing about this from Apple or from any "third party" before-submission checklists. The only similar question I could find was one 5 years ago about Objective-C, and I only can find 1 github library about iOS obfuscation. Is it a common practice to obfuscate Swift code when submitting to the Apple App Store? Especially to hide any

问题 ITMS-90809: Deprecated API Usage - Apple will no longer accept submissions of new apps that use UIWebView as of April 30, 2020 and app updates that use UIWebView as of December 2020. Instead, use WKWebView for improved security and reliability. I am trying to update an existing app, not a new app. Still I am not able to upload the app. I got this error via email: We identified one or more issues with a recent delivery for your app, "App Name" 20202.421.1 (6). Please correct the following