requirement changes from Typo3 v9 -> v10

[tobiasd]

Hey there, I'm fairly new to Typo3 CMS so this might be an issue with the sitepackagebuilder or not ;-) If not any hint for the root of my problem would be highly appreciated.

I started with a fresh installation of Typo3 v10.2 with the Bootstrap extension installed and then followed the Video Tutorial on youtube about the sitepackage to create a new template. To adopt the generated package from Typo3 v9 and Bootstrap 10 I changed

'constraints' => [
    'depends' => [
        'typo3' => '8.7.0-9.5.99',
        'rte_ckeditor' => '8.7.0-9.5.99',
        'bootstrap_package' => '10.0.0-10.0.99'
    ],
    'conflicts' => [
    ],

to

'constraints' => [
    'depends' => [
        'typo3' => '10.2.0-10.2.99',
        'rte_ckeditor' => '10.2.0-10.2.99',
        'bootstrap_package' => '11.0.0-11.0.99'
    ],
    'conflicts' => [
    ],

in ext_emconf.php. After some minor changes to the generated template (exchange logo image, setting the primary color for Bootstrap) I got the following error message from Typo3 when calling the entry page

Core: Exception handler (WEB): Uncaught TYPO3 Exception: Argument 1 passed to TYPO3\CMS\Frontend\Controller\ErrorController::pageNotFoundAction() must implement interface Psr \Http\Message\ServerRequestInterface, null given, called in /var/www/typo3_src-10.2.2/typo3/sysext/frontend/Classes/Controller/TypoScriptFrontendController.php on line 1361 | TypeError thrown in file /var/www/typo3_src-10.2.2/typo3/sysext/frontend/Classes/Controller/ErrorController.php in line 68. Requested URL: https://example.com/

Is this caused by some incompatibility between v10 and the generated sitepackage / my changes to the requirements? I saw that recently support for v10 was added to the buildpackage tool (#31) does it do additional changes to what I did to adopt the generated package?

On a sub-page I was mostly concentrating my work on for the design / template the error does not occur however.

[gilbertsoft]

Your changes are fine. I would suggest to set the first two constraints to 9.5.0-10.4.99. And you also need to change other files. Best would be download a new sitepackage and compare the two versions.

The error seems not to be related to the sitepackagebuilder, a stack trace would be helpful here. You can change the error output behavior in the admin tool.