-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[apple_asset_catalog] Include Product Type in AcTool Args #2403
Conversation
Hi @ydxia! Thank you for your pull request and welcome to our community.We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
@v-jizhang can you take a look? 🙏 |
For my understanding, should changes target the |
Yes, all PRs will be reviewed and merged here in the master branch. Only selected PRs can be ported to dev. |
ok so |
Bug fixes should be ported to dev too. |
hi - just pinging again here to get a sense of what the expected workflow is and if there's anything needed from my side. Thanks! |
Your PR looks good to me but we 're working on an Open Source plan. Thank you! |
Currently, building Messages extensions with buck will not generate the Messages app icon correctly. This is because in order to do so,
actool
needs to know what product type it is creating an asset catalog + app icon for.This change funnels the product type from apple_bundle into AppleAssetCatalog and AcToolStep so that
actool
is called with--product-type <product type>
(needs to becom.apple.product-type.app-extension.messages
for Messages extensions).