CONFIG_CHIP_LAST_FABRIC_REMOVED_ERASE_AND_REBOOT Not Working

[BilalAliAhmad]

nRF connect SDK 2.7.0 CONFIG_CHIP_LAST_FABRIC_REMOVED_ERASE_AND_REBOOT KConfig option is not working, it is not erasing nvs and not rebooting device. Although I have enabled it like this:
CONFIG_CHIP_LAST_FABRIC_REMOVED_ERASE_AND_REBOOT=y in prj.conf file. 

Also it still says device is already commissioned. 

[Simonr]

Hi Bilal

This is a default setting from the CHIP_LAST_FABRIC_REMOVED_ACTION choice, so it should be automatically enabled in our Matter samples at least, could it be that you just haven't added the common directory to your project, as this is common if you have set up the project from "Create new app from sample" in VS Code, which doesn't copy the common/folders.

Best regards,

Simon

[BilalAliAhmad]

do you mean I need to manually copy common directories to my project? But his already being used through Cmake file:

# Include all source files that are located in the Matter common directory.

include(${ZEPHYR_NRF_MODULE_DIR}/samples/matter/common/cmake/source_common.cmake)

[Simonr]

Are you certain these are actually included when you build your project on your end? That the CMake file is indeed adding the entire common folder here. 

Best regards,

Simon

[BilalAliAhmad]

Yes I am sure because app_task.cpp file use all matter server related initializations from common directory and it is working fine. There seems to be some issue with CONFIG_CHIP_LAST_FABRIC_REMOVED_ERASE_AND_REBOOT.