个人中心
gpt4 book ai didi

changing xcode build number doesn't change in appstoreconnect and remains the same 1.0(更改Xcode内部版本号不会在appstore Connect中更改，并保持不变1.0)

转载 作者：bug小助手 更新时间：2023-10-25 16:34:58 24 4
gpt4 key购买 nike



I have an application in which I want to upload it to testflight, before that the:
version 1.0
build 1.0
now I have an update and when I change it to:
version 1.0
build 1.1
it uploads successfully, but in appstoreconnect, it is processing and after finishing, there is nothing showed as build 1.1, why?!

我有一个应用程序，我想在其中将其上传到TestFlight，在此之前：Version 1.0 Build 1.0现在我有一个更新，当我将其更改为：Version 1.0 Build 1.1时，它成功上载，但在appstore Connect中，它正在处理，完成后，没有显示为Build 1.1，为什么？！


upvoting my question would be appreciated.

提升我的问题，我将不胜感激。


更多回答

Would you mind sharing your pubspec.yaml & info.plist ?

您介意分享您的pubspec.yaml&info.plist吗？

优秀答案推荐

To update the version for the ios build, follow the following steps.

要更新iOS内部版本的版本，请执行以下步骤。



  1. Change the version from pubspec.yaml file, as version: 1.1.0+1



  2. Open the ios folder in Xcode and change the version, as
    enter image description here





  1. Close Xcode and run the following commands in the terminal. flutter clean, flutter pub get, cd ios,



  2. For Mac M1 arch -x86_64 pod install --repo-update


    For Mac Intel pod install --repo-update




and then archive again.

然后再存档。


Must check the version of the newer build from the Organizer Window which will automatically open after successful build or you can open the organizer by pressing Command + Option + Shift + O

必须从构建成功后自动打开的管理器窗口检查较新版本的版本，也可以通过按Command+Option+Shift+O打开管理器



To control for version and build number there is two way

控制版本和内部版本号有两种方法



  1. First one from xCode you can change version and build make sure this below code info.plist


    <key>CFBundleVersion</key>
    <string>$(CURRENT_PROJECT_VERSION)</string>

    <key>CFBundleShortVersionString</key>
    <string>$(MARKETING_VERSION)</string>```



  2. Second if you want use version and build number in yaml file make sure below code in info.plist


    <key>CFBundleVersion</key>
    <string>$(FLUTTER_BUILD_NUMBER)</string>

    <key>CFBundleShortVersionString</key>
    <string>$(FLUTTER_BUILD_NAME)</string>




Note

注意事项


CFBundleShortVersionString refer to version

CFBundleVersion refer to build number

CFBundleShortVersionString参考版本CFBundleVersion参考内部版本号


更多回答

Hello, the version in pubspec.yaml is like that (#version: 1.0.0+1), the same as you mentioned, but what does that mean? I want to understand, is this the version number or build number, and what does +1 means? and about version and build number, I think every version has many build number, but yours is different, your build is 1 but version 1 point something, why?! I think about it like this = > version 1 , build: 1.0 , 1.1 , 1.2, 1.3, 1.4 ...etc but yours is the opposite build 1 , version: 1.0 , 1.1 , 1.2, 1.3, 1.4 ...etc which one is correct?!

您好，pubspec.yaml中的版本是这样的(#Version：1.0.0+1)，和您提到的一样，但是这是什么意思呢？我想知道，这是版本号还是内部版本号，+1是什么意思？关于版本和内部版本号，我认为每个版本都有很多内部版本号，但你的版本是不同的，你的内部版本是1而版本1指向一些东西，为什么？！我是这样想的=>版本1，内部版本：1.0，1.1，1.2，1.3，1.4等，但你的是相反的内部版本1，版本：1.0，1.1，1.2，1.3，1.4...等等，哪一个是正确的？！

Hey, below is the complete breakdown of the version and build numbering system. For example: 1.0.0+1 Version: 1.0.0 Build number: +1 There are three steps in the version. Major Version, Minor Version, and Patch Version. You change the patch version when you fix a bug. and change the minor version when you add a new feature or enhancements. and increment the major version when you make significant changes or introduce backward-incompatible features in your app. and the build number is changed with every new build upload. i'll explain in next comment.

嘿，下面是版本和版本编号系统的完整分解。例如：1.0.0+1版本：1.0.0内部版本号：+1版本中有三个步骤。主要版本、次要版本和修补程序版本。您可以在修复错误时更改补丁版本。并在添加新功能或增强功能时更改次要版本。并在应用程序中进行重大更改或引入向后不兼容的功能时增加主版本。每次上传新版本时，内部版本号都会更改。我将在下一条评论中解释。

You have to change the build number with every new update for the Play Store. for example: 1.0.0+1 When you release the next version of the app you must increment the build number along with the version number. for example: 1.0.1+2, 1.0.3+3, 1.1.0+4 and so on. but for appstore, you can reset the build number for every new version, but if you want to upload the same version to the testflight, you must have to increment the build number. for example: 1.0.0+1, 1.0.0+2, and when you change the version. 1.0.1+1, 1.0.2+1

每次更新Play Store时，您都必须更改内部版本号。例如：1.0.0+1当你发布应用程序的下一个版本时，你必须增加内部版本号和版本号。例如：1.0.1+2、1.0.3+3、1.1.0+4等。但是对于appstore，您可以为每个新版本重置内部版本号，但如果您想要将相同的版本上载到TestFlight，则必须增加内部版本号。例如：1.0.0+1、1.0.0+2以及当您更改版本时。1.0.1+1、1.0.2+1

24 4 0
文章推荐： Object instance still accessible after destruction(销毁后仍可访问的对象实例)
文章推荐： Lexical Analyzer with table-driven and character classification in rust(基于表驱动和字符分类的生锈词法分析器)
文章推荐： Getting Tokyo stock price data to appear on Google spreadsheet(将东京股票价格数据显示在谷歌电子表格上)
文章推荐： How can I change music cover photo using APIC frame in ID3 tag?(如何使用ID3标签中的APIC框架更改音乐封面照片？)
bug小助手
个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章
滴滴打车优惠券免费领取
滴滴打车优惠券
全站热门文章
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com