NB_SMS struggles over the "/" sign in the date of the received sms

[CptHolzschnauz]

After a sms is received, the lib ask with
AT+CMGL="REC UNREAD"
+CMGL: 0,"REC UNREAD","+TelNr",,"21
and breaks here, the modem is freezed.

The complete output (from m-center software) is
+CMGL: 0,"REC UNREAD","+TelNr",,"21/07/21, 07:09:48+08"

So the lib strugles over the "/" sign

I think i made a wrong setting with the modem but i don't know what. Any ideas?
If so then it can be helpful to include the correct modem setup in the NB_SMS class.
THX
Update: Compiled with a MACOS

[CptHolzschnauz]

I just double checked with another MKR1500 board. The same behaviour:

14:03:54.801 -> AT+CMGL="REC UNREAD"
14:03:54.801 -> OK
14:03:55.887 -> AT+CMGL="REC UNREAD"
14:03:55.887 -> +CMGL: 0,"REC UNREAD","+417xxxxxxxxx",,"21

There must be other out there with the same problem?

UPDATE : Just compiled and uploaded with a MS Computer and it works?!?
I didn't changed a digit in NB_SMS...
All done with the official Receive SMS Sketch.
But it eats the first digit....from Test to est?

14:31:40.743 -> AT+CMGL="REC UNREAD"
14:31:40.743 -> +CMGL: 2,"REC UNREAD","+41xxxxxxxx",,"21/07/25,14:31:38+08"
14:31:40.743 -> Test
14:31:40.743 ->
14:31:40.743 -> OK
14:31:40.743 -> Message received from:
14:31:40.743 -> +417xxxxxxxxx
14:31:40.743 -> est
14:31:40.743 -> END OF MESSAGE
14:31:40.743 -> AT+CMGD=2

14:31:40.780 -> OK
14:31:40.780 -> MESSAGE DELETED

[CptHolzschnauz]

It's not an issue, i have a internal problem, with another lib it works

[joshbober]

I am having this same issue where the message gets cut off, but it isn't due to the '/' character, I believe it is some kind of buffer error.
Using the official RecieveSMS sketch and a clean library install, clean compile, I have this issue every time. You say "with another lib it works", does that mean it does not work with this MKRNB library? I am submitting this as an open issue with more information from my testing.

[CptHolzschnauz]

Don't trust too much the AT console.
Do you need the whole message or just peek()?
Do the board (modem) freeze when this happens?

[joshbober]

For debugging purposes, I need to see how to handle receiving SMS messages for my project. I figured the official sketch is a good starting point for that.

The modem does not freeze, it enters the while() loop that waits for MODEM.ready() to return a non-zero number, which never happens. Please check out my post #86 where I go over more of the details.

I just wanted to comment here to say that, while this issue was closed, the resolution was not clear. At this point I know that it isn't the '/' character that is the problem, so I wanted to share that where it's relevant.

You mentioned using another library, can I ask which one?