I have registered 2 devices in App program portal. Only I have a Mac & device to download the App for testing. The other user does not have a Mac. But he has an iPhone. Is it possible for the other user to have the App downloaded for testing so we can discuss if we need any modifications before making the App live on App Store for public.
相关问题
- CALayer - backgroundColor flipped?
- Core Data lightweight migration crashes after App
- How can I implement password recovery in an iPhone
- how do you prevent page scroll in textarea on mobi
- Custom UITableview cell accessibility not working
相关文章
- Could I create “Call” button in HTML 5 IPhone appl
- Unable to process app at this time due to a genera
- How do you detect key up / key down events from a
- “Storyboard.storyboard” could not be opened
- Open iOS 11 Files app via URL Scheme or some other
- Can keyboard of type UIKeyboardTypeNamePhonePad be
- Can not export audiofiles via “open in:” from Voic
- XCode 4.5 giving me “SenTestingKit/SenTestKit.h” f
Use Ad Hoc distribution.
Follow the steps here to package the app for the tester. Publishing Applications for Testing
Then the tester should follow the steps here for installation. Instructions for Application Testers
Edit: Both links are to the reference documents from Apple itself and are likely to be kept more up to date as procedures change in later versions.
Ad-hoc distribution to Windows iTunes works as it does for Mac iTunes. I set up my Xcode projects per Apple's instructions for ad-hoc distribution, then added my own Makefile to create the distribution. Makefile snippet:
My project structure is ./Makefile and ./iphone/MyProject.xcodeproj with sources in the expected place ./iphone/Classes/*.[hm]. Makefile variable explanations:
I sym-linked Provisioning_Profiles to "Provisioning Profiles" for easier typing. I also hard-linked the appropriate provisioning profile in that directory as AppStore.mobileprovision or AdHoc.mobileprovision for easier updating.
The steps themselves are straight-forward: clear a build space, build the app, verify the code-signing bits are in place, prep a landing space for the distro, pull in the appropriate mobile-provision file, zip up the app, verify the signing, and zip up as an .ipa file. (Strictly speaking, the zipfile is needed only for AppStore, and the .ipa for AdHoc, but I put them both together for my own hysterical raisins. :-)
I then push the .ipa and the mobile-provision file up to a private website. My beta testers pull the .ipa down and drag-n-drop onto iTunes. Only if I add or remove a device does the mobile-provision change, thus forcing the beta testers to pull down and drag-n-drop the latest mobile-provision file.
This has worked very smoothly for me and my beta-testers on iClear (update in review).
I have been successful with AdHoc distribution. Thought of posting this info for someone else so it will help.
Follow the documentation from Program Portal user Guide, for Build steps.
Then you can drag the .app and .mobileprovision file (you used for AdHoc distribution) to iTunes account. It installs the App for you. You can then sync to device. It works great.
You need to send just the .app & .mobileprovision file to people who want to preview the App before it can go to AppStore. Their UDID's (device ID's) should have been registered in your Program Portal account.
The other use can drag your Ad Hoc build into iTunes on Windows. There are some pretty good instructions here.
To create an Ad Hoc build, you can follow the instructions in the iPhone dev portal. It is similar to doing a release build, just using a different provisioning profile.