We have already deployed a number of versions of our app to Playstore when I tried to release a build a week ago , They Showed me a waring to declare the REQUEST_INSTALL_PACKAGES because it was present in our first Internal test build due to openFile: package.
But we have already removed it from our code atleast 3 months ago and the playstore is asking us to fillout a form explaining why we need the Install Package Permission and where we use it in our App. We don't actually use it on our app. can any of you help me with this I'm also attaching the form that they showed inorder to declare the REQUEST_INSTALL_PACKAGES permission.
I tried to release the latest version of our app to production just like I always do but they are preventing the release until I solve the issue sown in App Contents for sensitive permission declaration.It didn't happen like this before.
Related
I am using Firebase App distribution over a year now to deliver my Flutter app releases to my testers and it's working fine by following this process :
Open XCode and make a release of the app
upload the .ipa to Firebase app distribution
If the testers download it the first time, add their device to my apple dev account
Make a new release with the new provisioning profile
The testers are able to download the release
Now i am using flutter 3.7 and i am using this command :
flutter build ipa --obfuscate --split-debug-info=/Users/foxtom/Desktop
It's working very fine apparently, i do have a .ipa file generated etc..
However, when i upload this .ipa coming from this command, all my testers (including myself) are getting Device is registered, all set ! from Firebase app distribution.
This is the message you get when the device is registered the first time and that you have to make a new release... So i have made 3 different releases after this one and the message remains the same.
Note : if i do the same release using Xcode, it's working fine.
I can't figure out if the issue is from Firebase or Flutter here... My guesses are :
Flutter doesn't take in consideration my provisioning profile
Firebase app distribution has an issue "veryfying" obfuscated builds
I have raised a ticket to Firebase support in the meantime, but i would like to know if someone had already experienced this and if there is a current solution.
EDIT : i have created a flutter issue to get more insight
I'm trying to create interval test for my flutter app.
But Google Console is not publishes the new version of the app for testers.
I'm NOT publishing the app for the first time.
I have a previous version of the app that was approved.
However this is my first test for the app.
I strictly followed the instructions provided by Google.
What I did:
made a new release that I want to test
created internal test
added list of internal testers (all of them are approved now).
published the new version to internal test
copied the link and tried to get the test version of the app as an internal tester.
However I've downloaded the old version of the app.
I've also tried to create alpha and beta testing after that and provided them with new version.
But still got this problem.
What's more, I did some extra step to solve this problem:
cleaned Play Market cache on the device
downloaded another simulator to test the app
changed the version of the app and downloaded it again
deleted and added again tester list in Google play console
Screenshots:
https://github.com/asg1997/qu/blob/main/Screenshot_1639590890.png
https://github.com/asg1997/qu/blob/main/Screenshot_1639591139.png,
https://github.com/asg1997/qu/blob/main/Screenshot_1639591150.png,
https://github.com/asg1997/qu/blob/main/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202021-12-15%20%D0%B2%2020.53.20.png,
https://github.com/asg1997/qu/blob/main/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%202021-12-15%20%D0%B2%2020.54.18.png
I have released 4.4.2 -v ,4.5.0-v and 4.5.1-v apk versions
I want to change the app signature ,while submitting new version I am getting error like - The keystore used by your App is inconsistent with the version on the shelf please refer the rule 8.6 of "App Gallery Review Guidelines"
How to submit the apk with different app signature?
I would like to remove 4.5.0 too.
Once a signature key is generated in AppGallery Connect or uploaded by you, it cannot be modified.
For details,check the following documents:
https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agc-appsigning-introduction-0000001051379577
Yes. For this You need to remove the application from App Gallery Connect, then after only it is possible to delete the application.
After the application is submitted successfully for removing, the app status changes to Pending removal. Huawei operations personnel will handle your application in 1 to 2 working days.
Note: Removing an app will not release the package name used by the app. A package name can be released only after you delete the app.
For details, check the following documents:
Remove the app: https://developer.huawei.com/consumer/en/doc/distribution/app/agc-remove_app
Delete the app: https://developer.huawei.com/consumer/en/doc/distribution/app/agc-delete_app
Note: For released app, changing signature is not recommended.
Our latest version passed review yesterday, and the beta testers (~10 people) received their notification that the build is ready to test on iOS. When they click the TestFlight link in the e-mail, it opens a screen that says: "Couldn't Load App. This build is no longer available." With a "Try Again" button. I have tried removing and re-adding all testers, and that didn't do much if anything. Also, a NEW tester that was only added to the new version could download it with no problem. This only appears to affect users that have an older version already installed?
Please help!
Instead of adding individual testers to the build, we started using the "External Groups" functionality in TestFlight. This seems to have resolved the issue for us, however there is still clearly an issue with individual testers getting access to successive builds.
We have an app in the store right now that was shipped with a wildcard app ID.
The update that is now pending approval was created with an explicit app ID, to enable push notifications.
We've noticed the following issue during ad hoc testing of the update: if we delete the app-store version from our iPhones, and then install the ad-hoc update, everything is fine. If, however, we leave the app-store version running in the background, and install the ad-hoc update over it, the updated version installs but fails to start up. We suspect that this has to do with the ID change.
If this problem is specific to ad hoc installs, then it is not a worry for us, but we are concerned that existing users will encounter this problem when doing the real upgrade from the app store.
Has anyone seen installation issues after upgrading from a wildcard-ID app to an explicit-ID version?