CRITICAL: Package stopped working after 3.1.1 update — "Class telesign\enterprise\sdk\Config not found"

[tuktukvlad]

We experienced a critical production outage immediately after updating telesign/telesignenterprise from 3.1.0 to 3.1.1.
Error details:

{
  "exception": {
      "class": "Error",
      "message": "Class \"telesign\\enterprise\\sdk\\Config\" not found",
      "code": 0,
      "file": "/var/task/vendor/telesign/telesignenterprise/src/verify/VerifyClient.php:24"
   }
}

This error did not occur on 3.1.0, but immediately appeared after upgrading to 3.1.1.
The issue has caused a major disruption in our production environment.
We urge you to treat this with high priority and provide an urgent hotfix or workaround.

Maintaining backward compatibility between minor versions is critical for production reliability.

Please investigate this breaking change and advise how your clients can mitigate the impact until a fixed version is released.
We expect:

• A prompt response and fix
• Clarification on how such a breaking change was introduced in a patch release

Thank you for your immediate attention to this matter.

[LanaJ11]

Hey @tuktukvlad,

Thanks for reporting this — I'm a product manager at Telesign, and I wanted to jump in here.

Really sorry for the disruption this caused — totally understand how frustrating it is to hit a breaking issue after what should have been a safe patch update. The error came from the addition of a new Config class in 3.1.1, which is used by other parts of the SDK. While the class was properly added in the release, in some cases the autoloader may not correctly register it and the error occurred despite what should have been a non-breaking update. We’ll be reviewing our release process to avoid this in the future.

Quick workaround:

• Reinstall the library
• Use the latest deployed version
• Run the composer dump-autoload command to refresh the class autoloading

Thanks again for the clear report and for your patience. If you have any questions or need further assistance, please don’t hesitate to reach out.

[tuktukvlad]

Hey @LanaJ11,

Thanks for the prompt response and clarification.

We’ll try the suggested workaround with composer dump-autoload and monitor the results.
Appreciate your attention to the issue and efforts to improve the release process.

[theeldarka]

@LanaJ11 Hi, please take a look -> #9