An iOS project can compile and run successfully without a Main.storyboard
.
The default Info.plist
generated by tuist
includes the value "Main.storyboard"
for the key "UIMainStoryboardFile"
.
In this case, running the project generated by tuist will crash at runtime because "Main.storyboard"
is declared in the target's "Info.plist"
, but the storyboard file is not present.
The default Info.plist
generated by Tuist should be the minimum essential necessary one to successfully compile and run an app.
Extend the interface of InfoPlist:
essential
, just as was done with build settings.extendingEssential(with: [String: Value])
, just as it's handled now to extend the default case..extendingDefault
case setting an empty string (""
) as value for the key "UIMainStoryboardFile"
..default
case to generate an Info.plist
file. Instead, use an explicit Info.plist
file and reference it with the file(path: Path)
case.Adding cases to InfoPlist
will not break the current API.
The idea of an essential Info.plist
is similar to the idea of the essential Build Settings
, so, it's consistent with already existing functionalities/concepts.
The new cases should be documented here.
Info.plist
" still valid?Info.plist
on Tuist looks like the one generated by previous versions of Xcode (before introducing Scenes).default "Info.plist"
also includes an "UIApplicationSceneManifest"
key.Having this in mind, should the "default Info.plist
"...
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too