*.profile-meta.xml files are not pulled after object deletion

Summary

After custom object deletions in a scratch org, files related to profile are not updated by sfdx force:source:pull command.

Steps To Reproduce:

1. Create a new scratch org.
2. Open the new scratch org.
3. Create a new Custom Object.
4. Retrieve modified metadata with sfdx force:source:pull
5. Verify the profile files are referencing, for instance, the new custom object layouts.
6. In the scratch org, delete the created Custom Object
7. Retrieve the metadata using sfdx force:source:pull again

Expected result

The *.profile-meta.xml files doesn’t contain any reference to deleted custom object assets.

Actual result

The *.profile-meta.xml files keeps references to deleted custom object assets. This will cause failure to any upcoming sfdx force:source:push execution.

Additional information

Created Object:

Retrieved metadata using sfdx force:source:pull

Retrieved metadata after custom object deletion.

Content of profile-meta.xml files after custom object deletion and pulling of scratch org source code.

ERROR: result of sfdx force:source:push -f into a new scratch org with the last pulled source code version:

SFDX CLI Version: sfdx-cli/6.50.0-9817aece8a (darwin-x64) node-v8.9.4

OS and version: darwin18 (MacOS Mojave)

[clairebianchi]

@sauloefo Thank you for the offer, but sadly this part of our codebase is not currently public.

[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.