iTunes Connect App Statuses

Table 9-1 iTunes Connect app statuses
Status Name	Description	Editable
Prepare For Upload	Appears as the first status for your app. This status means that you should enter or edit metadata, screenshots, pricing, In-App Purchases, Game Center, iAd Network settings, and so on, to prepare your app for upload to the App Store.	X
Waiting For Upload	Appears when you’ve completed entering your metadata and indicated that you are ready to submit your binary, however, you have not finished uploading your binary through Application Loader. Your app must be Waiting For Upload for you to be able to deliver your binary through Application Loader.	X
Waiting For Review	Appears after you submit a new app or update and before the app is reviewed by Apple. This status means that your app has been added to the app review queue but has not yet started the review process. Because it takes time to review binaries, keep in mind that this state does not indicate that your app is currently being reviewed. While your app is waiting for review, you can: Reject your binary to remove it from the Apple review queue Edit certain app information	X
In Review	Appears when Apple is currently reviewing your app before the app is rejected or approved. Note that it takes time to review binaries. We appreciate your patience and ask that you allow sufficient time for the processing of your app.
Pending Contract	Appears when your app has been reviewed and is ready for sale but your contracts are not yet in effect. You can check the progress of your contracts in the Contracts, Tax & Banking module. See“Managing Contracts, Taxes, and Banking.”
Waiting For Export Compliance	Appears when your CCATS file is in review with Export Compliance.	X
Upload Received	Appears when your binary has been received through Application Loader but has not yet completed processing into the iTunes Connect system. If your app has been in the Upload Received status for more than 24 hours, you should contact iTunes Connect Support through the iTunes Connect Contact Us module.	X
Pending Developer Release	Appears when your app version has been approved by Apple and you have chosen to set your version release control. Release it to the App Store when you are ready. To release your app to the App Store, click the Release This Version button on the app’s Version Details page within Manage Your Apps.
Processing for App Store	Appears when your binary is being processed and will be ready for sale within 24 hours.
Pending Apple Release	Appears when your app version will be held by Apple until the corresponding Apple iOS or OS version is released to the public.
Ready For Sale	Appears after the binary has been approved and the app is posted to the App Store. When your app is in this state, you have the option to remove it from the store by going to the “Rights and Pricing” page and removing all App Store territories. See “Removing an App from Sale.”
Rejected	Appears when the binary has not passed review. You receive a communication from App Review in the Resolution Center regarding the reason for the rejection.	X
Metadata Rejected	Appears when specific metadata items aside from your binary have not passed review. To resolve the issue, edit the metadata in iTunes Connect and your existing binary is then reused for the review process. You receive a communication from App Review in the Resolution Center regarding the reason for the metadata rejection.	X
Removed From Sale	Appears when your app has been removed from the App Store.
Developer Rejected	Appears when you’ve rejected the binary from the review process. Choosing the Developer Rejected status removes your app from the review queue. After you resubmit your binary, the app review process starts over from the beginning.	X
Developer Removed From Sale	Appears when you’ve removed the app from the App Store. See“Removing an App from Sale” and “Putting an App Back on Sale.”
Invalid Binary	Appears when your binary has been received through Application Loader but did not meet all requirements for upload. You receive an email detailing the issue with your binary and showing how to resolve it. To resend the resolved binary, go into iTunes Connect and click Ready to Upload Binary again. This action sets your app back to the Waiting For Upload state so that you can resend the binary through Application Loader.	X
Missing Screenshot	Available for iOS apps only. Appears when your app is missing a required screenshot for iPhone and iPod touch or iPad for your default language app or for your added localizations. At least one screenshot is required for both iPhone and iPod touch, and for iPad if you are submitting a universal app. Click the number next to the status to view a list of the territories in which a screenshot is missing.	X

Comments

Most Favorite Posts

Server-driven UI (SDUI): Meet Zalandos AppCraft and AirBnB Lona

A short WTF: Joe Birch: SERVER DRIVEN UI, PART 1: THE CONCEPT Zalando seems to follow the SDUI principle as well - defining a common design language and construct the screens on the backend while displaying them natively on the clients. They even go one step further; they implemented a mighty toolset to enable non-technical stakeholders to define their own native app screens Compass: Web tooling to create screens and bind data Beetroot: Backend service that combines the screen layout definition with the data Lapis/Golem: iOS/Android UI render engines Crazy cool! Good job, guys (when you do an open-source release?) To even move faster a Flutter based UI render engine implementation was great! See also AirBnB Lona SDUI approach Building a Visual Language Why Dropbox sunsetted its universal C++ mobile project and AirBnB its React Native implementation

Judo App - Server Driven UI out of the box

Judo App Judo brings server-driven UI to your iOS and Android apps. Build user interfaces visually in a fraction of time and publish them instantly without submitting to the app store. Build Experiences - With No Code The Judo app for macOS, available through the App Store, is built for design professionals with common keyboard shortcuts and familiar concepts like canvas, layers and inspector panel. Workflow is streamlined with the ability to drag and drop media files directly into your experiences and manage your own Judo files in Finder. Manage Creative Execution A Judo experience is interactive and can include text, images, video and buttons. An experience may be part of a screen, a single screen, or more typically multiple linked screens. Judo supports screen transitions, carousels, horizontal scrolling and modals. Clients can add custom fonts and define global colors and these are updates applied universally. Effortlessly Deploy Judo Cloud syncs your experiences with your iOS and

Dark Theme (Dark Mode) in Android WebViews, WKWebViews and CSS

So your apps just implemented a shiny new dark theme and it’s looking 👌 There are lots of benefits to having a dark theme in your application, and having it consistent throughout your application allows for a great user experience. But what happens when the the user runs into a WebView in your app? Support: if (WebViewFeature.isFeatureSupported(WebViewFeature.FORCE_DARK)) { ... } Set: WebSettingsCompat.setForceDark(webView.settings, WebSettingsCompat.FORCE_DARK_ON) Current setting: val forceDarkMode = WebSettingsCompat.getForceDark(webView.settings) Joe Birch Assuming your question is asking how to change the colors of the HTML content you are displaying in a WKWebView based on whether light or dark mode is in effect, there is nothing you do in your app's code. All changes need to be in the CSS being used by your HTML content. CSS dark mode via :root variables, explicit colors and @media query: :root { color-scheme: light dark; --h1-color: #333;

Backend-driven native UIs

Backend-drive native UIs John Sundell Slide Share Using Back-End Design to Create Customizable Front-End Mobile Experiences By controlling the front end of mobile apps from the back end we can build customized experiences at runtime, creating cleaner interfaces and reducing load times. Nithin Rao UX Magazine The Hub Framework Welcome to the Hub Framework - a toolkit for building native, component-driven UIs on iOS ( no Android support released yet ). It is designed to enable teams of any size to quickly build, tweak and ship new UI features, in either new or existing apps. It also makes it easy to build backend-driven UIs. The Hub Framework has two core concepts - Components & Content Operations. Spotify LeeGo: Build UI without UIView LeeGo is a lightweight Swift framework that helps you decouple & modularise your UI component into small pieces of LEGO style's bricks, to make UI development declarative, configurable and highly reusable. Wang Sheng Jia

netfox - A lightweight, one line setup, iOS network debugging library!

A lightweight, one line setup, network debugging library that provides a quick look on all executed network requests performed by your app. It grabs all requests - of course yours, requests from 3rd party libraries (such as AFNetworking, Alamofire or else), UIWebViews, and more Very useful and handy for network related issues and bugs Implemented in Swift 2.1 - bridged also for Objective-C Start To start netfox add the following line in didFinishLaunchingWithOptions: method of your AppDelegate Swift NFX.sharedInstance().start() Invoke netfox UI Just shake your device and check what's going right or wrong! Shake again and go back to your app! GitHub kasketis/netfox

ImageOptim

ImageOptim optimizes images — so they take up less disk space and load faster — by finding best compression parameters and by removing unnecessary comments and color profiles. It handles PNG, JPEG and GIF animations. ImageOptim seamlessly integrates various optimisation tools: PNGOUT, AdvPNG, Pngcrush, extended OptiPNG, JpegOptim, jpegrescan, jpegtran, and Gifsicle. It solves too the Xcode bug: corrupt PNG file. ImageOptim

KSCrash

Another crash reporter? Why? Because all existing solutions fall short. PLCrashReporter comes very close, but not quite: It can't handle stack overflow crashes. It doesn't fill in all fields for its Apple crash reports. It can't symbolicate on the device. It only records enough information for an Apple crash report, though there is plenty of extra useful information to be gathered! As well, each crash reporter service, though most of them use PLCrashReporter at the core, has its own format and API. KSCrash is superior for the following reasons: It catches ALL crashes. Its pluggable server reporting architecture makes it easy to adapt to any API service (it already supports Hockey and Quincy and sending via email, with more to come!). It supports symbolicating on the device. It records more information about the system and crash than any other crash reporter. It is the only crash reporter capable of creating a 100% complete Apple crash report (including thre

iOS & Android Development

Search This Blog