1. The base library must be carefully confirmed.

1 whether the development of small program or enterprise micro channel small program for the basic library must carefully see, especially the enterprise micro channel is currently the highest base library. The basic library of enterprise wechat is automatically upgraded, and will be upgraded every few months, which is not consistent with the highest basic library of wechat small program. For example, if there is a drop-down refresh operation, if the base library is lower than 2.1.0, the scroll view cannot be used.

2. Enterprise Micro releases the beta version.

1. Different from normal submission and release, the developer needs to scan the code to distribute the experience version on the phone.

3.CDN environmental control.

Because the small program package has a size limit, so the pictures should be stored separately on the server, most of the pictures given by UI are not compressed, you can first compress TinyPng here, as for the CDN picture address how to distinguish online and test environment, the current solution has the following:

  • 1: All pictures are not used<img src="XXX">All defined in background-URL, so that you can configure a separate webpackpublicPath, and then packaged to modify according to environment variablesCDNThe global address will do.
  • 2. Use VSCode to change the global address to an official address when going online.
  • 3. Define the URL of PB environment and the URL of online environment, add this URL to each picture using CDN. Url must configure global mixins, and each file should introduce this mixins..
  • 4. To be determined

4. The address book component is faulty

  • Wx-open-data: < wx-open-data > < wx-open-data > < wx-open-data > < wx-open-data > < wx-open-data > < wx-open-data > < wx-open-data > {}}.

  • 2. The address book component will call the interface itself, so there will be a delay in returning. The loading time can be slightly longer.

  • 3. Paging is not recommended for the address book component because the return callback time is uncertain.

5. System compatibility.

  • 1. IOS and Android are mainly distinguished. Currently, in addition to some native apis of devices (such as Bluetooth, WIFI, NFC, etc.), there are obvious differences between themflex-growThe support of thesrcoll-viewThe component is not very friendly, and there are often scrolling exceptions. If confirmedsrcoll-viewThen there will be no problem.

6. Login

  • 1. Applets login process Authorization -> get code -> Get accessToken with code -> Complete login

  • 2. AccessToken failure, which can be divided into two ways

  1. Log in again, jump to the home page.. Returns the corresponding in case of an interface failurecodeAfter, do a function in time to shake, login after jump to the home page
  2. Log in again and log in to the current page.. Every page that executes onload/onShow etc. immediately after entering the page must be executed with async await and then checked in the interceptor to see if it is invalid. If it fails, log in again and request the failed interface again after login.

7. Bind service domain names

  • To use web-view, you must bind the relevant business domain name, if your web-view is embeddediframe, must also bind the correspondingiframeThe domain name.

8. Enterprise micro small program release process

  • Upload code -> submit for review (note: only used in enterprise Micro) -> Review failure, prompting to ask the specialist to solve -> Upload small program using video /5 pictures -> upload success

9.