Problem with configuration of SetupFactory in di.xml

[SKovbel]

Had some errors during upgrading Magento2 from version dev60 to dev63 (win & linux).
(p.s. Clear installation was success.)

Fatal error: Call to undefined method Magento\Core\Model\Resource\Setup::getAttribute() in /app/code/Magento/GroupedProduct/sql/groupedproduct_setup/install-0.0.1.php on line 29

Declaration in Magento\GroupedProduct\etc\di.xml doesnt work

    <type name="Magento\Module\Updater\SetupFactory">
        <param name="resourceTypes">
            <array>
                <item key="groupedproduct_setup"><value>Magento\Catalog\Model\Resource\Setup</value></item>
            </array>
        </param>
    </type>

Finished upgrading after changed di.xml (put preference tag instead of the above text, i dont know if it is correct or not, but it works).

    <preference for="Magento\Module\Updater\SetupInterface" type="Magento\Catalog\Model\Resource\Setup" />

And the second similar error
Fatal error: Call to undefined method Magento\Core\Model\Resource\Setup::getLocale() in /app/code/Magento/Usa/sql/usa_setup/upgrade-1.6.0.2-1.6.0.3.php on line 27

    <type name="Magento\Module\Updater\SetupFactory">
        <param name="resourceTypes">
            <array>
                <item key="usa_setup"><value>Magento\Usa\Model\Resource\Setup</value></item>
            </array>
        </param>
    </type>

fixed by

<preference for="Magento\Module\Updater\SetupInterface" type="Magento\Usa\Model\Resource\Setup" />```

[verklov]

@Mackovey , thank you for reporting this to us! The team will look at the issue and we will respond once the analysis is complete.

[verklov]

@Mackovey , the team has looked at the issue. After running the upgrade, please reinit all autogenerating resources. In particular, /var/generation. This should fix the issue you reported.
Please verify if this eliminates the issue and let us know.

[verklov]

@Mackovey, we could not reproduce the initial issue that you reported. However, please take into account that the team periodically makes significant changes , which means that you should completely reinstall Magento when you experience issues similar to this. We know about this issue and cannot do anything about it due to the continuing changes to the product. We expect this issue to be completely eliminated once we finalize making changes to the product architecture.

We are closing this issue.