1개 답변
- 최신
- 최다 투표
- 가장 많은 댓글
1
In researching further, this appears to be a differentiation between the MQTT 5 specification and how AWS IoT Core has implemented it. This GitHub issue appears to describe what you are seeing.
As noted by the requester, there is a workaround that may work for you too:
import { v4 as uuidv4 } from 'uuid'; // ... builder.withConnectProperties({ keepAliveIntervalSeconds: 120, clientId: uuidv4() }); // ...
Please let me know if this resolves your issue. In the meantime I'll ensure the AWS IoT Core team knows about this, either to adhere to the specification or document the difference for others.
답변함 2달 전
관련 콘텐츠
- AWS 공식업데이트됨 3년 전
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 일 년 전
- AWS 공식업데이트됨 일 년 전