sfdx force:source:pull not recognizing that the application metadata file needs to be pulled when lightning record page assignments have changed

[matthew-allenSFDC]

Summary

Lightning record page layout assignments for app, recordtype and profile are stored in the application metadata files(Application.app-meta.xml) as profileActionOverrides.

After changing the lightning record page layout assignments through lightning app builder, when you issue a force:source:pull you get changes to the profiles and the record page itself. However, the application metadata file is not updated.

You have to update something in the application(such as the description) and then issue the pull again in order to get the application metadata file to update to include the new changes.

Steps To Reproduce:

Repository to reproduce: dreamhouse-lwc

NOTE: If your issue is not reproducable by dreamhouse-lwc, i.e. requires specific metadata or files, we require a link to a simple Salesforce project repository with a script to setup a scratch org that reproduces your problem.

1. Create scratch org
2. Create application
3. Create record type for object
4. Create lightning record page for above object without assigning to a profile or app
5. sfdx force:source:pull
6. Update lightning record page to assign profile and app and record type.
7. sfdx force:source:pull

Expected result

Application.app-meta.xml file should be updated to include the profileActionOverrides for the recordPage, recordtype, and profile.

Actual result

Profile and recordtype files are the only ones update.

System Information

{ "cliVersion": "sfdx-cli/7.173.0", "architecture": "darwin-x64", "nodeVersion": "node-v16.17.1", "pluginVersions": [ "@oclif/plugin-autocomplete 1.3.1 (core)", "@oclif/plugin-commands 2.2.0 (core)", "@oclif/plugin-help 5.1.14 (core)", "@oclif/plugin-not-found 2.3.3 (core)", "@oclif/plugin-plugins 2.1.1 (core)", "@oclif/plugin-update 3.0.2 (core)", "@oclif/plugin-version 1.1.2 (core)", "@oclif/plugin-warn-if-update-available 2.0.6 (core)", "@oclif/plugin-which 2.1.0 (core)", "alias 2.1.5 (core)", "apex 1.3.0 (core)", "auth 2.2.14 (core)", "community 2.0.7 (core)", "config 1.4.21 (core)", "custom-metadata 2.0.1 (core)", "data 2.1.4 (core)", "generator 2.0.6 (core)", "info 2.1.10 (core)", "limits 2.0.5 (core)", "org 2.2.9 (core)", "packaging 1.9.4 (core)", "schema 2.1.10 (core)", "signups 1.2.7 (core)", "source 2.0.19 (core)", "telemetry 2.0.2 (core)", "templates 55.1.0 (core)", "trust 2.0.4 (core)", "user 2.1.12 (core)", "@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)", "salesforce-alm 54.8.1 (core)" ], "osVersion": "Darwin 21.6.0", "shell": "zsh", "rootPath": "/Users/matthew.allen/.local/share/sfdx/client/7.173.0-5858bb0" }

Additional information

Feel free to attach a screenshot.

[github-actions[bot]]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[git2gus[bot]]

This issue has been linked to a new work item: W-11999574

[mshanemc]

this is a bug on server-side source tracking (the table the CLI queries to ask what's changed). I'm going to get it to the team that owns this type (CustomApplication). If you have the ability to open a case, that'll help get this prioritized.

[github-actions[bot]]

We have determined that the issue you reported exists in code owned by another team that uses only the official support channels. To ensure that your issue is addressed, open an official Salesforce customer support ticket with a link to this issue. We encourage anyone experiencing this issue to do the same to increase the priority. We will keep this issue open for the community to collaborate on.