The error exists

?I had updated the wordpress to 6.7.1-RC1-59440 and theme Astra 4.8.6.
?However, there is still error here.

?Notice: 呼叫 _load_textdomain_just_in_time 函式的方式不正確。Translation
?loading for the astra domain was triggered too early. This is usually an
?indicator for some code in the plugin or theme running too early.
?Translations should be loaded at the init action or later. 請參閱〈
?WordPress 的偵錯功能〉以進一步了解相關資訊。 (這項訊息新增於 6.7.0 版) in
?/home/aiehked/public_html/wp-includes/functions.php on line 6114

?Warning: Cannot modify header information - headers already sent by
?(output started at /home/aiehked/public_html/wp-
?includes/functions.php:6114) in /home/aiehked/public_html/wp-
?admin/includes/misc.php on line 1438

?Warning: Cannot modify header information - headers already sent by
?(output started at /home/aiehked/public_html/wp-
?includes/functions.php:6114) in /home/aiehked/public_html/wp-
?includes/functions.php on line 7137

?Warning: Cannot modify header information - headers already sent by
?(output started at /home/aiehked/public_html/wp-
?includes/functions.php:6114) in /home/aiehked/public_html/wp-admin/admin-
?header.php on line 9

?Warning: Cannot modify header information - headers already sent by
?(output started at /home/aiehked/public_html/wp-
?includes/functions.php:6114) in /home/aiehked/public_html/wp-
?includes/option.php on line 1715

?Warning: Cannot modify header information - headers already sent by
?(output started at /home/aiehked/public_html/wp-
?includes/functions.php:6114) in /home/aiehked/public_html/wp-
?includes/option.php on line 1716

We have the same problem.

https://www.ads-software.com/support/topic/function-_load_textdomain_just_in_time-was-called-incorrectly-22/

Same issue with Astra Add-On.

Hi @caritatang and @amit2d,

Thank you for highlighting this issue. This issue has impacted not just Astra but almost every plugin and theme. While WordPress is still working on this issue, the 6.7.1 RC1 version is still a testing version for this. Additionally, since it is taking time, we have also started working on individual fixes. We’ve added this to our to-do list and are actively addressing it.

Furthermore, I would like to mention that this error appears only when WP Debug mode is enabled. As a temporary solution, we recommend disabling it on your live site.

For further discussion, please open a ticket via our Support Portal. We also respond faster there.

Kind regards,
Aradhy ??