My app has three schemes, for each of my distribution channel:
Savings: App Store
Savings Setapp: Setapp
Savings Direct: Developer ID signed distribution
Of these three, I want to include the Sparkle framework (for updating app) only for Savings Direct.
My Podfile looks like this:
As you can see, "Sparkle" is added to the target GreenBooks. I only have a single target:
What I want to do is for schemes other than "Savings Direct", exclude the Sparkle framework; that is, don't include in the app at all.
How do I do that?
Found the answer. Just need to specify build configuration (configuration) when inputting the Pod entry:
https://guides.cocoapods.org/syntax/podfile.html#pod
Related
I need to publish 2 clients to 1 source code. How do I do it?
I read this article.
How do I build different versions of my Flutter app for qa/dev/prod?
However I could not find the answer from this article.
Is it possible to publish 2 application in same source code and same Key file and same version code and same version name(com.eclipse.side)?
In order publish the same source code into 2 different applications, for example if you have a paid version and a free version of your application you need to use flutter flavors
Basically, it will create 2 different applications that can be uploaded to the stores with the same code, with slight changes in the application Id for example
So, Is it possible to publish 2 application in same source code
Yes. It is irrelevant how you create your app.
and same Key file
Yes, however it's not really recommended
and same version code
Yes, version code is just a version number of your specific app only.
and same version name(com.eclipse.side)
Yes, versionName string used as the version number shown to users. Not sure you meant that one really as noone puts package id there though.
So the only thing that matters globally is application id from your manifest and it must be unique across whole play store submitted apps.
EDIT
my question is, can to publish 2 application with same package name?**
Again, there's no such thing as package name. It's application id that matters only. All the other things are just labels. If you want to release two apps both can show "My App" label. But one mush have different application Id than other (i.e. com.company.app1 and com.company.app2). That's it - so ensure your flavours set different application id and you should be good.
I want to submit my app on app store.All step i understand well But little confusing about version Number.I have following query.
1- Is it compulsory to put version number numeric only like e.g- 1.0,1.1 etc?
2- Can we put any text instead numeric value on the version number like e.g- hair style, maintain body?
Thanks in advance.
Here is the guide
It says this about the version number:
Numbering should follow typical software versioning conventions (for example, 1.0 or 1.0.1, or 1.1).
"MyApp v.maintain body" makes no sense and cannot be compared for update notifications, etc.
We followed following steps and found strange output.
What would be possible reasons for these?
Steps:
Created ipa's for 2 different applications using 2 different distribution profiles (both the profiles belongs to 2 different developer accounts) but keeping bundle id same.
Actual Output: Both ipa's where treated as same i.e. 2nd ipa overridden the 1st one.
Expected Output: Both ipa's should be treated as different i.e. 2nd ipa shouldn't override 1st one.
Surprisingly same output was observed for same applications.
Thanks in advance.
iOS uses bundle identifier to distinguish applications from one another. If you sign two application using similar bundle identifier and try to install one after then it will show similar behavior(Actual output).
For example one application you com.example.user.zzz and another application has same id then iOS will treat them as same application. Installation/Removal of one over other will depend on the order of installation and application version.
So in your case you should provide two different bundle ids so that iOS can distinguish them.
Thanks,
I am preparing to submit an app to the App Store and have come across the following form. In the past when I have done this incorrectly it caused me a lot of grief which I would like to avoid this time around.
It is giving me a few options to choose from, but I'm not sure which one is correct. I would assume there is a way to check my Xcode project to be sure that the bundle IDs match. More specifically I would think that the form below would correspond to my bundle id name
where if my app is called AWESOMEAPP the correct bundle to choose should read EricBrotto.AWESOMEAPP or EricBrotto - *. In fact I don't have either as an option. What I do have is ericbrotto - *. That said could I just choose this one and change my Bundle identifier to ericbrotto.${PRODUCT_NAME:rfc1034identifier}?
Any clarification would be great!
I would get rid of the dollar signs, and enter explicitly com.ericbrotto.myawesomeapp into all of the provisioning portal, iTunes Connect and the Xcode Target Build settings. Or use a wildcard just for the provisioning profile.
Can't figure out how to populate CFBundleVersion dynamically with ${BUNDLE_VERSION} which I would like to define as
BUNDLE_VERSION=`date "+%y%m%d"`
If you're doing command-line builds with xcodebuild, you can do something like
xcodebuild -target MyApp -configuration AppStore BUNDLE_VERSION=`date "+%y%m%d"`
However, I advise against doing this. An App Store app has three versions:
The iTunes Connect version number (this is the only one normally shown to the user)
CFBundleVersion
CFBundleShortVersionString
I think they're all supposed to be of the form [0-9]+.[0-9]+(.[0-9]+)?. To avoid confusion, I set them all to the same thing for App Store builds (we include CFBundleVersion/CFBundleShortVersionString in bug reports, and it's nice if they match CFBundleVersion). Non-App Store builds can include more info, since they don't need to be submitted.
I don't know if iTunes Connect lets you submit an app with CFBundleVersion that doesn't contain a ".", but I haven't extensively tested this.
You’ll need an Xcode configuration file and a configuration variable that you set at build time. This is described in some detail at Diego Massanti’s blog. You’ll need to modify the build phase he describes to set the variable to the current date instead of incrementing the existing value.