When I integrate the HMS Core SDK into my app or game, result code 6003 is
always returned during an API call. The official document indicates that this fault is caused by an incorrect signing certificate fingerprint. But I have checked that the app's certificate signature is the same as that configured in AppGallery Connect.
Official document
Step 1: Ensure that the app's certificate signature is the same as that configured in AppGallery Connect.
Open the APK file of the app, extract the META-INF directory from the file, obtain the CERT.RSA file in the directory, and run the keytool -printcert -file META-INF/CERT.RSA command to display the signature certificate information.
Check the SHA-256 certificate fingerprint configured in AppGallery Connect by referring to Configuring the Signing Certificate Fingerprint. If the information is the same as the preceding information displayed, the certificate fingerprint is correct.
Step 2: Ensure that the appid parameter in the manifest file is correct.
You can perform the check in either of the following ways:
• View the parameter directly in the manifest file under the project.
• Decompile the packaged APK file, and view the parameter. You can use any decompliation tool for that.
Step 3: Check whether the app is hardened or re-signed.
Since AppGallery Connect does not re-sign an app currently, you need to locate the fault if your app has been hardened or re-signed by yourself.
Step 4: Check whether HUAWEI App Signing is enabled.
Huawei provides the App Signing service for developers to let Huawei host their app's signature key and use it for the APK file to be distributed.
According to the official document, if the service is enabled, the generated certificate fingerprint must be added in AppGallery Connect.
Related
I tried to build new apk file of my app, but got error
What went wrong:
Execution failed for task ':app:validateSigningRelease'.
Keystore file not set for signing config release
previous version of my app that don't have purchases was build correctly but right now it's dosen't.
I found a lot informations how to set KeyStore file but nothing about what is it.
May you explain what is it
Basically Keystore is used to store private key and identity certificates that a specific program should present to both parties (server or client) for verification.
The Android Keystore system lets you store cryptographic keys in a container to make it more difficult to extract from the device. Once keys are in the keystore, they can be used for cryptographic operations with the key material remaining non-exportable. Moreover, it offers facilities to restrict when and how keys can be used, such as requiring user authentication for key use or restricting keys to be used only in certain cryptographic modes. See Security Features section for more information.
The Keystore system is used by the KeyChain API, introduced in Android 4.0 (API level 14); the Android Keystore provider feature, introduced in Android 4.3 (API level 18); and the Security library, available as part of Jetpack. This document goes over when and how to use the Android Keystore provider.
For details information please refer to this -
https://developer.android.com/training/articles/keystore
Even though I used last sdk, Huawei sign failed with status code 28. What causes this error?
Error 6003 indicates that this fault is caused by an incorrect signing certificate fingerprint.
You could:
Ensure that the app’s certificate signature is the same as that configured in AppGallery Connect.
.Open the APK file of the app, extract the META-INF directory from the
file, obtain the CERT.RSA file in the directory, and run the keytool
-printcert -file META-INF/CERT.RSA command to display the signature certificate information.
.Check the SHA-256 certificate fingerprint configured in AppGallery
Connect by referring to Configuring the Signing Certificate
Fingerprint. If the information is the same as the preceding
information displayed, the certificate fingerprint is correct.
2.Ensure that the appid parameter in the manifest file is correct.
You can perform the check in either of the following ways: View the
parameter directly in the manifest file under the project. Decompile
the packaged APK file, and view the parameter. You can use any
decompliation tool for that.
Check whether the app is hardened or re-signed.
Check whether HUAWEI App Signing is enabled. According to the official document, if the service is enabled, the generated certificate fingerprint must be added in AppGallery Connect.
About Error Code 6003, you are advised to check whether the appid is the same as the appid on AppGalleryConnect.
Ensure that the certificate fingerprint has been configured, and the certificate for packing the signature on the local client is the same as the certificate for configuring the fingerprint in AppGallery Connect. And the JSON file is stored in the project-level directory instead of the application-level directory, check the following items configuration process carefully.
1.Check whether the fingerprint certificate is correctly configured when you apply for related services. Open the APK file of an app, extract the META-INF directory from the file, obtain the CERT.RSA file in the directory, and run the keytool -printcert -file META-INF/CERT.RSA command to print the signature certificate information.
2.HMS Core (APK) will cache the signature file. You need to find HMS Core (APK) on the Apps page of your device and clear its cache, restart your app, and perform the previous operation again.
3.Sign in to AppGallery Connect, click My apps. On the page that is displayed, go to Develop > Project settings > conventional, check whether SHA-256 certificate fingerprint is consistent with the fingerprint in step 1.
Firstly, I made an app with flutter, I just implement Account Kit and Scan Kit for the app. Well, I got a previous bug for using google pixel 3XL (AVD) API Level 30, then I tried to change it to Nexus 6 API Level 28, and it worked (the latest version of HMS Core on both AVD). After I tried to run the application on my phone(Poco F1, using HMS Core Playstore Version), I found a bug like the following picture
But when I use the latest version of HMS Core, the bug is gone. Well, the problem it's not that much but when I submit the app to HMS Gallery, the reviewer found the bug and rejected my application proposal because he found an error message like the picture above, even though I already gave a note to use the latest HMS Core. But I don't think he read my note and it's like he doesn't understand the language(Indonesia) used in my application so he takes issue with the system that we have made, even though the application system that we made is like that.
.
Error Log - Huawei Sign In (Playstore Version HMS Core):
https://ghostbin.com/paste/wEqL4
.
note for reviewer:
https://ghostbin.com/paste/4ok59
.
attachment from reviewer:
https://obs.cn-north-2.myhuaweicloud.cn/nsp-appgallery-agcpri-drcn/application/errorFile/aff0e965b82548b2b7d180fc6cf31594.zip?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=MPXW6JOQOEGGIVNZK2PN%2F20210803%2Fcn-north-2%2Fs3%2Faws4_request&X-Amz-Date=20210803T162548Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=5dddb41e3a17cca9b50db3a8e55e14602e0035d9cfe3a58d6c7916ace344df76
.
Comment from the reviewer:
[Description]: An error occurs in your App). Please see the attachment， here is the path: Go to Console > App Service > AppGallery Connect>Find your app from the list and click the version to check the attachment. Please refer to rule 3.1 of "AppGallery Review Guidelines": https://developer.huawei.com/consumer/en/doc/distribution/app/50104 [Test Step]: 1. When clicking on "Sign in with Huawei ID", an error message pops up. 2. When login in using the admin test account, a QR code appears and prompts "scan me", but there is no scanning function. [Test Environment]: Wi-Fi connection, EMUI 10.1.0 (Mate 30), EMUI10.0.0（P20 pro） Multilingual settings. [Suggestion]: Please identify it accordingly. Then revise and resubmit your app for review.
.
I've made a demo video for this threat, please check this
https://youtu.be/fPJgaHQTXoY
App:
https://drive.google.com/drive/folders/1KPJrmjGTWRGHNecqDI1Hs6-zuDJflBw3?usp=sharing
Please help me how can I submit this app
Update
In the pics that you provided, we found a configuration issue.
SigningConfigs can contain debug or release.
so you can try to change here
to
In the screen recording that you provided, Error code 6003 is displayed.
To solve your issue, You need to check whether the certificate fingerprint of the APK signature file submitted to the AppGallery is the same as that configured on the AppGallery Connect website:
Ensure that the device and cloud configurations of the certificate fingerprint are consistent. The certificate packaged by the client application is the same as the SHA256 certificate fingerprint configured for the application on the AppGallery Connect website.
Verify that the certificate fingerprint is correctly configured when you apply for related services. Open the APK file of an app, extract the META-INF directory from the file, obtain the CERT.RSA file in the directory, and run the keytool -printcert -file META-INF/CERT.RSA command to record the signing certificate information.
Sign in to AppGallery Connect, click My projects, and select a required project. On the displayed page, select the app, go to Project settings > General information, and check whether the value in SHA-256 certificate fingerprint is the same as that in step 1.
In addition, HMS Core (APK) will cache the signature file. You need to find HMS Core (APK) on the Apps page of your device and clear its cache, restart your app, and perform the previous operation again.
I have a problem getting the signing certificate fingerprint for my Android app for the communication between phone and Huawei GT2 Pro that is a HarmonyOS watch. I follow the instruction of Wear Engine SDK integration process at the Huawei developer website (https://developer.huawei.com/consumer/en/doc/development/connectivity-Guides/service-introduction-0000000000018585) to develop my app on both phone and watch. However, it is not very clear to me how to generate the signing certificate fingerprint. Can someone help to describe the process?
Assume you are at the debug stage. You need use the debug certificate, i.e., the .cer certificate that you obtain in AppGallery Connect (AGC) to generate the signing certificate fingerprint. Here is the procedure:
Step 1 – use Huawei DevEco Studio to generate a key store (in p12 format) and a certificate signing request file (.csr);
Step 2- login your Huawei account on AGC, and use the .csr file to apply and download the debug .cer certificate file from the Certificate management that is under the Users and permissions on AGC;
Step 3 – open the .cer file and copy information in the last paragraph to the new text .cer file, and then open the new .cer file and click Details, then Public key to obtain the pubKey;
Step 4 - use a 3rd party online tool tomeko.net to encode the pubKey to base64 format, finally the base64Encode(pubKey) is the signing certificate fingerprint. You can find the detail of pubKey and base64 generation in https://developer.huawei.com/consumer/en/doc/development/connectivity-Guides/signature-0000001053969657.
I have created a new iPhone application.I have two mach machines. I have created the certificate for running application in iPhone in one mac. Can I use the other mac for running the application in iPhone. But when I try to do so I get an error "Codesign error:Code signing is required for product type "Application" in SDK Device iPhone OS 3.1.2. Please some one help me.
Regards,
krishnan.
Have you transferred your credentials to the second Mac? They are stored in your keychain.
You may need to read up on how Code-signing works: http://en.wikipedia.org/wiki/Code_signing
Here's an overview:
Developer creates a Certificate via a Certificate Authority (CA)
This certificate is used to 'sign' the binary, providing 'proof' of who created it
Developer then uses the Certificate to sign the binary (this is the step you're missing on the second MAC)
This is handled via xcode, assuming you've followed the detailed steps on http://developer.apple.com/iphone
Clients using the binary can now verify the Certificate against a known CA to ensure the integrity of the build.
Also check that you are code signing on the target as well when you do the Archive build
Spent hours to figure this out. Actually you need to click on Project --> Build Settings --> click target --> code sign..
THIS IS not apparent