My app is currently well-developed but not released on App store. 40 volunteers are willing to test my app. I want to let them test my app by Over The Air (OTA) Ad Hoc distribtuion.
However, since i need their UDIDs to set their iPhones as test devices on iOS provisioning portal, test users might not want to give such private information.
Besides, does provisioning file contain all the UDIDs of test users?
I am afraid of that all the UDIDs would be known if someone opens the provisioning file.
Are there experienced developers who already successfully persuade test users to give their UDIDs for Ad Hoc distribution?
Since a company will contact test users, they said it's really hard to ask test users' UDIDs. Is it any second solution?
I would agree that it is awkward to ask people for their UDID.
There is a free app that will let them automatically send their UDID to you. I find it's not only easier to persuade test users to use it, it also makes the process easier for them.
https://itunes.apple.com/us/app/ad-hoc-helper/id285691333
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 finally got an invite to an internal tester to work using iTunesConnect and the Test Flight app. I find that for adhoc distribution this is simply not going to work...
30 day expiration is way too short.
In the old Test Flight, a tester had multiple devices. With the new test flight each invitation is good for only one device. If you try to use the invite on a different device it says it is already in use.
I don't see any work around for the expiration period, any ideas on a workaround for the second issue, or am I doing something wrong? Is there a way to add devices to the the user account.
Perhaps, this is not the vehicle I should use for my adhoc distributions? Other suggestions are welcomed.
The new TestFlight works better than the old one for multiple devices. The invite only works once, but it's tied to the Apple ID you use it with, log into the TestFlight app with that same Apple ID on another device and you can just install the app. Don't try to reuse the invite.
I personally find the Internal testers useless though, since you have to grant those users access to your iTunes Connect account. There's a work around where you can use your own email, something like "me+user1#whatever.com" and have the invite come to you, then you just forward the invite link to the user you want to use the build and not have access to iTC, but that's a pain.
The best plan is, send the app for TestFlight review, get it approved, then add all of your testers as External testers. You can submit new builds without going through review each time by keeping the version number (CFBundleShortVersionString) the same, increment the build number (CFBundleVersion), and checking the option that says "no significant changes for this build".
If you don't need to support iOS 7, the new TestFlight is way better than the old one. With the initial review being the only downside.
Here's a quick guide that explains what you can do with the New TF:
New TestFlight • Quick need-to-know guide
There are two ways I can think of.
Get OS X Server and add the phones individually to your Provisioning profile. You will be limited to 100 phones, but any of those phones can login to the server and download the latest build on to their device.
Get an Enterprise account. You can't release to the App Store with an Enterprise account however.
You can import your devices to testfairy from test flight
https://app.testfairy.com/testers/testflight-export/
This I haven't tried yet.
I'm stuck with this damn "Application failed codesign verification" warning that I simply can't solve... I'm about to submit my app to Apple. :(
Having a look to my provisioning profiles made me realize that the status of my development profile is "Active, managed by Xcode" whereas my distribution profile is only "Active". It may be the reason of this problem because anything else seems to be OK. So what is wrong here ?
Thanks a lot for your advices.
Having a look to my provisioning profiles made me realize that the
status of my development profile is "Active, managed by Xcode" whereas
my distribution profile is only "Active".
The team development profile includes certificates for all the developers on your team and device ID's for all your devices. Since only one person is authorized to distribute applications for any given account, and since there are no device ID's associated with the distribution provision, there's no need to have Xcode or the provisioning portal manage your distribution provision -- there'd be very little to manage.
It may be the reason of this problem because anything else seems to be
OK. So what is wrong here?
No, difference in the description of your development and distribution profiles isn't the problem. The problem is that the codesign utility was, for some reason, unable to sign your application. There are several things that can prevent your app from being signed, such as:
Wrong distribution profile selected in your project's build settings.
App ID in distribution profile doesn't match that of the app you're trying to sign.
Problem with distribution profile, e.g. an expired certificate.
There are also a great many questions right here on SO pertaining to signing your app for distribution. It doesn't make sense to rehash all those answers here, especially without more information about what you've already checked or at least seeing the specific error. Take a look at some of those questions first and see if something rings a bell. Otherwise, take a look at the Troubleshooting section of the Tools Workflow Guide.
I am really confused with ios provisioning profile. Can I use one Development Provisioning Profile for multiple apps? Same question for Distribution Provisioning Profile.
thanks for your help.
Yes, you can use the same certificates for multiple apps.
It may seem complicated, but once you look at it, it's not so bad. Here's the breakdown:
The development provisioning profile gives you the opportunity to test apps you create (any) until you try to push it to Apple. When you do that, the distribution profile comes into play. Essentially, it connects any apps you produce with your App Store storefront.
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.