Yes. all of devices have been added to the profiles in AppDev Center.
Yes. all of devices have been added to the profiles in AppDev Center.
i just shared the new app with you. It is more complicated than the others but same issues on all of them. BOS3
Quick question. Do you have an older version of apple iphone or ipad that you can download and test the app on? I am trying to find one with my friends, but no luck yet.
Do you know what this line means?
Do you have the provisioning profile installed to your iPhone? Use iPhone Configuration Utility to verify
Is there something that I have to download to my devices before I can start downloading the apps for testing?
Do you mean with iOS 6.1? - yes, we have.
Sorry, I'm not understand what line do you mean?
OK. I have finally figured it out. It maybe that I am new to all this, but man, there is a very important step missing in many documents. One has to upload the provisioning profiles to each of the testing devices.
So here is what the problem was:
I had used an iphone app called UDID+ that is supposed to give you the device unique identifier used during the testing and provisioning profile. It turns out that it generated some random number that I should have checked with the itunes UDID which is displayed when you click on the serial number of the device in the Summary screen when connected with iTunes.
Once I copied the right UDID from the iTunes and regenerated the provisioning profiles, everything else just fell into place.
Another important utility that I have discovered is the iphone configuration utility for windows. It allows you to see the console error messages as well as the correct status of all profiles and apps on the devices.
You can download it from here:
http://support.apple.com/kb/DL1466
Anyways, this issue and the UDID+ app has caused me to loose many days and a lot of frustration.
Also, for Appery, it would be nice to add the step that for testing apps, load the provisioning profile file to the testing devices.
Thank you all for your help and sorry for causing this issue. But good learning for me at least.
Thank you for pointing on this, we definitely will update it in our documentations.