this is a problem between next15 and next-intl, please wait a few days for next-intl or next15 to have a new update