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.
Related
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.
This is the full error-message:
Cannot show Automatic Strong Passwords for app bundleID: com.ckbusiness.Wishlists due to error: Cannot identify the calling
app's process. Check teamID and bundleID in your app's
application-identifier entitlement
What am I missing here??
We have the same issue with Xcode 12.2 and iOS 14.2 and applied more details on the Apple Developer forum.
Can this be related? The documentation of the Associated Domain File shows a new section at the bottom about macOS 11 and iOS 14:
Starting with macOS 11 and iOS 14, apps no longer send requests for apple-app-site-association files directly to your web server. Instead, they send these requests to an Apple-managed content delivery network (CDN) dedicated to associated domains.
Update - December 3:
We checked many things:
Code signing
Our target is set to "Automatically managing signing".
In App Store connect we looked up the the entitlement:
Select app
Select "Activity"
Select a Build
Scroll down to "Store Information", the right column shows the Entitlements.
The com.apple.developer.team-identifier matches the prefix in the application-identifier. The latter matches exactly with the value in the apps array in the apple-app-site-association file on our website.
However, when performing Build & Run with Xcode on device, the debug app is signed with a different Signing Identity:
Apple Development: (other ID than com.apple.developer.team-identifier)
An estimated guess is that this would create a mismatch with the apple-app-site-association file. Hence we added this new id to the existing apple-app-site-association file and uploaded on our server:
{
"webcredentials": {
"apps": ["ABCDEF1234.com.domain.appName", // Release ID from App Store
"1234ABCDEF.com.domain.appName"] // Debug ID from Xcode
}
}
Tried again, still the same error.
Also performed the usual stuff like:
Uninstall app from iPhone and reboot iPhone
Clean Build Folder in Xcode
Delete Xcode folder DerivedData from /Users/xxx/Library/Developer/Xcode and rebooted MacBook
Availability of apple-app-site-association file
While updating this file on our server, we found a docu update. In June 2019 (when we launched this particular app) it mentions to place the file in 2 folders:
https://<fully qualified domain>/apple-app-site-association
https://<fully qualified domain>/.well-known/apple-app-site-association
Note: Currently only the later .well-known directory is mentioned.
It appeared that our file was only in the first folder. So we duplicated it and checked again, but still the error is shown.
To rule out that it takes time for iOS 14 to update changes of the apple-app-site-association file based on the new Apple-managed content delivery network (CDN), we even used the mode option in the entitlements file:
While you’re developing your app, if your web server is unreachable from the public internet, you can use the alternate mode feature to bypass the CDN and connect directly to your private domain.
You enable an alternate mode by adding a query string to your associated domain’s entitlement as follows:
webcredentials:doamin.com?mode=developer
Again, no luck.
TestFlight version
To avoid using Xcode debugger and it's debug signing, archived the Xcode 12.2 build and submitted it to App Store. Verified the entitlements from the build in App Store Connect as described above. They match the apple-app-site-association file.
Released for internal TestFlight testing and tested on device. Tapping the first password text field does not show the password suggestion.
Conclusion
Although we seem out of options, hopefully any of these exercises can inspire others to identify a solution. Or it's just a massive Apple bug and we need to wait for a fix from them.
Work again in Version 13.0 beta (13A5155e) !
I'm trying to upload an app to app store, and I'm getting a lot of trouble.
Now I received this email:
Dear developer,
We have discovered one or more issues with your recent delivery for "usualBike". To process your delivery, the following issues must be corrected:
Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported. Please check your Xcode project's code signing entitlements configuration, and remove any unneeded entitlements.
Specifically, key "com.apple.developer.default-data-protection" is not supported.
Invalid Code Signing Entitlements - Your application bundle's signature contains code signing entitlements that are not supported. Please check your Xcode project's code signing entitlements configuration, and remove any unneeded entitlements.
Specifically, key "com.apple.developer.pass-type-identifiers" is not supported.
Once these issues have been corrected, go to the Version Details page and click "Ready to Upload Binary." Continue through the submission process until the app status is "Waiting for Upload." You can then deliver the corrected binary.
Regards,
The App Store team
The second one I found this:
Invalid binary in itunes connect
But i have iOS 5.1
This probably means that you have Data Protection and Passes enabled for your App ID in the iOS provisioning portal. This is not supported for iOS 5.1
You should disable this by:
Going to the iOS provisioning portal
Open the App ID tab
Click configure next to the App ID you're currently using
Unselect the Enable for Passes and Enable for Data Protection options
Redownload the provision for your application and rebuild it using this new provision.
I signed up for TestFlight.
Then I followed all steps in this tutorial:
But Xcode throws this warning:
Application failed codesign verification. The signature was invalid,
contains disallowed entitlements, or it was not signed with an iPhone
Distribution Certificate. (-19011)
It smells like there is a lot more work to do than what they wrote in the tutorial.
Is there a complete tutorial which walks through every step without stepping over anything?
And do I need to add the SDK even for simple beta tests?
(Edit: No, SDK is not needed!)
Start with logging into the Provisioning Portal, and adding a test device or two, under Devices. Then go to Provisioning and create a new one for the appID you are working on and add those devices.
Back to Xcode and use the Organizer:Devices:Provisioning Profiles to download (refresh) the Provisioning Profile. Set your project's Debug scheme's signing to use that developer profile. You should then be able to build and then archive. Once archived, do an ad hoc distribution and save off that file to the desktop.
Go to your account on TestFlightApp.com and press the Upload Build button. Drop the file you saved on your desktop, into the Build upload area. TestFlightApp will give you errors if the app wasn't bundled for adhoc or signed properly.
Now, here is where TestFlightApp.com will save you work. Send out invites to friends from within TestFlightApp.com. TestFlightApp.com will manage notifying them and as they create an account, it will also help them find their UDIDs. These UDID's can be batched up and later downloaded by you and re-uploaded to the Apple Provisioning Center, into your devices section.
You then use Xcode to refresh your profiles, and rebuild the app, archive, and upload to testflightapp. Then you can select which one of your testers will get to see this build and what message they should be sent. Your testers will not have to figure out how to download the files and install them using iTunes or other app, they merely press the install button.
Believe me, while it is still a bit of work, it is so much better than not using TestFlightApp.com, especially if your users are not very savvy about app installation. In the future, you can use the TestFLight SDK to gather crash reports and usage information for your debug builds.
See the following for some more info: TestFlight beta-testing iOS app
I get warning: Application failed codesign verification. The signature was invalid, or it was
not signed with an Apple submission certificate. (-19011) can anyone help me ...ive been stuck
for a month ...also the app goes on my device for testing and i get a file to zip in my build
iphoneos file but when i use the app loader it says: Directory Services reported the following
error: Your Apple ID or password was entered incorrectly. (-20101)...i don't know how this happens when i log in correctly.. please help someone thank you.
When you receive "Directory Services reported the following error: Your Apple ID or password was entered incorrectly. (-20101)" from Application Loader, this means that your username and/or password has changed or it's in correct.
Solution:
1)Open Application Loader.
2)Click Window->Run Setup Wizard (Shift-Command-S).
3)Read the information on below the "Welcome to Application Loader." text
4)Click "Next".
5)Enter your iTunes Connect information (Apple ID and Password). If there are multiple developers on the account, use the Team Lead/Agent account information.
6) Click "Next".
7) If the information is correct you will get "Your iTunes login information has been verified." and if not you will get the same error as before and you will can always go back to re-enter the correct iTunes Connect information (Apple ID and Password).
I hope this helps.
Before doing a build for submitting (Release) to the app store, in Xcode under project properties ensure you have the settings for Release/Distribution selected. Then in the certificate row check you have your distribution certificate selected.
In Organizer check that your certificate is still valid. If not use your web browser and update the distribution certificate under developer.apple.com. THe update certificate takes a few minutes to become available. Back in Xcode use the update in Organizer to load your new certificates. If you get an error logging in then Xcode probably remembers an old or wrong password.
When you have your certificated sorted out, and want to do a build for the store use "Build and Archive" to upload your binary to Apple. The app loader still exists but since Xcode 3.2.something this functionality is included in Xcode
The best solution would be to develop for the Android. However, failing that are you using the Application Loader, not the xCode one which no longer works.
Also have you created your own Provisioning profiles for release and using them when you archive your code into its zip file from within Xcode?