Skip to content

Provide default Info.plist for *_application rules#2919

Open
ssarad wants to merge 5 commits intobazelbuild:mainfrom
ssarad:sp/infoplist-optional-ios-application
Open

Provide default Info.plist for *_application rules#2919
ssarad wants to merge 5 commits intobazelbuild:mainfrom
ssarad:sp/infoplist-optional-ios-application

Conversation

@ssarad
Copy link
Copy Markdown
Contributor

@ssarad ssarad commented Apr 19, 2026

Fixes #1858

The issue is quite old but we're currently at a larger monorepo with several apps so I figured this would be nice to get in. In this PR, I focused mostly on ios_application but happy to hear some thoughts if we want to expand this towards *_application

Copy link
Copy Markdown
Member

@keith keith left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is the way that xcode treats this plist just that it's a default and if you have custom stuff? or does it always merge it in to whatever you provide too? if it's the latter i wonder if instead of just treating this as a default if we should just do something more like default_plist | user_plist always.

also can this apply to more targets than just ios_application? i assume some others could benefit from this too?

this is very nice to do, i always find this annoying in simple cases

Comment thread README.md Outdated
"ipad",
],
infoplists = [":Info.plist"],
infoplists = [":Info.plist"], # Optional; a default Info.plist will be used if not provided
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
infoplists = [":Info.plist"], # Optional; a default Info.plist will be used if not provided

i think we should toss this from the example. IMO the value of this example is just providing the most minimal info

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, makes sense. Also for

is the way that xcode treats this plist just that it's a default and if you have custom stuff? or does it always merge it in to whatever you provide too? if it's the latter i wonder if instead of just treating this as a default if we should just do something more like default_plist | user_plist always.

Its actually due to some custom stuff but also we are moving towards a monorepo setup so before all apps join, they'd want to evaluate and play around with simple Bazel setup and often times I'm running myself into creating these info.plist which I realized could be much simpler if we just made a default one like Xcode does

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also can this apply to more targets than just ios_application? i assume some others could benefit from this too?

Yeah this was my thinking too - should we expand to all *_applications? I think yes, and I'll do that and make the push, if you feel we want to scope it to just ios_application or macos_application, let me know

@ssarad ssarad changed the title Change ios_application Info.plist requirement to optional Provide default Info.plist for *_application rules Apr 21, 2026
ssarad and others added 2 commits April 21, 2026 00:56
Co-authored-by: Keith Smiley <keithbsmiley@gmail.com>
@ssarad ssarad requested a review from keith April 21, 2026 05:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Feature request: Stop requiring infoplists for applications

2 participants