I searched a lot on StackOverflow and Googled a lot but I didn't find the exact answer I was looking for.
I recently submitted my application to the App Store review after several weeks of testing with TestFlight.
My application has been accepted on the App Store, and I indicated that I would like to do a manual release. So my application currently has the status "Pending Developer Release".
My build 1 is now ready to be released on the App Store.
The launch of my app is in a few weeks and I would like to have my build 2 (which already contains bug fixes) validated by the AppStore before the launch of my application. However, if my build 2 doesn't pass the App Store review before the launch of my app, I would like to be able to launch my build 1 anyway.
On the AppStore, I can't upload a new build if my old one hasn't been released. I have to cancel the already released build.
So I was wondering how to do this.
Can I, for example, validate my build 1 on the AppStore and set the availability to "no country"? and the day I launch, I just change the availability to "all countries"?
I hope I made myself clear!
Thanks,
Viktor
First things first , if you have a build with state Pending Developer Release for version (ex: 1.0.0)
you cannot upload a new build with same version (ie 1.0.0)
Or Else if you want to upload a new build with same version 1.0.0 you should cancel already approved build for version (ie 1.0.0) which changes the state of the build to Developer Rejected , in this state you can upload new build ( with probable bug fixes ) on same version (1.0.0)
If for some reason apple rejects your new build ( They inform why they rejected though), you cannot go back to already approved build.
Now if you want to release the build and make it Ready for Sale state then it's visibility in Appstore depends on Availability in Countries.
If you make Availability to none , then the build state for version 1.0.0 changes to Developer Removed From Sale ( No need to panic , if you add one or more countries in Availability the state would change to Ready for Sale state again)
However this makes you restricted from using 1.0.0 version again , so you need to use 1.0.1 or any new version greater than previous one.
If versioning is not an issue , you can release 1.0.0 and remove countries , so even if newer build (1.0.1) is rejected by apple , you can still release your app on the pre-decided date.
Hope this is helpful information.
Related
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.
I am trying to publish app to google play appstrore and rejected. It seems that Google made some security update, because previous version of apps were published? Is there any solution for this?
Note: i have updated latest SDK from manager
Your APK has been rejected for containing security vulnerabilities, which violates the Malicious Behavior policy. If you submitted an update, the previous version of your app is still live on Google Play.
To properly handle SSL certificate validation, change your code in the checkServerTrusted method of your custom X509TrustManager interface to raise either CertificateException or IllegalArgumentException whenever the certificate presented by the server does not meet your expectations. To confirm you’ve updated correctly, submit the updated version to the Developer Console and check back after five hours. If the app hasn’t been correctly upgraded, we will display a warning
Problem is using OpenSSL 1.0.1l in the official 4.5 release SMF and next releasing an upgrade to the 4.5 players to OpenSSL 1.0.2g which is the latest release. Wait SMF 4.5.3.
I wouldnt hold my breath waiting for app studio 4.5.3. I have been in touch with them and they said that they have dropped the desktop IDE as their cloud IDE is doing much better. They gave also mentioned that in 6 months time their cloud IDE will have a WYSIWYG editor.
Hopefully the trusted manager error will not occur when publishing with the cloud IDE
I have an app approved by app store that is version 1.0, and I want to update the app to version 2.0. I changed version to 2.0 in iTunes. It's in the "waitin for upload" state. I have made some code modification in my version 1.0 and changed the bundle version as 2.0. When I am about to upload the appbinary using xcode, it still shows the version as 1.0. If I m to click the validate button, it gives a message that it's already uploaded. Should I change the bundle identifier? I'd be so grateful if you guys could help me out.
You should update the BundleVersion in your Info.plist file prior to compiling your final release build.
Is the iTunes state "Waiting for Upload"? If not, then you have not yet told itunesconnect that you are ready to upload binary.
Delete your build folder and/or check your target to make sure you are building your release target and not trying to send an old release build.
I'm testing my in app purchase code for an update to my app. The in app purchase works great when I do an install from xcode to my phone. The issue arises when I have the currently released version installed on my phone then I install the dev version over the top of the release version. When I install in this way my product ID comes back as invalid even though I've tested it many times and it works as long as I didn't have the release version installed previous to installing the dev version.
We did alter our Bundle ID in this update but everything has worked except when we install in the way I described above.
Has anybody encountered this behavior before?
Also the currently released version does not have in app purchases.
This happens all the time.
If you install your development version over the App Store version - new In App Purchases IDs are returned as invalid.
This will work perfectly when you upload the new version to the App Store.