I have uploaded my build to iTunes connect, and set up internal testing with TestFlight, but my testers are not receiving any invite emails, and my iTunes connect is acting odd. My build has a yellow warning sign next to it, i'm not sure why. Please tell me what I am doing wrong. I am pretty sure that it has something to do with my provisioning profile. I think the pictures below will be most helpful in terms of extra info.
Your third screen shot explains why:
To use TestFlight beta testing, build 1 must contain the correct beta entitlements.
You should follow the instructions in the FAQ link that the error message gave you.
Contrary to the other answer, you can beta test with internal users without review. For external beta testers, you do need a review, but it's less comprehensive than the one for the App Store and typically only takes a day or two.
Related
I think similar questions may have already been asked but cannot find quite the right answer.
I have an app that I build using Fastlane and then deploy to both TestFlight and MS AppStore. We want to be able to have our testers test the app on AppStore but I cant quite wrap my head around the whole provisioning profile story in that case.
I currently have one build going up with ad-hoc profile and another with development profile. I can access it with my phone but my device is on both profiles so it works flawlessly.
When my manager or product manager try download it... well firstly it tells them that "The developers are working on a version for your device. You'll receive an email once this app is released" but then if they follow the link from the email it attempts to install then gives the lovely message of "This app cannot be installed because its integrity could not be verified" which from Googling suggests an issue with the provisioning profile... which makes sense because their devices aren't on the profile.
I came across the possibility of using in-house profiles but for that you need to be a part of Apple Enterprise Program, which, we are not. And that is intended for internal-use apps. Which I guess testing will be but also no.
The only thing I can think of would be to add their UUIDs to the provisioning profile but what bugs me with that is that I would need to make a new build every time theres someone else that wants to test the app which is ugly (not to mention that I'd need to get their devices UUID and can you imagine me trying to get the big boss to give me their devices UUID so that they can have the app in their hand and play with it)
Another thing is we are wanting to do automation testing, and that will run on random devices, so no idea how I would deal with provisioning those
Please if anyone can point me in the right direction?
Also could someone please explain to me the differences between the different provisioning profile types?
AppStore is one that gets resigned by AppStore
Ad-hoc as far as I understand is anyone on the provisioning profile can use it
Development, I have no idea what the difference between development and ad-hoc is
Theres also development id? not sure what that is
Enterprise/In House as far as I understand is a self signed and anyone can use the app but its designed for internal only apps.
theres apparently validation and package too, no idea.
Please and thank you for any assistance
I am having hard time to transfer application. It shows TestFlight beta testing criteria not matching. But I already removed all builds and test information from TestFlight. I have same issue in my two different iTunes account. If anyone have solution for this then please let me know.
I already contacted apple support but no reply from them since one week.
Enclosed are screenshots of my account status of TestFlight and app transfer page.
You should make sure that you removed all the information, in all languages. It worked for me.
screenshot
Every time we upload an app with an issue (missing entitlement, privacy string missing from the project's .plist), iTunes connect emails the error to every single one of the tester emails in our list, even if they're not registered to test for the application I am uploading.
Currently I am the only person in the list for this application, and yet it's sending the email to everyone testing an unrelated app.
How do I turn this ridiculous behavior off and stop annoying them?
This is not a bug. It is a 'feature' of PEBKAB.
The issue was another developer had quietly added the users to itunes connect as internal testers on a separate project. They had all been given a 'developer' role, and when I created the app, they were automatically put on the developer email list for that one, too.
A quick diddle of the users and roles table fixed it all up, no trip to Apple Support required.
Unfortunately this is just how iTunes Connect works. I have reached Apple complaining about this, their answer was that I should use External TestFlight distributions.
Honestly I really recommend you to use other beta distribution platform like beta by Fabric, the build process is using ad-hoc builds, in our team we use beta by Fabric for small builds then once we are almost ready to push to the AppStore we run a small test by using the final build in TestFlight.
I'm not saying Testflight External distributions are bad but is not the right tool for a daily workflow some times you can't afford waste 3 to 6 hours waiting for apple to approve your new build.
I am currently developing an IOS APP on Xcode and I want to have a run on my iphone. It says failed to code sign "my app", no valid signing identities (i.e. certificate and private key pair) matching the team ID “(null)” were found.
Xcode can attempt to fix this issue. Anyone have ideas? Thanks alot!
For you to run applications build from Xcode that are not submitted to the AppStore, you must have a subscription to a Developer Program. This subscriptions is currently $99/year. Not a terrible price to pay but check out this link to see if it's worth paying for.
Briefly some of the benefits:
Code signing to install apps on your own device.
Sending builds to websites like HockeyApp to allow others to test your app and give back feedback
Submitting to the Apple AppStore
Hope this helps :)
I am using XCode 6 and building the IPA. I have been following many posts in Stackoverflow and have gather information and the steps as to how to create the provisioning profiles and build the IPA.
I have been able to build the AdHoc IPA and have been successful in deploying it in my device. The application gets launched and is running fine. Now my query is that, as I am able to install the application on my device without any issues, does it mean that the IPA when uploaded to Apple will also get approved. (I am not using any private APIs. I am building my application using Appcelerator).
No, it doesn't mean that at all.
You've proven only the following:
That you have an app that compiles.
That you have an appropriate provisioning profile to load to your device.
Apple cares about a lot more than just that. For instance, you say it's "running fine", but Apple will test it fairly thoroughly to see if they can get it to crash. From personal experience, they might even find a crash that you can't replicate on your end (which is terribly frustrating!).
Also, Apple has gotten more picky about their approval process. I submitted an app that had an extra feature that linked to another app that was related but distinct. Apple ruled that my app was incomplete as it required another app to be fully-functional. What did I do? I removed the extra feature, and then Apple approved the app. Yes, I took away a feature and my app went from "incomplete" to "complete". My point? Apple's review process is fairly subjective and it can depend on who looks at your app and what kind of day they're having.
On your first app submission, be prepared for several back-and-forth sessions where they reject your app and you have something to fix. On the plus side, they're generally pretty specific about the problem they found, so it makes it easier to fix it!
You may get approved the first time out, but it's a higher bar you have to pass than just the items you mentioned in your post.
EDIT
Also, you need to make sure that you have an appropriate Distribution profile. For loading to your device, you are most likely using a Development profile. Make sure you've gone through the steps to create an App Store Distribution Profile (which also required a Distribution Certificate, by the way).