1. Apply for a certificate
1.1. Android Certificate
Android certificate application is very simple, directly click the link below and fill in the content as required
Android certificate online production tool
It should be noted that some modules require you to provide the SHA1 value, which bloggers are required to provide when applying for the Amap API, and Autonavi itself provides the method to obtain it (click on the portal).
However, the method provided by Autonavi basically requires relevant environment, which is not very friendly to bloggers who are not traditional Android developers. After asking our Android development colleagues for help, we got a more convenient method:
Download and install apK via the link below. Open ApK to find your own app and see the relevant information
Link: pan.baidu.com/s/1uj0hkVBC… Extraction code: LFJE
1.2. IOS Certificates
When it comes to ios, as long as you have a Mac, it’s all very well, but obviously I don’t have a poor blogger, so I had to find a new path. Fortunately, there are plenty of people who have explored the path for me.
Process for creating an Apple certificate for a Windows PC
I got the tutorial from my colleague in APP development of the company. However, there are some imperfections in the tutorial. I will make some supplements below.
When creating a development environment certificate, you must select the device for debugging; otherwise, debugging will fail. In this case, you need to create a test device in advance and obtain the UDID by clicking jump
2, packaging,
2.1 android packaging
HbuilderX– Launch — Native App — Cloud packaging
2.2 iOS packaging
HbuilderX– Launch — Native App — Cloud packaging
2.3. Hot change bag
HbuilderX– Launch — Native App — Build App WGT pack
The WGT package is used for online hot updates and needs to be used in conjunction with the back end, which will continue to be updated later in the hot update tutorial.
3, debugging,
Official document portal
3.1. Custom base
Custom docks are not normally required, but they may be needed if you use native plug-ins in your project or if you use third-party SDKS (such as wechat Pay) that validate client information.
How to make a custom base:
HbuilderX– Run — Run to phone or emulator — make custom debug dock
The following steps are basically the same as the packaging steps, so I won’t repeat them here, except that you need to switch the “formal package” option to “Custom debug Base”.
Note when creating the IOS custom dock, you need to select the certificate and description file of the development environment, and select the device for debugging when generating the description file. Otherwise, debugging will fail
3.2 Android debugging records
① WebView debugging console: you can view dom like a browser to view a web page, you can see the style, for solving some strange style problems have magic effect; Location: Run — run to phone or emulator — display the Webview debug console
(2) the adb path
The blogger encountered a very weird problem that did not appear on any other computer, take a note
When the mobile phone is connected, the trust popup window cannot be displayed, and the following error is reported during operation
After much searching, it was found that adb was the problem, so I downloaded a new ADB (ADB download address), changed the ADB path (run — run to mobile phone or emulator –ADB path Settings), sure enough, the trust popup window popped up and successfully installed the application on the mobile phone.
But at the same time, it also introduces a new problem: running error, and can not hot update during debugging.
It is still adb’s problem, but I could not find a solution for a long time, so I used a solution that could not be solved:
When using third-party ADB to set up the trust popup, check the permanent trust option, after the trust, change the ADB path back to the default path, that is, the empty path, you can happy to start hot update debugging. This method palliative, every time change mobile phone and have to operate again, there is a real solution to tell the brothers.