Huawei divides real machine debugging into physical real machine and remote real machine. What I'm talking about here are all physical real machines (mobile phones, tablets). The debugging of HarmonyOS system is extremely complicated, which is not as simple and convenient as Android.
Post the official debugging flow chart:
To sum up:
The above process can be ignored, not to the point. Is it necessary to debug the real machine? Cer and p7b files for creating and debugging applications in AppGallery Connect are generated from here.
Prerequisites:
1. The mobile phone of HarmonyOS system is connected to the computer through USB, and the USB is turned on for debugging.
2. A Huawei developer account with real-name authentication.
3. application development tool DevEco-Studio
Key processes:
1.Studio create an application.
2. if you haven't logged in, click "login" on the file > project structure & gt project & gt signature configuration page.
3.AppGallery creates an application (the package name is the same as that created by Studio).
4. When the official document is here, click Retry on the signature configuration page to automatically sign it. I tried, but it didn't work. The following are all manual.
5.Build > Generate key, csr generates p 12 and CSR file.
6. Get the mobile phone udid, and command line hdc shell bm get -udid (the next step is for device management).
7.AppGallery home page > users and access > devices on the left side manage devices added with udid (used when generating p7b).
8.AppGallery home page > users and access > Cer file generated by certificate management on the left (used to generate p7b and signature configuration)
9.AppGallery home page > my project > left HarmonyOS system application >: HAP provision profile, and generate p7b file.
10. Finally, match the parameters such as p 12, p7b and cer on the signature configuration page, and run the HarmonyOS system and apply it to the real machine.