I have one app that is in market on Alpha mode (because the app is only for a resctricted group of persons).
And now I need to have another twin app (also in Alpha), considered "Dev" so, when I'm going to do updates first the them will be available on that version and only after that they will be apllied to that Production.
My workarround to have this version was to create a new app on the store, then create a new app (with different package name) and publish there (I don't know if this is the best way to handle this).
Problems:
I can't have both apps installed simultaneous, when I try to install the the second app store just gives me a error. Same happens when I try to install from xamarin.
I've been searching and everyone says that I need to have a different package name, but I already had it.
Someone knows a solution for this problem? Or a different way to do
I rejected a binary i had which was 1.0 (1.0).
The status went into Rejected by developer.
I went to upload a new binary and ran into this issue, i then saw that i needed to increment my build.
I increased both the app version and build to 1.1, this was a mistake.
I got some error about the app version not matching, understood.
Then i tried app version 1.0 and many different build numbers.
1.1, 1.0.1, 1.2, 1.3, 1.0.3..nothing works.
I keep getting this error. There is only one build listed on itunes connect (1.0)
I tried submitting with no binary and it says i need one.
I even tried changing the app version to 1.1 in itunes connected and then uploading
1.1 (1.0) and that fails as well with the same duplicate issue.
Anyone ever have this issue?
The workaround of changing the build number is working for me, with the following context:
the app version status is "Prepare for submission"
the new version number is well saved in iTunesConnect (pressing the save button on version page in iTunesConnect)
the CFBundleShortVersionString is matching the version number in iTunesConnect (e.g. "1.2")
the CFBundleVersion in the Info.plist is incremented (e.g. 1.2.1)
In this way, several build are associated to the iTunesConnect version.
Here is how it looks like in iTunesConnect (1.2 is the short version number, 1.2 and 1.2.1 are the bundle versions):
I was trying for hours with no luck, after waiting a few more hours i got a reply from apple support asking for more info.
When i went to replicate the issue again for screenshots i decided to use a build number of 2.0, i was hoping maybe it wanted the major version to be higher.
This worked!
Everywhere online that i read said that 1.0 to 1.1 would work fine...or 1.0.0 to 1.0.1.
I, for some reason, had to go from 1.0 to 2.0.
Or there is always the possibility that waiting a few more hours did something.
Solved this issue by incrementing build version by 1 instead of sub-version. i.e. 1.0 to 2.0 instead of 1.0 to 1.1
I experienced this also, just increase the build number fixed it for me. I changed the build version to 1.0.1 and it worked. This can be found in the 'General' Tab in Xcode. Make sure you archive and validate again before submitting to App Store.
You need not to change the version number ,just change the Build number. But you should know that the Build number must be higher than last version you had uploaded. For example, your version number is 2.6.8 and Build number is 2.6.8 then you can change the Build number to 2.6.9. If you change the Build number to 2.6.8.0 it will occur a error say that the Build number(2.6.8.0) must be higher than the exist one(2.6.8) . So the key point is Build number.
#Jayprakash Dubey
#Tenaciousd93
Tried many different build numbers myself. The only option that worked for me was to give a 4 figures build number : 1.1.0.1 (1.1 being my app version number on iTunes Connect).
Hope it helps!
I guess, since Apple has integrated test flight into itunesconnect, there is a difference between version and Build (which is the wording they use in project-settings->target->generalScreen) and in info.plist its equivalent is "Bundle Version String short" and "Bundle Version". Here the wording has never made real sense to me.
I have gotten the error with version 2.2 and build 2.2. I changed it to version 2.2 and build 1 (because it was my first upload) and it worked.
For certain reason, Apple provided the build field on the General Tab in Xcode.
I have also encountered this issue and as much as you do, I am getting the same error over and over again even if I was changing the version numbers.
What is suppose to be done here is to update the build number only even using the same version number.
In my case, I have an App version 0.0.1, every time I upload a binary I need to change the build number eg:
Upload build 0.0.0 - Reject Binary and
Upload build 0.0.1 - Reject Binary and
Upload build 0.0.2
I tried ApplicationLoader 2.9.1, it's working for me.
ApplicationLoader 2.9.1 can download from itunes connect.
I've had this problem before and have solved it like you have, by upping my build number every time. It has always worked.
Now however, I am completely stuck. I have just added the Today Extension to my app, and now when I try to upload it always comes back with a 4238, no matter what version / build combination I put in. It's crazy, been at it for 2 hours now.
I'm wondering if there is any way certain build settings could make the uploader think there are 2 binaries?
I have a separate distribution profile for the main app and the extension, I also have 'Build Active Architectures Only' set to NO. That is all I can think of that would mess this up.
Any thoughts?
My issue was that the build number that I was updating in the General tab of Xcode wasn't changing the bundle version in the app's plist - so the uploader thought I was uploading the same build every time no matter what build number I was using. Once I changed the bundle version in the plist, everything worked fine.
I solved same problem...I uploaded a version 1.01 and build 1.1 then I decided to reject this compilation. I Changed on i-tunes version to 1.1 and tried to upload new version 1.1 build 1.1 and I got error. Then I change on xcode to build 1.2 and upload ok.
In my case I had to make build numer higher that last build number I uploaded. I had on iTunes Connect app with build number 3, then rewrote app from scratch and tried to upload new app with build number 1 I got same error, after changing to build number 4 it worked fine.
Check if you have used the run script:
if the answer is yes, then you have to submit your changes to your git server, then the script will increase your build version number automatically!
Solved this problem by Modifying the Build Number under General -> Identity in the Target build of the Xcode project. Afterwards go to the Product menu, select Clean and Build your app.
From Build : 1
To Build : 1.2
Finally, repeat the app submission process by running Product -> Archive and follow the screen prompts.
I have uploaded the app, but for missing screenshots for 3.5", I got the same error.
And could not upload again from xcode.
(So I make an ipa file, in xcode organizer and export as ipa).
But when I press the upload build in the itunesconnect then it take the old uploaded file (give me an option to choose).
And then after saving this, I got the option for submit for review.
(If you go to the pre release tab in itunesconnect, you can see the previously uploaded app.)
I am using TestFlight to distribute test versions of my app to a private group of people. As I am making a lot of updates these days I wonder if some of my testers will get sick of the large amount of update emails they receive.
So I thought it would be a better approach to let the app check for updates when started and than showing a small notification that there is a new version out and to only notify the testers about important updates by mail.
So my question is: Is there a way to retrieve information about new builds by RSS or some other channel?
Thanks.
The TestFlight iOS SDK already supports this for beta versions if you have the SDK integrated into your app:
Beta In App Updates
If a user is using a beta version of your app, you are setting the
UDID, a new beta version is available, and that user has permission to
install it; an in app popup will ask them if they would like to
install the update. If they tap "Install", the new version is
installed from inside the app.
NB: For this to work, you must increment your build version before
uploading. Otherwise the new and old builds will have the same version
number and we won't know if the user needs to update or is already
using the new version.
To turn this off set this option before calling takeOff:
[TestFlight setOptions:#{ TFOptionDisableInAppUpdates : #YES }];
I'm just trying to build my first phonegap app. So I created test AdobeID and make a successful built. But on the very same machine I need to use my company AdobeID login, but I cannot find out how to change it. Every time i run phonegap build it uses that test AdobeID that I provided in the first built.
Any ideas ?
Thanks
You should remove the project from your test ID and log in with your real Adobe ID and then upload it again from scratch, I believe.
If you are doing phonegap on mobile such as iOS, Android, you need to deactivate the test AdobeID.
Another way is to completely uninstall the app.
However, you can only activate each account 6 times. One of the limit Adobe set.
with titanium appcelerator, how do i specify I want to use version X in my project?
how do i know which is the latest version of Appcelerator that I have to use?
Oho.
So in the tiapp.xml file there is this entry:
<ti:app xmlns:ti="http://ti.appcelerator.org">
... other stuff here
<sdk-version>3.1.1.GA</sdk-version>
You'll be wanting to edit that value to the value of the titanium sdk you'd like to use. I uh, i don't quite understand why the "GA" is there, but that appears to be on all the 3.X version\
As for the latest version, i'm unsure. I don't know quite how to check what version you have available.
As for what version Titanium is up to, go to the titanium api homepage and then select the link "QuickStart" - it is a tab-like thingy.
On that page, search for the words "compatibility matrix", and click on that link. I didn't post the link because the simple folks who mind the Titanium website might change it.
On that link, there are a few tables listing what version of the sdk needs which version of android/ios etc. You'll find the latest version they're using there.
Good luck, warrior.