构建问题:iOS- iOS -Archive on Expo React本机应用程序 - 如何使用Expo CLI提交应用程序和播放商店?
我正在尝试将更新推向我正在为此提供的应用程序和播放商店的更新。
这是一个由Expo构建的React Native应用程序。
大约两年来,该应用程序本身都没有被触及。我的更新很简单 - 修复了几个错别字并从40起更新到SDK 41。
现在,我想将提交更新提交到App Store,但是我仍在使用Expo CL。
我输入:
expo build:ios -t archive
获取:
There is a new version of expo-cli available (5.4.12).
│ You are currently using expo-cli 5.4.11 │
│ Install expo-cli globally using the package manager of your choice; │
│ for example: `npm install -g expo-cli` to get the latest version │
expo build:ios has been superseded by eas build. Learn more: https://blog.expo.dev/turtle-goes-out-to-sea-d334db2a6b60
Run the following:
› npm install -g eas-cli
› eas build -p ios https://docs.expo.dev/build/setup/
expo build:ios will be discontinued on January 4, 2023 (182 days left).
然后进行:
Checking if there is a build in progress...
Accessing credentials for username101 in project hoz
✔ Do you have access to the Apple account that will be used for submitting this app to the App Store? … yes
› Log in to your Apple Developer account to continue
✔ Apple ID: … [email protected]
› Restoring session /Users/myname/.app-store/auth/[email protected]/cookie
› Team Name Corporation (354678UXY)
› Provider Team Name (987654321)
✔ Logged in Local session
✔ Bundle identifier registered com.teamname.ios
✔ Synced capabilities
✔ Fetched Apple distribution certificates
✔ Successfully validated Distribution Certificate against Apple Servers
✔ Fetched Apple push keys
✔ Will you provide your own Apple Push Notifications service key? › Let Expo handle the process
✖ Failed to create Apple push key
Failed to set up Push Key
Failed to prepare all credentials.
The next time you build, we will automatically use the following configuration:
Project Credential Configuration:
Experience: @username/slug, bundle identifier: com.teamname.ios
Provisioning profile is missing. It will be generated during the next build
Apple Team ID: 354678UXY, Apple Team Name: Augmented Reality Sports Management Corporation (Company/Organization)
Distribution Certificate - Certificate ID: 1234567899
Apple Team ID: 2529XVZUYJ, Apple Team Name: Team Name (Company/Organization)
**You can have only two Apple Keys generated on your Apple Developer account.
Please revoke the old ones or reuse existing from your other apps.
Please remember that Apple Keys are not application specific!**
- 我是新人的新手,所以我也想知道,Eas Cli应该 摆脱CLI?
- 获得最新SDK的目标?该应用在40岁时,我应该把它拿到45吗?这做什么?
I am trying to push an update to the app I'm helping with that's already on the App and Play store.
It is a React Native app built with Expo.
The app itself hasn't been touched in about two years. My updates were simple - fixing a couple typos and updating to SDK 41 from 40.
Now I would like to push submit the update to the app store however I am still using Expo CL.
I type:
expo build:ios -t archive
and get:
There is a new version of expo-cli available (5.4.12).
│ You are currently using expo-cli 5.4.11 │
│ Install expo-cli globally using the package manager of your choice; │
│ for example: `npm install -g expo-cli` to get the latest version │
expo build:ios has been superseded by eas build. Learn more: https://blog.expo.dev/turtle-goes-out-to-sea-d334db2a6b60
Run the following:
› npm install -g eas-cli
› eas build -p ios https://docs.expo.dev/build/setup/
expo build:ios will be discontinued on January 4, 2023 (182 days left).
it then goes:
Checking if there is a build in progress...
Accessing credentials for username101 in project hoz
✔ Do you have access to the Apple account that will be used for submitting this app to the App Store? … yes
› Log in to your Apple Developer account to continue
✔ Apple ID: … [email protected]
› Restoring session /Users/myname/.app-store/auth/[email protected]/cookie
› Team Name Corporation (354678UXY)
› Provider Team Name (987654321)
✔ Logged in Local session
✔ Bundle identifier registered com.teamname.ios
✔ Synced capabilities
✔ Fetched Apple distribution certificates
✔ Successfully validated Distribution Certificate against Apple Servers
✔ Fetched Apple push keys
✔ Will you provide your own Apple Push Notifications service key? › Let Expo handle the process
✖ Failed to create Apple push key
Failed to set up Push Key
Failed to prepare all credentials.
The next time you build, we will automatically use the following configuration:
Project Credential Configuration:
Experience: @username/slug, bundle identifier: com.teamname.ios
Provisioning profile is missing. It will be generated during the next build
Apple Team ID: 354678UXY, Apple Team Name: Augmented Reality Sports Management Corporation (Company/Organization)
Distribution Certificate - Certificate ID: 1234567899
Apple Team ID: 2529XVZUYJ, Apple Team Name: Team Name (Company/Organization)
**You can have only two Apple Keys generated on your Apple Developer account.
Please revoke the old ones or reuse existing from your other apps.
Please remember that Apple Keys are not application specific!**
- I'm new to Expo so I would also like to know, is EAS Cli supposed to
get rid of Expo Cli? - Is the goal to get to the latest SDK? The app was at 40, am I supposed to get it to 45? What does this do?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
您可以使用
eas-cli
提交您的应用程序,即使使用expo-cli
构建了应用程序。EAS-CLI将替换与构建/提交/出版以及与服务Expo提供的其他内容有关的功能,但它不包含与本地开发相关的功能,例如
expo start/run:ios/run:ios/run:android/prebuild
没有什么可以阻止您使用较旧的SDK上传STH构建的Expo方面,但是由于缺乏iOS 15支持(也可能是其他原因),因此很可能不会在AppStore中接受。您可以检查 https://blog.expo.dev/ ,有一篇博客文章。每个SDK的重大变化。
You can use
eas-cli
to submit your app even if it was built usingexpo-cli
.eas-cli will replace functionality related to building/submitting/publishing and anything else that is related to services expo provides, but it will not contain functionality related to local development e.g.
expo start/run:ios/run:android/prebuild
There is nothing blocking you on the expo side to upload sth build using an older SDK, but most likely it will not be accepted in AppStore because of the lack of iOS 15 support(and likely other reasons). You can check https://blog.expo.dev/ , there is a blog post that goes through the major changes in each SDK.