[Issue] Property "ShowDefaultNotificationMessage" does not have accessor method

[m2-assistant[bot]]

This issue is automatically created based on existing pull request: magento/magento2#26056: Property "ShowDefaultNotificationMessage" does not have accessor method

---

Description (*)

If you want create queue which will triggered whem you will save product in the admin (I created plugin afterSave for the Magento\Catalog\Model\ResourceModel\Product::save()), you will get critical error - Property "ShowDefaultNotificationMessage" does not have accessor method "setShowDefaultNotificationMessage" in class "Magento\CatalogInventory\Api\Data\StockItemInterface". Even if you do not use this interface in your extension, you still get an error.

Fixed Issues (if relevant)

Manual testing scenarios (*)

1. Create simple rabbitmq queue extension
2. Create plugin afterSave for the Magento\Catalog\Model\ResourceModel\Product::save()
3. Set up consumer
4. Save product in the admin panel
5. Run php bin/magento queue:consumers:start YourConsumerName
6. Got error)

Questions or comments

Contribution checklist (*)

• [ ] Pull request has a meaningful description of its purpose
• [ ] All commits are accompanied by meaningful commit messages
• [ ] All new or changed code is covered with unit/integration tests (if applicable)
• [ ] All automated tests passed successfully (all builds are green)

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

:white_check_mark: Jira issue https://jira.corp.magento.com/browse/AC-997 is successfully created for this GitHub issue.

[m2-assistant[bot]]

:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[crippsy14]

Just to confirm, this is still an issue. Can I confirm if the accessor method is being added into the interface?

[mamsincl]

still issue, please

freshly duplicated on 2.4.6-p5 - product pushed to queue initially and failed to hydrated back is obtained by productRepository in adminhtml area

update: as a quick workaround, resetting the related extension attribute (since related interfaces/classes are marked as deprecated, really no see any chance of getting any official solution)

$product->getExtensionAttributes()->setData('stock_item', null);