Now I've got an app in the App Store, with some IAPs.
I'm making a newer version of this app, but with very new IAPs. I added the new IAPs in iTunes connect, but when I tried to make it for review, it said they will accept it only with a new version of app. So what is the correct sequence? I want to test the new IAPs with my new version.
make the new version, upload
wait until they accept, but I don't let them publish?
then send for review the new IAPs?
after can test the new IAPs?
Can somebody tell me the correct sequence?
To add new IAPs and control the release of them, you
make new IAPs
create a new version of your app that includes the IAPs and set to developer release.
upload the new version
To test your IAPs, you only need to create them in iTunes Connect. You can then create test iTunes users and test your purchases in developer and ad hoc builds of your app. Make sure to log out of iTunes & App Store in the Settings.app and to log in using an Existing Apple ID in your app.
Related
Hello I had to fix an IAP id after my iOS app was approved and published.
The app was pointing to IAP with id "MyIAP1" but the id on the AppStore was "MyIAPABC".
This obviously wasn't working... since the App was looking for a non existant IAP ID.
So to avoid releasing a new App build, I've created a new IAP on the AppStore with ID "MyIAP1", the one available in the published App. The IAP is working correctly when I run the App from Xcode but it is not working on production. Do I need to release a new build to somehow enable new IAP products on production? (even if the code is exactly the same of the previous build)
You can since you have already submitted IAP before.
Note: If you have already submitted an in-app purchase with your app,
and you decide to add additional in-app purchases later, you can do so
without submitting an app version.
ref: https://help.apple.com/app-store-connect/?lang=en#/dev1986a0e5c
App is not published on App Store but distributed to testers via Testflight on previous account.
Now I have to shift the app to new account.
With same Bundle Identifier
Can I place it on new account with same bundle identifier?
What will be the procedure to transfer the app because it is in the Testflight and docs says "The app must have a published version." ?
If I just have to simply upload it to new account then what changes to be made and what are the consequences?
Will the testers get it as a new app or an update to installed one?
Are the certificates of older account are required to sign the app?
With new Bundle Identifier
App will be treated as a new app and will be signed with new certificates. So will there be any chances to conflict with the previous one? Or I have to remove the older app from previous account?
If there is any way to distribute it as an update to previous one that replaces the installed one?
What changes to be made and what are the consequences?
According to the Apple Doc -
The app must meet specific criteria to be transferable.
App transfer criteria. Before an app can be transferred it has to meet the following criteria:
Both accounts can’t be in a pending or changing state, and the latest version of the agreements in the Agreements, Tax, and Banking section must be accepted.
No version of the app can use an iCloud entitlement.
No version of the app can use a Passbook entitlement.
The App must have had at least one version that has been released to the App Store.
In-app purchase product IDs on the app can’t be the same as product IDs on any apps in the recipient’s account.
TestFlight beta testing should be turned off for all beta versions of the app.
Sandboxed Mac apps that share the Application Group Container Directory with other Mac apps cannot be transferred.
Source - Apple Doc Link
So ,
You can not move your Testflight app on your new account.
Yes, you can place it on new account with same bundle identifier but before that you have to delete that app first from App Store Connect.I believe that is the case, although you probably could rename the original rather than deleting it.
When an app is removed in this way, the app's name is released to other developers, so make sure you can reuse the name (bundle id),as long as no other developer grabs it before you do.
Upload it to new account then what changes to be made - just upload it as you did before for Testflight and there will be no consequences.
Will the testers get it as a new app or an update to installed one - If you upload it as a new app from your new developer account, it will be a fresh new app for the testers ,not a updated version, but if that version contains any changes then definitely they will get it.
Are the certificates of older account are required to sign the app - No. But you have to download the necessary certification to upload an iPA on iTunes connect for your new developer account.
With new Bundle Identifier
No, there will be no conflicts if you upload the app with different developer account with new identifier as long as it's for Testflight and not published in app store.
You can notify the tester about this app, what it's new feature, or easy way to do that is update the version number while uploading it. If is there anything else you have to know then feel free to ask me in the comment, i will be happy to answer that.
I have submit new version of app and new in app Purchase. Apple have accent new version of app but not accept in app Purchase.
In-App Purchase - New Business Model
We have begun the review of your In-App Purchase(s) but aren't able to continue because your submitted In-App Purchase(s) indicate a change of business model for your app. Therefore, we need to verify the implementation of your submitted In-App Purchase(s) in the app to ensure your app, and its In-App Purchase(s), are in compliance with the App Store Review Guidelines.
Next Steps
Please upload a new binary for review and resubmit your In-App Purchase(s) with the binary so that we can continue the review.
I don't understand, I must only upload new build to itunes connect or then I must add build to in app Purchase?
Steps that help me are:
You should remove your new In-App purchase.
Reject last app version (if it on Pending developer release state), or just create new version
Re-create In-App purchase again (I did it via Application loader (btw it's more usable than website itunesconnect.apple.com). Don't forget to add screenshot and languages (at least one - for example, English).
On itunesconnect.apple.com at the page of your prepared for submit version, you can find In-App purchases section (that was hided before)
Click on "+" - and add your re-created in-app purchase
Upload binary and submit for review
Enjoy!
Well, if they write about different model, than you must re-check types of your in-app purchases.
May be the means that your application must fulfill with their business models, so for example, I think, you can't create paid application with subscription.
Btw, refer to this model descriptions
After that simply create new build and don't forget to attach in-app to it before review
As you know. In-App Purchases need to be configured in iTunes connect. And just before changing app. status to ready to upload, you assign those purchases to the app. version.
Purchases will become available for clients only with a new version of your app.
I have an app with a web based administration system to add products along with their store ids. My app. is communicating with my db throw a web service. therefore products don't need to release a new app version to be available.
Is there a way to achieve that without uploading a new version of the app.
You can modify the available products in iTunes connect without having to upload a new app version. From the iTunes connect IAP management page:
"The first In-App Purchase for an app must be submitted for review at the same time that you submit an app version. You must do this on the Version Details page. Once your binary has been uploaded and your first In-App Purchase has been submitted for review, additional In-App Purchases can be submitted using the table below."
I have currently an app in Waiting for review state. I want to implement in app purchases for the next version of the app, not his one. Can I create new products and test the new version of my app with in app purchases without creating an issue for the review team?
These new products should not reflect in this version of the app.
yes of course you can.. just dont add them to the App's Metadata's In-App-Purchase section...