joergb Member Licensed User Longtime User Jan 15, 2020 #1 Hello, under ios 13.3 the client doesn't fire the astream.new_text event, even though the server sends the message. we looked in the source and changed the following statement in the astreams_NewDate Prcedure: B4X: Copy old: If Buffer.Length <= 0 Or Buffer.Length > 255 Then return new: If Buffer.Length <= 0 Then return because we received a Message with a Length of 265 Byte and in the old version, these message was ignored. now it works and it seems that the removal of the limit of 256 doesn't matter. Am I right or will this crash soon ?
Hello, under ios 13.3 the client doesn't fire the astream.new_text event, even though the server sends the message. we looked in the source and changed the following statement in the astreams_NewDate Prcedure: B4X: Copy old: If Buffer.Length <= 0 Or Buffer.Length > 255 Then return new: If Buffer.Length <= 0 Then return because we received a Message with a Length of 265 Byte and in the old version, these message was ignored. now it works and it seems that the removal of the limit of 256 doesn't matter. Am I right or will this crash soon ?
Erel B4X founder Staff member Licensed User Longtime User Jan 16, 2020 #2 I don't see this code in that class: https://www.b4x.com/android/forum/t...n-working-with-streams-of-text.27002/#content Upvote 0
I don't see this code in that class: https://www.b4x.com/android/forum/t...n-working-with-streams-of-text.27002/#content
joergb Member Licensed User Longtime User Jan 16, 2020 #3 Hi Erel thanks for your reply. it seems, I used a older version of asyncstramtext. Upvote 0
