Expo battle (19th) -- after expo is packed, release the sub-app to the store. Note: expo -- expo

Expo battle (19th) -- after expo is packed, release the sub-app to the store. Note: expo -- expo

Summary: this series of articles will give a comprehensive introduction to expo. Since I started to contact expo in May, my research on expo has been intermittent and has been around for nearly 10 months, next, let's talk about the content on the official website.
I guess I will go to the full machine flip + personal modification supplement + demo test form to perform a big blood test on the expo! Welcome to the expo interest learning exchange group: 597732981
[I have previously written some columns about the East I west of the expo and rn entry configuration. You can click here to view: learn from scratch rn Development]
Related Articles:
Expo (1) -- What is expo, how to install expo clinet and xde, and how to use xde
Expo (2) -- expo life cycle, expo community communication mode, expo learning essential resources, issues of concern when developing and using expo
Expo (III)-Introduction to expo and expo limitations and precautions for project selection during development to developers who have already developed react native projects
Expo (4)-quickly build an app with expo, key terms in expo
Expo (5) -- configuration information of app. json file in expo
Expo big battle (6) -- expo development mode, expo exp command line tool, expo how to view log, expo debugging method
Expo (7) -- how expo uses Genymotion Simulator
Expo (8)-publish in expo and link in expo. You can come and talk to me about link.
More>
Next we will start the verification code.
 Deploy to App Store
This Guide provides best practices for submitting your expo application to Apple iTunes Store and Google Play Store. To learn how to generate a local binary file for submission, see build an independent application.
Although you can use Expo Client and expo. i/O personal data is shared with published projects, but submitting independent applications to Apple and Google stores is essential for having dedicated real estate projects on users' devices. Submitting to these stores has higher requirements and quality standards than sharing toy projects with several of your friends, as it gives your applications access through a wider distribution platform.
Disclaimer: especially for Apple, review guidelines and rules are constantly changing, while Apple's execution of various rules is often picky and inconsistent. We cannot guarantee that your specific project will be accepted by any platform, and you are ultimately responsible for your application's behavior. However, the expo application is a local application, and its behavior is the same as that of any other application, so if you create some great applications, don't worry!
Make sure that your application is valid for many form factors (Make sure your app works on terraform factors)
It is a good idea to test your applications on devices or small screen simulators (such as iPhone SE) and large screens (such as iPhone X. Make sure that your components are displayed as expected, no buttons are blocked, and all text fields are accessible.
In addition to mobile phones, you can also try your apps on your tablet. Even if you have ios. supportsTablet: Set to false, your application will still be displayed on the mobile resolution of iPads and must be available. (Test application compatibility before deployment)
Seamless application loading
 
 

  
  
Add a startup screen. This is the first thing you can see after selecting an application.
  
  
AppLoading ensures that your interface is ready before the user sees it.
  
  
Even if the Internet connection is poor, you can pre-load and cache resources to quickly load applications.
 
 
Play nicely with the system UI)
 
 

  
  
Configure the status bar so that it does not conflict with your interface.
  
  
Use native gestures whenever possible.
  
  
Use meaningful interface elements on the device. For example, see the iOS Man-Machine Interface Guide.
 
 
Note: The text color of the status bar is white by default for iOS independent apps. However, when developing an expo application, because the expo application itself has a black status bar, it is set to black by default. Users are often surprised that their independent applications suddenly show a white status bar. To keep the color black, use the <StatusBar barStyle = "dark-content"/> component. For more information, see the StatusBar documentation.
Customize your app metadata (Tailor your app metadata)
 
 

  
  
Add a great icon. The icons between iOS and Android have different requirements and are quite strict. Therefore, be familiar with this guide.
  
  
Customize your primaryColor.
  
  
Make sure that your application has a valid iOS Bundle Identifier and Android package (Make sure your app has a valid iOS Bundle Identifier and Android Package ). Please select these carefully because you will not be able to change them in the future.
  
  
VersionCode and buildNumber are used to distinguish different binary files of an application.
 
 
IOS-specific guide
 
 

  
  
All applications in iTunes Store must comply with the App Store comment guide.
  
  
It is helpful to browse common application rejection.
  
  
Incorrect icons cause the binary file to be rejected. Therefore, check the application icon Guide carefully.
  
  
Even if your app does not have an influence on the appearance of the iPad, if the elements cannot be normally displayed on the iPad, Apple will reject your app. Make sure to test your application on the iPad (or iPad simulator.
  
  
Apple will ask if your application uses IDFA. Because expo depends on Subdivision analysis, the answer is yes. You need to check several boxes on the Apple submission form. Refer to the "subdivision Guide" to learn which boxes you want to enter.
 
 
System permissions dialogs on iOS)
If your application requests system permissions to users, such as using the camera of the device, accessing photos or sending notifications, Apple needs to explain how your application uses the data. Expo automatically provides you with a sample reason, such as "allow cool-app to access the camera ". If you want to provide more information, you can use the ios. infoPlist key in app. json to overwrite these values. For example:
"infoPlist": {  "NSCameraUsageDescription": "This app uses the camera to scan barcodes on event tickets."},
The complete list of expo keys provided by default is displayed. You can provide any overwrites you want in the infoPlist configuration. Because these strings are configured locally, they are published only when you build new binary files using exp build.
 
Next, let's continue with the introduction. This article mainly introduces the precautions for releasing the sub-app to the store after expo is packaged. You are welcome to pay attention to my public account. Is this article accepted? My metric is public
The number of followers increases. You are welcome to repost it, but you must keep your blog link!
 
Category: Expo