Welcome!
What did you do?
I am running an instance of Evolution API v2.3.1. In my deployment environment (Coolify), the CONFIG_SESSION_PHONE_VERSION variable is still present and set to a value like 2.3000.1020885143. Previously, this variable was used to specify the WhatsApp client version that the API should emulate.
What did you expect?
Based on recent discussions and information, I expected that this variable would no longer be necessary or would be ignored by the API, as the Evolution API is supposed to automatically manage the WhatsApp client version, typically by emulating the version of the WhatsApp application on the paired mobile device.
What did you observe instead of what you expected?
Despite the understanding that CONFIG_SESSION_PHONE_VERSION is deprecated, it still appears as an active configuration option in my deployment environment. This raises questions about its current role and whether its presence might cause any unintended behavior or conflicts with the API's automatic version management.
Screenshots/Videos
No response
Which version of the API are you using?
Evolution API v2.3.1
What is your environment?
Linux
Other environment specifications
No response
If applicable, paste the log output
No response
Additional Notes
My primary concern is to ensure optimal message synchronization and delivery, as I've experienced issues where messages appear on WhatsApp Web (desktop app) but not on the mobile app or browser-based WhatsApp Web. While this specific issue might be related to other factors (as discussed in previous analyses), I want to confirm that my environment variables are correctly configured and not causing any interference.
Could you please provide definitive guidance on the following:
-
Is CONFIG_SESSION_PHONE_VERSION still used or required in Evolution API v2.3.1 and later versions?
-
If it is no longer used, is it safe (and recommended) to remove this variable entirely from the environment configuration?
-
Are there any known scenarios where keeping this variable, even if deprecated, could lead to unexpected behavior or conflicts?
Welcome!
What did you do?
I am running an instance of Evolution API v2.3.1. In my deployment environment (Coolify), the CONFIG_SESSION_PHONE_VERSION variable is still present and set to a value like 2.3000.1020885143. Previously, this variable was used to specify the WhatsApp client version that the API should emulate.
What did you expect?
Based on recent discussions and information, I expected that this variable would no longer be necessary or would be ignored by the API, as the Evolution API is supposed to automatically manage the WhatsApp client version, typically by emulating the version of the WhatsApp application on the paired mobile device.
What did you observe instead of what you expected?
Despite the understanding that CONFIG_SESSION_PHONE_VERSION is deprecated, it still appears as an active configuration option in my deployment environment. This raises questions about its current role and whether its presence might cause any unintended behavior or conflicts with the API's automatic version management.
Screenshots/Videos
No response
Which version of the API are you using?
Evolution API v2.3.1
What is your environment?
Linux
Other environment specifications
No response
If applicable, paste the log output
No response
Additional Notes
My primary concern is to ensure optimal message synchronization and delivery, as I've experienced issues where messages appear on WhatsApp Web (desktop app) but not on the mobile app or browser-based WhatsApp Web. While this specific issue might be related to other factors (as discussed in previous analyses), I want to confirm that my environment variables are correctly configured and not causing any interference.
Could you please provide definitive guidance on the following:
Is CONFIG_SESSION_PHONE_VERSION still used or required in Evolution API v2.3.1 and later versions?
If it is no longer used, is it safe (and recommended) to remove this variable entirely from the environment configuration?
Are there any known scenarios where keeping this variable, even if deprecated, could lead to unexpected behavior or conflicts?