Issue Description:
While utilizing your package as an SMS API provider in our project, we faced challenges related to SMS segmentation. Notably:
When sending an SMS containing 201 characters that should have logically split into three parts, it was instead being segmented into four parts.
Text corruption occurred in messages of certain lengths (e.g., 71 characters), where the message content was altered, displaying Chinese characters unexpectedly.
Solution and Testing:
We have developed a fix for these issues, which has been thoroughly tested over the past three months. Since implementing this modification, the SMS handling has been functioning correctly, with no observed issues in message segmentation or content integrity.
Issue Description: While utilizing your package as an SMS API provider in our project, we faced challenges related to SMS segmentation. Notably:
When sending an SMS containing 201 characters that should have logically split into three parts, it was instead being segmented into four parts.
Text corruption occurred in messages of certain lengths (e.g., 71 characters), where the message content was altered, displaying Chinese characters unexpectedly.
Solution and Testing: We have developed a fix for these issues, which has been thoroughly tested over the past three months. Since implementing this modification, the SMS handling has been functioning correctly, with no observed issues in message segmentation or content integrity.