We created an app that is ready for beta testing, the app is published to a specific region and we have created a beta testers list, the url is generated and when you click on it the user can otp in to be a tester, but when he goes to actually download the app it says that the app is not available in his country?
We have this problem also. We have an app that is available only in Spain, and we want to have beta testers in Italy to test the app before we make it available to all public. I've just asked this to the support guy on https://support.google.com/googleplay/android-developer/ (there is a chat that appears at the bottom).
My question:
The app is available only in Spain but we want to have beta testers in Italy. Is this possible?
Support answer:
The country distribution refers to the whole app, not individual tracks (like beta or production). As a result, it is not possible to beta test in one country whilst the production version is in another country.
Conclusion:
It seems that you need to make it available to that region before people living on that region can install it and beta-test it.
Related
I've been developing a Swift app for a while now on my own individual developer account linked to my longstanding everyday AppleId - so the AppleId also has all my bought music, apps, appleTV and other content etc etc. As I have developed the app I have realised that it has considerable commercial potential, and so would rather release it under an organization (a private limited company) than under my own individual name.
The app itself is relatively straightforward, it is self-contained other than having a single non-consumable in app purchase. I have not yet uploaded the app to AppStoreConnect, although I have set up the app name and the in app purchase on AppStoreConnect for testing purposes. I would like to release in the quickest way possible now. Using XCode 14.
What is the quickest, most straightforward and trouble-free way to achieve my goal? Should I:
Release it under my own individual developer account and then ask apple to change my individual account to an organization account? Are there any complications with this given that this dev account is attached to my personal AppleId? How long does it usually take Apple to achieve the change? Does the App remain on sale throughout? Are there ever any problems or is there anything else I should be aware of?
OR
Set up a totally fresh AppleId and create a new developer account for the organization on this id? (I appreciate this will cost extra money but am willing to bear the cost). If I do this, how do I transfer the app from my individual account to the organization account? Do I have to go through the Apple 'transfer an app' process? Are there any pitfalls with this? When the transfer is complete, how do I alter my XCode set up to continue working on the app under the new account? Also, as I have not yet submitted the app to AppStore (although I have set up the name / IAP ) can I simply use XCode to point the app at the new account and upload it to that instead without invoking the Apple 'transfer an app' process - how would I alter my set up on XCode to achieve this?
I am currently in the process of setting up the company, and should have necessary info eg DUNS no etc fairly shortly.
While I'm familiar with development itself and I've already released one paid app on the AppStore under my own individual account attached to my everyday AppleId, this seemed to be a relatively simple and automated procedure. My main difficulties with my current problem seem to stem from the fact that I have never worked as part of a swift development team, and I understand very little around the actual 'architecture' of app development, eg XCode signing / teams / bundle ids etc, and I'm really struggling to understand the technicalities of the connection between XCode / Developer Account / AppStore Connect / AppleID.
I've looked through other posts on this topic but most seem several years out of date, and I am aware that AppStore functionality in this area has changed over the years.
Any help would be greatly appreciated - particularly if you can recommend which route to go down and answer any of my specific points. I have tried asking Apple, but all I get back are standard replies directing me to their app transfer process - unfortunately though I'm something of a solo outfit and I really need the benefit of people's experience here, as I need this process to go quickly and smoothly!
Cheers!
I read about alpha/beta testing of apps in Play Developer Console. I have almost understood the concept of beta/alpha testing. Just have a question:
I want my app to be visible in Play Store but only those people can download it who are invited (like using email addresses or G+ communities). Seems like Alpha/Beta Testing hides the app from public.
But I have seen several apps (Can't think of the name) in Play Store with the text similar to This app is still in beta. Please wait until we reach more audience. And as expected there's no install button.
I want something similar to this. Public can see but only those can install who join G+ community.
Does open/closed beta testing provide such feature?
Google Play Developer Console allows developers to upload a beta APK, and invite a Google Group to use it.
How to know how many users are using my beta?
In the console:
Go to Statistics,
Click Export as CSV,
Uncheck everything but Installs devices current and by app version
In the resulting CSV, spot the id of the APK you sent for beta
The number in the third column is the number of beta users.
The Google Play Developer Console has changed a lot since the original answer.
If you are using Open Beta Testing then go to:
Release Management / App Releases / Manage Beta
and you will see something like this:
Note: if the number of testers is not showing, this might be because the number has not yet reached a certain threshold.
This specifically answers the question "How many people have opted into Beta testing?" which may or may not be what the OP was really interested in.
Analytics would be the way to discover how many are actually using the beta version.
I am interested in developing an app for Windows Phones, and was wondering if they support the concept of limited/beta releases for their app developers? By this, I mean the ability to deploy a beta or demo version of my app to a limited/restricted audience, such as business partners, customers, external beta testers, etc. Nothing in their SDK documentation indicates either way. Thanks in advance!
You can create a Beta App submission in the Dev Center, and by adding certain Live Ids, limit the access to your application and make it available to your Beta Testers. See the following for more information :-
http://msdn.microsoft.com/en-us/library/windowsphone/help/jj215598%28v=vs.105%29.aspx
My company needs to upload an app to the store , that will only be available to 80 people over the world that will get the permission to test it.
The ad-hoc method requires their iphones id's to be register with the app, and obviously we dont have it.
Whats the best way, to upload the app to the store ,to let this people to get it ?
(NO, without just go to the review process of apple)
thanks.
Besides the enterprise developer program, Ad-Hoc distribution is the only way to limit your audience.
If you try to game the app store with an unreasonable high price and promo codes (limit of 50 codes per app version) Apple will kick you out of the review process in no time.
Use testflight to get device IDs easier and deploy you app to the testers.
There is no way to do that, for the Adhoc, you must register their UDID devices.
You can upload the app in the AppStore, put it's price high, and give the prople that you want to test the app a redeem code that will download the app free, but i think the number of redeem code you have is 25. If you find anyway to do that, share it with us please.
If the 80 people that will be testing/using the app are employees of the company, you should look into the Enterprise Developer Program. Enterprise development lets you deploy an internal app to employees of your organization that is not released to the App Store. It essentially lets you build an Ad Hoc like version of your app that can then be installed on devices without the need to get UDIDs.
The cost is $299 instead of the normal $99 and there are a few caveats on whether or not your organization qualifies. But if you do qualify, it vastly simplifies deploying an internal app and it gives you specifically what you were asking for - no review and no need to ask for UDIDs. You can put the signed bundle up on a website and simply give people the URL to it for OTA installation, so you don't even need iTunes.
Alternatively, if the end users are not a part of your organization, you can also look into developing Custom B2B Apps. This one comes with a few more hoops to jump through and it also requires an Apple review, but it allows your app to be sold only to specific customers and doesn't put it in the App Store. If you're already a developer with Apple, there's even a WWDC video on it.