I have uploaded an app in play store. I have created releases in Internal Test and Closed Test tracks. I have created In-App products also. Then I have added testers account for licensed testers. I have opted in using the opt-in url. But when I installed the debug build of the app in physical device with same package name which is configured in play console I am unable to test In-App products.
Actually its been 2 days since i have uploaded my app for first time. Using test accounts, I am unable to download the app from play store. It seems, google will take time to review the app and approve it. But in the docs(added url below), they have mentioned that we can test In-App products with debug builds. But I am unable to test it.
My debug build has same package name as that of app uploaded in play console. I have configured the product id correctly too. Can somebody help what might be the issue. Should I wait for google to complete the review and approve my app?
https://developer.android.com/google/play/billing/test
Check out this post: Testing in-app purchases on Android
This should solve your issue and make this process clear for you.
Related
I’m new for IAP feature in iOS. I sent my couple of day to test IAP for learning purpose bur did not get success.
Something I’m missing to implement or whatever I don’t know exactly thats why I’m asking here. Basically I wrote code from this tutorial and my system is iOS 9/10 and Xcode 7/8 actually I tried with both.
I did all the step correctly Make “Test User”, Remove iTunes account from the device etc and also test cases from this web link but still facing “In Valid Product ID” don’t know why? but did not get list of product(s) from iTunes.
Just clear me for below point
1) Do I need upload app on AppStore (temporary then reject it) for first time test IAP in sandbox environment or no need to do?
2) Do I need to add ”Contracts, Tax, and Banking Information" in iTunes for sandbox environment or no need to do? (Right now added in my iTunes Account)
I added product on iTunes with and without screenshot uploaded but each time when I upload screenshot with product in iTunes then status was “Ready to Submit” and and without screenshot status was “Missing Metadata”
Is it correct status? and can we test IAP purchase with this status in Sandbox Environment?
1) No. There is no need to upload an App and reject it in order to test In-App purchases. You only need to create a sandbox account.
2)Yes, add the required information.
Make sure you have properly submitted each In-App purchase AND added them to the app - both steps required.
Having submitted a beta version of my IOS App trough Itunes Connect and Testflight to INTERNAL users, and selected it for testing to EXTERNAL users, it displays "waiting beta app verification" (from Internal users) and I don't know how to release the app for EXTERNAL User. (see pict enclosed).
It did worked on past version but I don't know how ... times, upload from Internal users, approval from them (but don't know how).
Need to re-test then submit my app quickly, any help welcome !
NOTE : Apple displays help on old itune connect versions, and don't see where this can be done. See here
Apple says:
Upload a build for the app. See Uploading a Build for an App.
Add App Description and What to Test to the build. This step is optional for releasing your builds to internal testers, but required
when submitting your app to Beta App Review for external testing. See
Add Metadata for your Prerelease App.
Distribute the app to internal testers.
Submit the app for Beta App Review, and distribute it to External users.
You need to have every build reviewed from apple for distribution to external testers.
I'm not sure how it worked earlier, but for now
All builds distributed to external testers must pass through an Apple review. While these reviews do not fall into the same queue as those submitted for App Store release, they can take time.
In other words, you have to use button "submit for beta app review" ;)
You can find guides here: Ray Wenderlich or kyleclegg.com
I have to solve the problem of how to allow review (testing) of our app by prospective developers, when the app is not yet Ad Hoc. I can't get it that far. Here's the problem:
I have to find a new developer to help update our app for 2016. It's a 365-day calendar of info that updates every year. The initial app download is a shell (free) in which 29 in-apps, each a different geographical region of information, can be purchased & downloaded. Regions are 16.95 each. In order to help candidates familiarize themselves with the app, they need to be able to download an in-app region and see the app function. I can't expect candidates to pay 16.95 for a region, so I need a way for them to test the app.
1: I can't use the promo code feature in iTunes Connect because it is worthless for in-app testing, which makes it worthless for many apps out there since the in-app is often where much of the critical content lies.
2: I can't sign candidates on as Sandbox or TestFlight testers because I can't upload the app into iTunes connect without getting an error message I don't know how to fix. When I try and submit the app through XCode or the App Uploader, I get an error reading, "The Info.plist in the package must contain the CFBundleShortVersionString key." I don't know what to do with that error, so I can't get a version into the iTunes Connect environment to invite testers into.
So the Apple TestFlight for external testers is finally available. My app is in stealth mode. But I want to send it to a few people to beta test before I release. While going through the process for submitting my app for beta testing review, the submission process requires a Marketing URL which is supposed to be
A URL with information about the app you are adding. This will be
visible to testers in the TestFlight app.
Given that my app is in stealth mode, I don't want to have a public url where I describe my app. So has someone already gone through this process and have some ideas how I might safely do this without divulging my app to the public? Thanks.
I created a document saying, "Information about this app has been shared privately with you." I put in a link to this document in TestFlight, and Apple accepted it.
I'm trying to understand how to work with In App Purchases. I've read many documents and seen a lot sample codes but I can't understand why product list is empty. According to documentation and forums I made this:
Setup contracts on iTunes connect.
Create AppID on provision portal with unique bundle ID
Create and install provision profile for this AppId and enable In App Purchases
Create application on iTunes connect.
Create purchases for this application.
Submit application.
Reject application.
In code, I've tried to receive product information by product ID and as result I can see empty list. However, I can see an array of invalid product IDs.
Could you help me to understand what is wrong?
Thanks.
According to Apple documentation:
Follow these steps to test your application in the sandbox.
- Log out from your iTunes account on the test iOS device.
- Before you can test your application, you must first log out of your regular iTunes account. iOS 3.0 includes a Store category in the Settings application. To log out of your iTunes account, exit your application, launch the Settings application and click the Store icon. Sign out from the currently active account.
- Important: Do not sign in with your test account in the Settings application.
- Launch your application.
- Once you have signed out of your account, exit Settings and launch your application. As you make purchases from your application’s store, Store Kit prompts you to authenticate the transaction. Log in using your test account to approve the payment. No financial transaction takes place, but transactions complete as if a payment was made.
I've tried it and can't see "Store Kit prompts you to authenticate" when I ask for products. Maybe I need to setup project in xCode?
Hm...
I can see products in Simulator of iOS 5 but can't buy it. Magic.
Try to delete your build and app on your device. I think this one should work.
It can take a good few hours for Apple's server to get round to enabling the in-app buys. I had the same problem that you did, but then it just started working half a day later.