uni-app Huawei offline push Assist_HW: get hms token failed:6003: certificate fingerprint error

uni-app offline push can not get Device Token, Android offline push can not receive messages

Due to business requirements, the app needs Huawei offline push, and Huawei offline push needs to configure the app certificate fingerprint signature SHA256
uni-app official also provides the corresponding Huawei offline push document. After the process of the official document is completed, the SHA256 signature can indeed be generated. ,
but still can't receive offline push messages when testing the custom packaging base

6003 means the certificate thumbprint is wrong

If it is created according to the process on the official website document, it is actually a new app and a new certificate.
However, because the current application certificate is already available before the app is developed, it should actually obtain the fingerprint of the current application certificate
. Solution:

1. Find the Android certificate used when packaging the current app
2. View the certificate fingerprint information of the current certificate (for details, you can search on Baidu: Android obtains the fingerprint information of the signature certificate and other keywords to find the method of obtaining certificate information)
3. Here is obtained through the keytook of javajdk, as shown in the figure:
4. Add the fingerprint of the current certificate, save and download the latest agconnect-services.json file
5. 
6. Log in to the dcloud background to upload the latest agconnect-services.json file and click Save
   7.
7. Add the obtained SHA1 certificate fingerprint to: androld application signature
8. 
9. After saving successfully, repackage a custom base to get the latest clientid
   10. Enter clientid in troubleshooting, if you can get Device Token, it means success