iPhone 应用程序:应用程序进入 App Store 之前在特定设备上进行 Beta 测试

发布于 2024-08-21 21:17:34 字数 145 浏览 6 评论 0 原文

我在App程序门户中注册了2台设备。只有我有一台 Mac 和一台 Mac。设备下载App进行测试。另一个用户没有 Mac。但他有一部 iPhone。其他用户是否可以下载该应用程序进行测试,以便我们可以在将该应用程序发布到 App Store 公开之前讨论是否需要进行任何修改。

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.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(5

二货你真萌 2024-08-28 21:17:34

按照此处的步骤为测试人员打包应用程序。 发布应用程序进行测试

然后测试人员应按照此处的步骤进行安装。 针对应用程序测试人员的说明

编辑:两个链接均指向 Apple 本身的参考文档,并且随着后续版本中程序的更改,可能会保持更新。

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.

古镇旧梦 2024-08-28 21:17:34

我已经成功地进行了 AdHoc 分发。考虑为其他人发布此信息,这样会有帮助。

  1. 来自计划门户>供应>分发时,您需要创建一个 AdHoc 配置文件。
  2. 下载 AdHoc 移动配置文件并确保其已安装在您的计算机中。
  3. 接下来,您应该转到 xCode 并像分发一样构建项目。
  4. 确保在“构建”部分属性下为“代码签名”选择“AdHoc 移动配置”。并指定 Entitlements.plist。
  5. 还要按照文档所述验证构建结果。

请遵循程序门户用户指南中的文档了解构建步骤。

然后您可以将 .app 和 .mobileprovision 文件(用于 AdHoc 分发)拖到 iTunes 帐户。它会为您安装应用程序。然后您可以同步到设备。效果很好。

您只需发送 .app 和 . .mobileprovision 文件提供给那些想要在应用程序进入 AppStore 之前预览该应用程序的人。他们的 UDID(设备 ID)应该已在您的计划门户帐户中注册。

I have been successful with AdHoc distribution. Thought of posting this info for someone else so it will help.

  1. From Program Portal > Provisioning > Distribution, you need to create a AdHoc provisioning profile.
  2. Download the AdHoc mobile provisioning file and make sure it's installed in your machine.
  3. Followed by this you should go to xCode and build the project as you would for Distributing.
  4. Make sure you select the "AdHoc mobile provisioning" for Code Signing under Build section properties. And Entitlements.plist specified.
  5. Also verify Build results as per document says.

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.

書生途 2024-08-28 21:17:34

另一种用途可以将您的 Ad Hoc 版本拖到 Windows 上的 iTunes 中。 这里有一些很好的说明

要创建临时版本,您可以按照 iPhone 开发门户中的说明进行操作。它类似于进行发布构建,只是使用不同的配置文件。

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.

过去的过去 2024-08-28 21:17:34

Windows iTunes 的临时分发工作方式与 Mac iTunes 的工作方式相同。我按照 Apple 的临时分发说明设置了 Xcode 项目,然后添加了我自己的 Makefile 来创建分发。 Makefile 片段:

AdHoc AppStore : 
    rm -rf iphone/build/$@-${DEVICE_SDK}/${APP_NAME}.app
    cd iphone ; xcodebuild -target ${APP_NAME} \
            -configuration $@ -sdk ${DEVICE_SDK}${SDK_VERSION}
    for f in embedded.mobileprovision CodeResources _CodeSignature/CodeResources ; do \
            [ -f iphone/build/$@-${DEVICE_SDK}/${APP_NAME}.app/$f ] || \
                    { echo BITCH MOAN COMPLAIN : missing $f ; exit 1 ; } \
    done
    mkdir -p ${DISTRO_ROOT}/$@
    [ -f ${DISTRO_ROOT}/$@/[email protected] ] || \
            cp ${PROVISION_DIR}/[email protected] ${DISTRO_ROOT}/$@/[email protected]
    cd iphone/build/$@-${DEVICE_SDK} ; \
            rm -f ${DISTRO_ROOT}/$@/${APP_NAME}.app.zip ; \
            zip -r -y ${DISTRO_ROOT}/$@/${APP_NAME}.app.zip ${APP_NAME}.app
    cd ${DISTRO_ROOT}/$@ ; rm -rf ${APP_NAME}.app ; unzip ${APP_NAME}.app.zip ; \
            codesign -vvvvv ${APP_NAME}.app && rm -rf ${APP_NAME}.app || \
                    { rm -rf ${APP_NAME}.app ; exit 1 ; }
    cd iphone/build/$@-${DEVICE_SDK} ; \
            rm -rf Payload ; mkdir Payload ; \
            ln -s ../${APP_NAME}.app Payload/ ; \
            zip -r ${DISTRO_ROOT}/$@/${APP_NAME}.ipa Payload

我的项目结构是 ./Makefile 和 ./iphone/MyProject.xcodeproj,源代码位于预期位置 ./iphone/Classes/*.[hm]。 Makefile 变量说明:

APP_NAME=whatever_your_app_is_named
DEVICE_SDK=iphoneos
DISTRO_ROOT=/some/path/you/like
PROVISION_DIR=~/Library/MobileDevice/Provisioning_Profiles
SDK_VERSION=3.1.2

我将 Provisioning_Profiles 符号链接到“Provisioning Profiles”以便于键入。我还将该目录中适当的配置文件硬链接为 AppStore.mobileprovision 或 AdHoc.mobileprovision,以便于更新。

步骤本身很简单:清理构建空间,构建应用程序,验证代码签名位是否就位,为发行版准备登陆空间,拉入适当的移动配置文件,压缩应用程序,验证签名,并压缩为 .ipa 文件。 (严格来说,仅 AppStore 需要 zip 文件,AdHoc 需要 .ipa,但我将它们放在一起是为了我自己歇斯底里的葡萄干。:-)

然后,我将 .ipa 和移动配置文件推送到私有文件夹。网站。我的 Beta 测试人员将 .ipa 拉下来并拖放到 iTunes 上。只有当我添加或删除设备时,移动配置才会更改,从而迫使 Beta 测试人员下拉并拖放最新的移动配置文件。

这对我和我在 iClear 上的 Beta 测试人员来说非常顺利(审核中的更新)。

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:

AdHoc AppStore : 
    rm -rf iphone/build/$@-${DEVICE_SDK}/${APP_NAME}.app
    cd iphone ; xcodebuild -target ${APP_NAME} \
            -configuration $@ -sdk ${DEVICE_SDK}${SDK_VERSION}
    for f in embedded.mobileprovision CodeResources _CodeSignature/CodeResources ; do \
            [ -f iphone/build/$@-${DEVICE_SDK}/${APP_NAME}.app/$f ] || \
                    { echo BITCH MOAN COMPLAIN : missing $f ; exit 1 ; } \
    done
    mkdir -p ${DISTRO_ROOT}/$@
    [ -f ${DISTRO_ROOT}/$@/[email protected] ] || \
            cp ${PROVISION_DIR}/[email protected] ${DISTRO_ROOT}/$@/[email protected]
    cd iphone/build/$@-${DEVICE_SDK} ; \
            rm -f ${DISTRO_ROOT}/$@/${APP_NAME}.app.zip ; \
            zip -r -y ${DISTRO_ROOT}/$@/${APP_NAME}.app.zip ${APP_NAME}.app
    cd ${DISTRO_ROOT}/$@ ; rm -rf ${APP_NAME}.app ; unzip ${APP_NAME}.app.zip ; \
            codesign -vvvvv ${APP_NAME}.app && rm -rf ${APP_NAME}.app || \
                    { rm -rf ${APP_NAME}.app ; exit 1 ; }
    cd iphone/build/$@-${DEVICE_SDK} ; \
            rm -rf Payload ; mkdir Payload ; \
            ln -s ../${APP_NAME}.app Payload/ ; \
            zip -r ${DISTRO_ROOT}/$@/${APP_NAME}.ipa Payload

My project structure is ./Makefile and ./iphone/MyProject.xcodeproj with sources in the expected place ./iphone/Classes/*.[hm]. Makefile variable explanations:

APP_NAME=whatever_your_app_is_named
DEVICE_SDK=iphoneos
DISTRO_ROOT=/some/path/you/like
PROVISION_DIR=~/Library/MobileDevice/Provisioning_Profiles
SDK_VERSION=3.1.2

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).

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文