I already have existing app which its bundle identifier start with digit.
The app is transferred from third party to our account.
Here is the bundle id SS from itunesconnect
Xcode however, always replacing first digit of my bundle id with dash
4UDBLABLA.com.company.appname => -UDBLABLA.com.company.appname
I've try some workaround to keep my original bundle id, but also get replaced with dash when uploading to app store
How can i upload my app with these bundle id?
Xcode version: 8.2.1 (8C1002)
System Information:
OSX El Capitan 10.11.6
There are not a lot of details here. But I was there yesterday, and I know how hard it can be to describe. You type the bundle ID in correctly, and it keeps putting back the same mistake. I had the same problem - the first character (a number) was automatically replaced by a '-'.
In Xcode, search through the project for the good part of the address. In your example, search for 'UDBLABLA.com.company.appname'. I found the entry that kept going wrong, and a more obscure second copy that it had presumably created for itself somewhere deep in the settings. When I fixed that second copy (there were several entries for different sorts of build, but they were all in the same place), all was well. Until the next thing.
Related
I'm in the process of "rebranding" an existing app of mine, which has been on the App Store for 3 years.
This includes a new app name which should be reflected in the whole Xcode project as well.
The rebranded app should roll out as an update for all existing installations.
I've successfully followed the instructions given here:
How do I completely rename an Xcode project (i.e. inclusive of folders)?
(Additionally, I've changed the bundle name in the info.plist.)
with one exception: Changing the product bundle identifier in the build settings. I guess that's the only place I have to keep the old name so that AppStoreConnect realises this actually is the old app?
Is that so, if not, which is the setting that is needed to identify this as the old app?
Your app is identified using the Bundle Identifier only. You should not modify it. You can change almost everything else.
Note that you cannot reset the Version and Build numbers back to 1 and their values should be greater than the last numbers you used to submit your app.
Alright, I'm trying to upload my first app to the App Store, at first it got rejected due to a simple bug, But I can't figure out how to re upload the fixed version to iTunes Connect. When I try to send it through Xcode ou Application Loader, I get the following error:
The bundle uses a bundle name or display name that is already taken.
The app's version is 1.0, the build number is 1. I can't figure out how to replace the older rejected compilation with the new one. Every time I try sending a new compilation, I get this error. I already tried changing the app's version and bundle numbers. I also can't make a new version or even delete the app from iTunes Connect.
I'm using Xcode 9.
I probably rejected the rejected build, so the app's status is "ready to send" again, like in the beginning.
The error you have mentioned, does not seem to be about the version, but rather the app name. Its been asked and answered already
For versioning :
Read the Technical note on Version Numbers and Build Numbers.
Specifically :
For every new build you submit, you will need to invent a new build
number whose value is greater than the last build number you used (for
that same version).
You you will have to bump your build number.
Turns out it was the app's name (Display name)! Looks like that if you compile it with a different display name than what's on iTunes Connect, it will get you that error!
I am working on some Swift code with my children. We would like to work from a shared codebase, so that we can each grab the code, then build and install the app onto our phones.
When I grab the source code my daughter wrote, I get the errors:
The app ID "com.example.OurApp" cannot be registered to your development team. Change your bundle identifier to a unique string to try again.
and:
Xcode couldn't find a provisioning profile matching 'com.example.OurApp'.
If I change the Bundle Identifier value in XCode to something globally unique, everything works. But I don't want to do that because then it is confusing what changes should be committed and/or shared.
The Bundle Identifier value seems to be statically attached to the project files, and those project files need to be checked into to source control, which means that we have to manually muck with that value before we can build and sign our app so that we can run it on our phone.
We each have a developer account that gives us the ability to sign an ipa with our certs, which allows us to install builds on our phone.
I think I want to make the Bundle Identifier dynamic based on the machine or user that is building it.
I think I want to type com.myfamily.$(SOME_ENV_VARIABLE).OurApp into the Bundle Identifier box in XCode, and then commit that file so that any of us can just grab the code, mess with the code, then install the signed ipa on our phone without changing any of the XCode project file values.
No matter what I type into the "Bundle Identifier" box in XCode, the resulting value in the plist within Build/Products/.../Info.plist is garbage. Even changing some .swift files causes this plist to change to some junk value.
How do I make it so that I can share an XCode project with my family such that we can each sign and run the app, without changing or git-ignoring any of the project files/plists?
We are using XCode 8.3.x and running iOS 10.
My client is trying to install a build. Everytime, it hangs at 90%. Sometimes they leave it -- still hanging -- and check the app and see the version numbers as incremented.
This time though, they've left it running there for 5 minutes and still the version hasn't updated.
They removed the app and tried to install again and it's not installing, just hanging. How do I fix this?
I had this same issue and worked with Apple for literally a month going back and forth with there engineers. In my case it was my build number had a 0 after a . which for some reason they have a bug that considers that an 'old' version of your app.
Maybe you are having the same issue:
OK = Build #: 2015.6.29
Not OK = Build #: 2015.06.29
I know it sounds ridiculous but that was the fix for my issue. Not also Apple made mention that I shouldn't start my version number with 0 either, but I can not confirm that.
I ran into this same problem today but only used external testers, so while I suspect the following should apply to internal testers, I can’t confirm. Here is what I found in the documentation:
From App Distribution Guide: Setting the Version Number and Build String
The build string represents an iteration (released or unreleased) of the bundle and is also a two-period-separated list of positive integers, as in 1.2.3. For Mac apps, the user can click the version number in the About window to toggle between the version number and the build string. For details on possible values, see CFBundleVersion in Information Property List Key Reference.
Information Property List Key Reference is in documentation for Core Foundation Keys:
CFBundleVersion (String - iOS, OS X) specifies the build version number of the bundle, which identifies an iteration (released or unreleased) of the bundle. The build version number should be a string comprised of three non-negative, period-separated integers with the first integer being greater than zero. The string should only contain numeric (0-9) and period (.) characters. Leading zeros are truncated from each integer and will be ignored (that is, 1.02.3 is equivalent to 1.2.3). This key is not localizable.
It should have been a tip-off that my new build showed up in TestFlight as 1.1, instead of the 1.01 in my Xcode project.
We got into this situation two different ways. It started off by submitting a build, call it 0.9.1. Everyone was happy and could install.
We then submitted 0.9.2, somehow the provisioning profile became invalid after submitting. The result was that folks would get to 90% then be told that it could not be installed.
After we discovered that the profile had gone invalid, we turned off the switch for TestFlight testing. Users that continued to follow the email link would be presented with 0.9.2 even though the build wasn't available and would get the same 90% experience. For these users, we could instruct them to tap the "Close" at the top left where they would return to the list of apps in TestFlight and there they could tap on 0.9.1 and be good to go.
After this I invited some new testers. All of the new tester receive invites for 0.9.2 even though it is disabled, and there doesn't seem to be a way to help them. We are just going to have to submit a new build.
I am building an app whose name starts with a digit rather than an alpha character. Xcode4 insists on converting a digit in the first position of the product name to a hyphen in the bundle identifier. I know I can override the bundle name in the info.plist file and replace ${PRODUCT_NAME:rfc1034identifier} with a literal such as 22catch.
If I do this, is it going to cause me any problems further down the line when I come to upload the project to the appstore for approval?
Thanks
No it will not create any issue. You can also change bundle identifier. It is not necessary to use Exact an me of project in Bundle identifier. You can use different one
In best of my knowledge , when you upload in Appstore , in that time there you will give a app name .
so I think it will not create any issue in future.