This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 93%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
As per question:
Paid for app. (Its not a free to download app)
Built and released a Test flight version.
Testflight nominated testers dont appear to be able to download and test the app without having to purchase the app.
Windows UWP app.
using namespace Windows::Services::Store;
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 92%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERL%3C/text%3E%3C/svg%3E)
Hello,
Welcome to Microsoft Q&A!
Yes, the test flight package is designed for test purposes and the users are selected by the developer. But this is a special mechanism and only for test flight.
Thank you.
"the test flight package is designed for test purposes and the users are selected by the developer. But this is a special mechanism and only for test flight."
Yes we know that, we need to be able to test the In App Purchase flow in a Paid for app. I.e. the app is not a free to download app.
The problem is that when a VALID identified registered tester attempts to download the paid for app FOR TESTING ONLY they cannot - the store seems to insist (we or) they pay for the app before it allows a download for TESTING.
As per the original information: "How can testflight testers test In App Purchases in a paid for app without having to purchase the app"
IE people who are TESTERS, need to TEST an app without having to PAY TO DOWNLOAD THE TEST APP.
If you have other feature requests, please submit your feature request in the Feedback Hub. The team is actively checking user's feature requests there. If your request has a high vote, the team would consider implementing it. You could find the Feedback Hub in the Start menu.
This is not a feature request (or at least should not be a feature request),
The ONLY documented way to test In App Purchases is to upload a testflight build to the store.
What is the process to test In App Purchases for apps that are NOT free to download?
(Forcing testers to purchase the app is NOT a viable soln)
The test flight package is designed to be the way for developers to test their packages. If you want to test your app for free, you could try to test your app with sideloading. If you want to test the app that published in the store, then you will need to use the test flight package. If you want to make it for free, this is a feature request, then you could submit it in the Feedback Hub.
Another option is that you could submit a new version of your app and make the submission not available to the public and set the price as free. Then you could let the users you choose to download the app for free and test. After testing, you could create a new submission and change everything back- make the app public and set a price again.
Testing the In App Purchase functionality does not appear to be viable via sideloading - probably something to do with what its signed with / no licence info.
The dashboard explictly blocks making any new submission 'private'. - apparently because its already a live publicly available app. In all cases it appears that making the submission 'free' means all those with access to the app will be able to download for free (even if only available via a direct link which obviously very few people will discover...)
I have no doubt there are many other hacks that can be dreamt up to get around what is clearly a fundamental flaw in the Test flight process, but that does not detract from the fact that the Test Flight mode does not support the one thing it is supposed to support.
Never mind, its just another thing that we will find a way around...
So if you have other feature requests, you could submit them in the Feedback Hub. The team is actively checking user's feature requests there.