I am trying to upload a build to the app store but I am getting the issue that it builds successfully but Distribute App does not appears there. It displays like Distribute Content.
Image:
Making sure to have below Build Settings resolved issue for me :
"Skip Install" should always be No for all Application Targets.
"Skip Install" should always be Yes for all other targets(Includes AppClip, Frameworks, Watch Targets).
I solved this by going to 'Build Settings' > 'All' and setting the value of 'Skip Install' to 'No'
I did fixed this issue now. I have just make changes in workspace setting as like below:
1) Goto file -> WorkSpace Setting
2) Make changes in Shared Workspace setting as => Build Systems -> New Build System(Default)
3) Also Make changes in Per-user Workspace setting as => Build Systems -> New Build System
I fixed my problem by keep "Skip install" of Runner No and "Skip install" of Frame work or 3rd parties is Yes
Thanks for the old answers, I have solved the problem by keeping "Skip install" of frameworks to false.
But one thing special is that, runner and framework in my project are in different schemes. Hope the picture will help new comers.
Related
Relatively frequently I need to clean & rebuild because Swift starts to miss things up. But doing so, I am rebuilding Cocoapods dependencies, to no avail.
Can I clean only the project, not the whole workspace?
Thanks,
Zsolt
Go to Manage schemas -> Click Edit button for your active schema -> Select Build target -> Uncheck the "Find Implicit dependencies" checkbox .
I tested the plugin cocoapods-binary and it is working pretty well:
Plugin website: https://github.com/leavez/cocoapods-binary so you have pod as frameworks
Referenced on cocoapods officiel website: https://guides.cocoapods.org/plugins/pre-compiling-dependencies.html
Also, you can use š Rugby.
It caches pods and keeps them on a different path.
So, you can clear DerivedData without losing your pods.
I'm sure this is a dumb mistake on my part but I can't find the right answer.
I have a project that has a snapshot dependency on another project. For sake of discussion website is dependent on toolkit.
Monitoring the build folder:
c:\programs\Teamcity\buildagent\work
I see the toolkit get built and the folders all exist as expected:
c:\programs\teamcity\buildagent\work\toolkit
Then the website build kicks off and the folder above gets deleted before the website build starts.
This results in the website saying the reference couldn't be found. What setting am I missing?
Using TeamCity 7.1.2, working on getting it upgraded to 8.1 but it requires some internal evaluation first.
Don't think its a version issue. How do both of your builds know where to put the artefacts at . For ex teamcity normally builds stuff at c:\programs\teamcity\buildagent\work****\toolkit , not at c:\programs\teamcity\buildagent\work\toolkit ?
Also, if your targets are dependent upon each other across builds, (1) have you setup any artefact dependencies or (2) any process that does not read of a shared agent workspace ? or (3) forcing both builds to run from the same directory
See if both your builds are running on the same target "folder name". In case they are , deselect any option that "cleans up build targets" before they run.
Also, you might want to check your build files to see if they have any code to clean directories before they start to run
It seems that XCode always builds both Debug anŠ² Release configurations (see screenshot attached). I can't untoggle "Profile" option. I need to build Debug version only in 95% of my time. How can I save time by not building Release version every time I press "Build"?
By default, XCode practically always build for Debug, in Release XCode build only when you select from menu Archive or to Profile (shortcut cmd+I) and you see this because when selected you see XCode build your project.
The tab you selected just shows the target(s) (MagicCards1 here) that will be built for each action (Run, Profile, Archive...).
Only one build will be made with the appropriate build configuration (Debug, Release, ...) for any given action: your screenshot shows that the 'Debug' configuration will be used to build your target when you run your project, leading me to think that Xcode already does what you're expecting (and that it'll only compile the source files that changed since the last build).
You can try to compare Debug and Release builds made from scratch by cleaning (Shift+Cmd+K) and building (Cmd+R) with different build configurations in the scheme's Run settings.
You should also check if 'Build Active Architecture Only' is set to Yes and if 'Analyze during Build' is set to No in your Build Settings:
You may also want to watch this WWDC 2013 video: Xcode Core Concepts 401. Schemes are covered around the 44'-mark.
https://developer.apple.com/videos/wwdc/2013/?include=401#401
The tile basically says it all.
I'm developing a mac app which has the normal app target, but also has two more command-line tool targets whose products are copied to the app when building. I remember seeing somewhere that the "Skip install" was important in these cases, but I remember nothing of what I read, so this might be incorrect.
Anyway, I just wanted to know what this option affects.
I believe this only matters when you're developing for the App Store. If you archive your app target and this includes building other targets (command line tools, static libraries, ...), all the targets' products are copied into the archive, unless SKIP_INSTALL is set to YES.
You can verify this: Archive your application, find the archive in the Organizer, Option-Click --> "Show in Finder", go into the archive (Option-Click --> "Show Package Contents"), and in /Products you will find multiple files/folders. However, App Store builds only allow one product within the Products directory. Xcode warns you about this if you "Validate" your archived app in the Organizer:
When you set SKIP_INSTALL=NO (which is the default), the build target will be installed to $(DSTROOT)$(INSTALL_PATH) during the build phase. Setting SKIP_INSTALL=YES causes the target to be built but not installed.
Setting SKIP_INSTALL=YES can be useful for static archives (libsomething.a) that will be later linked into other targets or bundles that will be installed by another target's copy-files build phase.
Skip Install (SKIP_INSTALL)
In case with archive
xcodebuild archive SKIP_INSTALL=NO
NO - allows to put data into <some_path>/<some_name>.xcarchive/Products or install a framework in archive
When following the apple doco here for archiving an application, i.e. setting "Skip Install build setting" to YES, when I do then go Product->Archive it does not show up in Organizer/Archives.
However if I ignore the doco and leave "Skip Install build setting" as NO, then I do get a resultant archive appearing in Organizer.
Question - What setting should I be using to make sure the archive is good for distribution? If the answer is by setting (ie. "Skip Install build setting" ) it to YES, then how do I get around the fact the archive in this case doesn't appear in Organizer?
You should set the SKIP_INSTALL build setting for all targets in a scheme but your application, i. e. for all dependencies like frameworks and libraries. Donāt set it for the application target itself.