Hello, i tried Putting build 3 Versionname 3.1 and i get this log :
Texte collé(2).txt (14.9 KB)
From what i found the error changed to:
CFBundleShortVersionString value of 3.1 does not match the value of 1.0 specified in the request.
This confirms that App Inventor correctly changes the version inside the generated IPA, but the upload request itself remains fixed to version 1.0.
It looks like it should work given that you have a version 1.1 set up in App Store Connect and that your version number is 1.1 in your publish settings, so I am not entirely sure where the 1.0 string is currently coming from.
I am looking into seeing whether switching the backend tool we use to perform uploads will be more robust to this failure mode.
should i perform another test ?
Can you test vC=2 and vN=2.1 as sequential nombers from the prior version in TestFlight. These AI2 project controls are very curious. On the past I had similar problems as you and since then I've been very careful to use always only numbers and always consecutive ones as vC=n - vN =n.1
i tried it, it worked on MIT app , but it didn’t appeared on app store connect
Good. You must wait the initial automatic Apple verification process to put in TestFlight. May be the delay is more than 5 hours or more. You will receive one email from Apple when you will have the app in the Apple TestFlicht.
is it possible it won’t appear because on test flight, i already have a build 2 under version 1.0 ?
hello, so what should i do ?
Ups¡¡¡ It is new for me. May be you can expire this TestFleiht version and repeat the process with versionC=3 / versionN=3.1. Or wait more time to receive an Apple mail about it. Sorry, for me is the first time with this scenario.
@ewpatton can you help here?
@ewpatton Until the MIT team review this issue may be would be good to put in the iOS Builder documentatiot that the VersionCode must be always numerical and serial consecutive whit the prior VersionCode (VersionCode=”n”) and the VersionName must be “VersionCode.1”. I dont know if others formats run well, this format seems runs well.
Currently this situation creates a lot of confusion because the AI2 Builder, with these VersionCode and VersionName concepts, behaves very strangely and confusingly for users (it would be good for iOS developers to have clear rules on how they should work and what means every code in the Apple platform). Off course, with the right rules also for the Android platform becasue the fields are the same for both platforms.
Thanks
it is expired for about 20 days 
May be can you expire manually in the TestFleight
i did since the beginning of august
is there another builder ?
https://code2.appinventor.mit.edu (beta)
Keep attention about import keystore from the other platafomr.
The same problem here: Uploading APPS directly to Appstore
i tried using the code2 server, and got the same result !
I did a few more tests after your reply.
With VersionName = 3.1, Apple reports:
CFBundleShortVersionString value of 3.1 does not match the value of 1.0 specified in the request.
So the generated IPA is clearly using the updated VersionName, while the value “1.0 specified in the request” remains unchanged.
I also tested changing the iOS minimum SDK, with no effect.
I also tested the same project using the Code2 iOS build server.
The result is identical to the official MIT server: the generated IPA reflects the new VersionName, but Apple still reports that it does not match the value 1.0 specified in the request.
This suggests the issue is not specific to one build server instance.
Yes, I tried to update an app today and actually encountered a very similar error:
STATE_ERROR.VALIDATION_ERROR, status: 409, title: Validation failed, detail: Info.plist value mismatch. CFBundleShortVersionString value of 1.2 does not match the value of 1.1.0 specified in the request.
At first, I created a new version in App Store Connect and named it 1.1.0. Apple didn't accept that, so I renamed it to 1.2. The same error occurred again after that. I tried it twice more after reloading the browser for App Store Connect and AI2. Then I increased the build version number to 5, and it worked. 
The whole thing is very strange.
