Brand new Electron stuck on rapid cyan (lib/mbedtls/library/ssl_tls.c:6983: bad application data message)

Troubleshooting
1

Is this a sim card issue if so how can I get a sim replacement?

cC\x82\xfa\x9dH\x12\xac!!\x9dc\xf9x\xc0\x10[\xe2\""
   190.820 AT read OK    6 "\r\nOK\r\n"
0000190820 [system] TRACE: received 53
0000190821 [comm.protocol.handshake] INFO: Sending HELLO message
0000190821 [comm.protocol.handshake] INFO: Sending HELLO messa0000190822 [comm.coap] TRACE: sending message id=2
0000190822 [system] TRACE: send 58
socketSendTo(0,54.157.13.160,5684,,58)
   190.823 AT send      36 "AT+USOST=0,\"54.157.13.160\",5684,58\r\n"
   190.833 AT read  >    3 "\r\n@"
   190.883 AT send      58 "\x17\xfe\xfd\x00\x01\x00\x00\x00\x00\x00\x02\x00-\x00\x01\x00\x00\x00\x00\x00\x02\xf2\xe9\b\x14\xf5\x17bJ\x8fxLOR\x0e\xc8\xffV\x93\xfaA \xd7}F\x9c$\x16\xbf+\a\xae\x96\x1d\f-\xcd\x93"
   191.025 AT read  +   16 "\r\n+USOST: 0,58\r\n"
   191.035 AT read OK    6 "\r\nOK\r\n"
   191.035 AT read  +   17 "\r\n+UUSORD: 0,67\r\n"
Socket 0: handle 0 has 67 bytes pending
   191.046 AT send      16 "AT+USORF=0,813\r\n"
   191.056 AT read  +   52 "\r\n+USORF: 0,\"54.157.13.160\",5684,14,\"\x14\xfe\xfd\x00\x00\x00\x00\x00\x00\x00\n\x00\x01\x01\""
   191.067 AT read OK    6 "\r\nOK\r\n"
0000191067 [system] TRACE: received 14
lib/mbedtls/library/ssl_tls.c:3655: dropping unexpected ChangeCipherSpec
lib/mbedtls/library/ssl_tls.c:3955: discarding invalid   191.068 AT read  +   17 "\r\n+UUSORF: 0,53\r\n"
Socket 0: handle 0 has 53 bytes pending
   191.079 AT send      16 "AT+USORF=0,813\r\n"
   191.099 AT read  +   91 "\r\n+USORF: 0,\"54.157.13.160\",5684,53,\"\x16\xfe\xfd\x00\x01\x00\x00\x00\x00\x00\x01\x00(\x00\x01\x00\x00\x00\x00\x00\x01$\x16\xa0\xeb\xc79\xd3\r\x1ac\x99\x9a\x1a\x15\">\xde5\xc8a\x1c\xfe\rB(A\xa9\xf5\xb7\xcf\xd1\x92\""
   191.111 AT read OK    6 "\r\nOK\r\n"
0000191111 [system] TRACE: received 53
lib/mbedtls/library/ssl_tls.c:6983: bad application data message
0000196232 [system] TRACE: send 58
socketSendTo(0,54.157.13.160,5684,,58)
2

This is caused by a configuration problem on the Particle cloud side for your Electron.

(That’s not evident from this log, There was a device ID in a support ticket for this issue that allowed me to determine that.)