Hello team,
I need to make a definitive architectural and risk assessment for a production environment, and I would appreciate your official insight as project maintainers.
After analyzing the source code of the current stable version (2.3.7), we couldn't find any explicit references to the Coexistence (CoEx) flow or Embedded Signup for the official Cloud API. We noticed that references to branch 2.4 are currently marked as Release Candidates (rc1 / rc2).
Our technical questions for this decision are:
- If we connect an active WhatsApp Business number currently running on a physical phone using the official Cloud API channel in the stable version 2.3.7, will the phone app disconnect immediately (Meta's default behavior without CoEx)?
- Is official support for keeping both the physical phone and the Cloud API connected simultaneously (CoEx) strictly tied to the final stable release of version 2.4.0?
Thank you in advance for clarifying this so we can align our handoff documentation with full technical safety.
Hello team,
I need to make a definitive architectural and risk assessment for a production environment, and I would appreciate your official insight as project maintainers.
After analyzing the source code of the current stable version (2.3.7), we couldn't find any explicit references to the Coexistence (CoEx) flow or Embedded Signup for the official Cloud API. We noticed that references to branch 2.4 are currently marked as Release Candidates (rc1 / rc2).
Our technical questions for this decision are:
Thank you in advance for clarifying this so we can align our handoff documentation with full technical safety.