White page, on all nodes that use Address module

@drattar, can you create a new node with an address field?

Sounds like you have display_errors=off in your php.ini and need to consult your server logs to get the error.

@Abyss
No, i cant Create a new node with Address module field either.
@bojanz
thank you, i changed display_errors to display_errors=on; so i can track the error

Fatal error: Declaration of Drupal\address\Repository\CountryRepository::loadDefinitions($locale) must be compatible with CommerceGuys\Addressing\Country\CountryRepository::loadDefinitions(string $locale): array in /home/***/public/modules/contrib/address/src/Repository/CountryRepository.php on line 43

As mentioned here → and many another posts, Downgrading commerceguys/addressing don't work currently.

composer require commerceguys/addressing:1.3.0 drupal/address

- Downloading commerceguys/addressing (v1.3.0)
- Downgrading commerceguys/addressing (v1.4.2 => v1.3.0): Extracting archive

Sounds like you solved it.

actuality, i don't solve it yet and i mentioned that.
Even, this patch doesn't work and i still face same error.
https://www.drupal.org/files/issues/2022-11-09/3302484-28-for-8.x-1.9.patch →

Your module and your library need to be in sync.

So either you dowgrade the library (to remove the typehints there) or you use the patch (to add the typehints here).

The error is telling you which side has typehints and which doesn't (the ":string" part), allowing you to debug what's going wrong.

@drattar Could you provide more information?
Since I reviewed the downgrade method and it works correctly on a clean deployment.
composer require commerceguys/addressing:~1.3.0 drupal/address

Although previous attempts failed; The module is now working.
I intended to migrate to Drupal 9 and then update the modules to the latest version; And I updated the Mariadb database from version 5 to version 11 .. I did not make any other modification.
Oddly enough, this module is now working.

I updated the module to the latest version (1.12.0), with all its dependencies, and the problem was fixed.
The strangest thing is that I haven't seen anything in the Drupal logs when visiting the broken page.

Automatically closed - issue fixed for 2 weeks with no activity.