Request Install Packages Permission: Permission use is not directly related to your app's core purpose.We found that your app is not compliant with how REQUEST_INSTALL_PACKAGES permission is allowed to be used. Specifically, the use of the permission is not directly related to the core purpose of the app.
I tried this solution on my manifest.xml file
I also contact to play console support and also uploaded a video for all my app functionality still my app get rejected.
Related
Our app is built in Ionic / Capacitor.
I got this mail when I submit my latest app.
Our latest app is rejected.I try to resubmit app and also try to appeal but nor I got response nor my updates are approved.
In our latest bundle I try to add
<uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" tools:node="remove"/>
So now our app not contain this permission and also now that is not shown in below permission
But still my app is rejected after this.Is there any place from where I have to remove this permission?
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 uploaded my app on the internal test track on google play console ,it took over 2 days and still pending then I decided to upload it to the internal app sharing which brought me this message.
I've released it as a signed bundle .
As I understood from the play console help
Uploaded artifacts for internal app sharing aren't shown in your
artifact library, nor can they be included in releases on testing or
production tracks.
So this means I should just wait till internal test is published first or I have to build a new unsigned bundle for app sharing ?.
If so .I've read that the internal app sharing has its own signing and I've been using flutter which has a long process of signing .So am not sure whether to remove all the code in gradle and the key.properties file or generate a new new keystore.
Simiar issue
Your app needs to published on a track before it can be uploaded to internal app sharing.
It looks like you are still waiting for your app to be approved on the internal test track, so there is nothing you can do until then, you have to wait that your app is approved and published (and probably avoid publishing another version in the meantime which might reset your waiting time). Since COVID, waiting times have increased, so it will require some patience.
Regarding siging:
On any track, the app bundle needs to be signed.
On internal app sharing, the app bundle does not need to be signed. So you can remove the signature step in Flutter when building for internal app sharing if that significantly speeds up build times.
I'm added Crashlytics for my iOS app. I downloaded framework from it via their site link, and went through all the steps for integrating the frameworks, adding the run script, etc.but problem is that i add framework in manually and not receiving a email.
Did you follow the instructions mentioned here to manually add the Crashlytics SDK?
Did you also integrate the Firebase SDK?
To use Firebase Crashlytics, you also need to install the Firebase SDK along with the related configuration. E.g. Installing the GoogleService-Info.plist file and the initialization code.
Once you do this, you will need to cause a crash. For this, you need to run the app, stop Xcode, and from the device run the app and cause the crash. Then you will need to run the app again from the device. If everything was done correctly, then you should see the report in your Crashlytics console.
So as everyone knows, publish to the appstore is a nightmare, at this precise moment i´m trying to publish my app but i keep getting erros regardless of using nativescript sidekick or using aplication loader, also i have done EVERY step that is said here... so:
When using nativescript sidekick:
I hit the publish button, select my certificate and provisioning
profile.
Insert my appstore credentials
The error is: Errors is: The request can't receive any response
i Went here but the problem persists!.
When uploading the ipa file in application loader:
The error simply says(always!!!) that my provisioning profile is not for that bundle etc etc.
What can i do here? what is the problem?
Thanks for your time, regards
As mentioned on the official {NS} website to create your ipa file try running:
tns build ios --release --forDevice
This will create an ipa file in this directory: /platforms/ios/build/device
Then try running this command to publish the App:
tns publish ios your-apple-id your-password --ipa path/to/ipa