--- title: Dynamically generated Info.plist files with Tuist 0.15.0 description: Tuist 0.15.0 adds a new defaultSettings attribute for controlling generated build settings (.recommended or .essential), turns Info.plist into its own model in... canonical: https://daily.dev/posts/dynamically-generated-info-plist-files-with-tuist-0-15-0-mbo4rx36m twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Dynamically generated Info.plist files with Tuist 0.15.0 | daily.dev og:description: Tuist 0.15.0 adds a new defaultSettings attribute for controlling generated build settings (.recommended or .essential), turns Info.plist into its own model in... og:url: https://daily.dev/posts/dynamically-generated-info-plist-files-with-tuist-0-15-0-mbo4rx36m og:image: https://api.daily.dev/og/posts/Mbo4RX36m.png og:image:alt: Dynamically generated Info.plist files with Tuist 0.15.0 og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Dynamically generated Info.plist files with Tuist 0.15.0 **[ Tuist ](https://daily.dev/sources/tuist-blog)** · 4 min read · 0 upvotes · 0 comments ## Summary Tuist 0.15.0 adds a new defaultSettings attribute for controlling generated build settings (.recommended or .essential), turns Info.plist into its own model in preparation for letting Tuist manage its content, prints total generation time after running tuist generate, adds support for customizable schemes, and enables setting compiler flags on source files. Several bug fixes are also included, covering project generation format inconsistencies, code sign on copy defaults, duplicated localized resources, and bundle dependency handling. The team also mentions upcoming work to integrate Tuist with Xcode's newly announced native Swift Package Manager support. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I control the default build settings Tuist generates for my Xcode project? Pass the defaultSettings attribute to the Settings model in Tuist, choosing either .recommended for a fuller set including warning flags to catch bugs early, or .essential for a minimal set needed to compile, such as PRODUCT_NAME and TARGETED_DEVICE_FAMILY. This defaults to .recommended for backwards compatibility, or you can pass nil to disable generated settings entirely, available starting in Tuist 0.15.0. _daily.dev surfaces release notes like this for developers tuning Xcode build configs with Tuist._ ### Can Tuist generate custom Xcode schemes instead of just default ones? Yes, as of Tuist 0.15.0 schemes are configurable using a Scheme model that accepts a name, shared flag, buildAction, testAction, and runAction, letting you define exactly which targets are built, tested, and run. Before this version schemes were not customizable and Tuist only generated a default scheme per target. _Track tooling updates like this when scripting Xcode project generation workflows on daily.dev._ ### Does Tuist support setting compiler flags on individual source files? Yes, starting in Tuist 0.15.0, compiler flags can be passed alongside source file globs when defining a Target, for example specifying a flag string next to a sources path like Sources/**/*.m. This was not previously possible even though Xcode itself rarely uses the feature. _Developers configuring per-file build settings can follow tool updates like this on daily.dev._ --- Tags: [#ios](https://daily.dev/tags/ios), [#swift](https://daily.dev/tags/swift), [#xcode](https://daily.dev/tags/xcode) [View this post on daily.dev](https://daily.dev/posts/dynamically-generated-info-plist-files-with-tuist-0-15-0-mbo4rx36m) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Dynamically generated Info.plist files with Tuist 0.15.0","url":"https://daily.dev/posts/dynamically-generated-info-plist-files-with-tuist-0-15-0-mbo4rx36m","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/dynamically-generated-info-plist-files-with-tuist-0-15-0-mbo4rx36m"},"datePublished":"2026-08-23T12:23:37.393Z","dateModified":"2026-08-23T12:55:05.423Z","description":"Tuist 0.15.0 adds a new defaultSettings attribute for controlling generated build settings (.recommended or .essential), turns Info.plist into its own model in...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3291e22717bab4faad3c0ed92b980dc7?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/3291e22717bab4faad3c0ed92b980dc7?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"\n Tuist\n ","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"\n Tuist\n ","logo":"https://media.daily.dev/image/upload/s--3AYDH23h--/f_auto,q_auto/v1787487506/logos/tuist-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/tuist-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/dynamically-generated-info-plist-files-with-tuist-0-15-0-mbo4rx36m","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ios,swift,xcode","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"\n Tuist\n ","item":"https://daily.dev/sources/tuist-blog"},{"@type":"ListItem","position":3,"name":"Dynamically generated Info.plist files with Tuist 0.15.0"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/dynamically-generated-info-plist-files-with-tuist-0-15-0-mbo4rx36m#faq","mainEntity":[{"@type":"Question","name":"How do I control the default build settings Tuist generates for my Xcode project?","acceptedAnswer":{"@type":"Answer","text":"Pass the defaultSettings attribute to the Settings model in Tuist, choosing either .recommended for a fuller set including warning flags to catch bugs early, or .essential for a minimal set needed to compile, such as PRODUCT_NAME and TARGETED_DEVICE_FAMILY. This defaults to .recommended for backwards compatibility, or you can pass nil to disable generated settings entirely, available starting in Tuist 0.15.0. daily.dev surfaces release notes like this for developers tuning Xcode build configs with Tuist."}},{"@type":"Question","name":"Can Tuist generate custom Xcode schemes instead of just default ones?","acceptedAnswer":{"@type":"Answer","text":"Yes, as of Tuist 0.15.0 schemes are configurable using a Scheme model that accepts a name, shared flag, buildAction, testAction, and runAction, letting you define exactly which targets are built, tested, and run. Before this version schemes were not customizable and Tuist only generated a default scheme per target. Track tooling updates like this when scripting Xcode project generation workflows on daily.dev."}},{"@type":"Question","name":"Does Tuist support setting compiler flags on individual source files?","acceptedAnswer":{"@type":"Answer","text":"Yes, starting in Tuist 0.15.0, compiler flags can be passed alongside source file globs when defining a Target, for example specifying a flag string next to a sources path like Sources/**/*.m. This was not previously possible even though Xcode itself rarely uses the feature. Developers configuring per-file build settings can follow tool updates like this on daily.dev."}}]} ```