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.
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
App is developed in Unity. The .apk if shared externally works and im able to sign in with GPGS. However the internal testing build downloaded from Play Store wont let me authenticate. I rolled out the internal testing with all the terms and service accepted. I selected the email-list of testers as well. No idea why it works on a externally shared .apk but not when downloaded through google play tester link. Only think I have done so far is disable billing for the app though I have 300$ worth of credit due to first sign in. Since it works outside of playstore download I assume the billing isn't the problem?
I rolled out the internal testing with everything set. I was expecting it to sign in with GPGS properly as it does when the app installed via externally shared .apk file.
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
My team is planning a large upgrade of our app. Since our last app store submission, we have changed the executable binary file name. This was among several changes to make naming conventions make more sense.
When upgrading our app via Xcode (installing and replacing the old app), we see a very unusual "crash" upon launching it that seems to be on the OS side. There is no app crash log, but see this in the device console:
1) "Application 'XXXXX' exited abnormally with exit status 1" and
2) "posix_spawn("/xxxx/yyy/zz"): Permission denied"
If I rename the executable and target back to what the app store version uses and repeat the upgrade process, I don't see this crash and the app runs normally.
Our concern here is that upon submitting our app to the store, any user who downloads it will experience a crash too and have to delete & re-download the app.
Has anyone else experienced this?
Has anyone successfully submitted an app with a modified executable binary file name and not seen any problems with users upgrading?
As a developer I think everything will be FINE, but I need some evidence that there won't be an issue to present to my product manager. We have a lot of users paying us money that could be upset by this :)
I'm trying to upload an updated iPhone version. I compile with the distribution provisional and get the error - "Application failed codesign verification. The signature was invalid, or it was not signed with an Apple submission certificate. (-19011)".
I'm trying to make the same process for my previous version and it works fine. So I guess it's not the provisional. The bundle id I using in my new application is similar to the previous. I changed the projects structures and added features.
There is another issue which might be related: the application runs well on device but when I'm trying to create an archive I get an error of not find .h files though they are in the path.
I will appreciate if you can assist.
Thanks,
Eyal
Apple's App Store is experiencing downtime lately:
http://www.tuaw.com/2011/07/13/itunes-connect-down-for-maintenance-for-most-of-july-13/