Skip to content

Actions: aws-amplify/aws-sdk-ios

Actions

Issue Comment

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
issue_comment.yml
120 workflow runs
120 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
draft: iot crash Issue Comment #396: Issue comment #5550 (comment) created by ZealBK
9s
9s
AWSIoTMQTTClient iOS Crash during reconnect/stream close in AWSMQTTSession Issue Comment #395: Issue comment #5568 (comment) created by thisisabhash
6m 36s
6m 36s
Getting crash Issue Comment #394: Issue comment #5567 (comment) created by cadivus
24s
24s
AWSMobileClient social login: userState becomes signedOut only after task kill and relaunch Issue Comment #393: Issue comment #5563 (comment) created by masashi972
6s
6s
AWSMobileClient social login: userState becomes signedOut only after task kill and relaunch Issue Comment #392: Issue comment #5563 (comment) created by masashi972
12s
12s
AWSMobileClient social login: userState becomes signedOut only after task kill and relaunch Issue Comment #391: Issue comment #5563 (comment) created by thisisabhash
10s
10s
Inquiry regarding the “Invalid user attributes: email” error when signing in with Google social login on a different device Issue Comment #390: Issue comment #5536 (comment) created by masashi972
7s
7s
Crash in PushNotificationsCategory.registerDevice(apnsToken:) – EXC_BREAKPOINT / preconditionFailure Issue Comment #389: Issue comment #5562 (comment) created by jvh-aws
9s
9s
The issues related to issues/5556, issues/5557, issues 5558, and issues/5559 have been closed.But I still have a question. Issue Comment #388: Issue comment #5560 (comment) created by G279zhu
8s
8s
MQTT connection disconnects when iOS app goes to background and fluctuates between connected/disconnected when app in foreground Issue Comment #387: Issue comment #5561 (comment) created by tyllark
7s
7s
The issues related to issues/5556, issues/5557, issues 5558, and issues/5559 have been closed.But I still have a question. Issue Comment #386: Issue comment #5560 (comment) created by harsh62
7s
7s
The issues related to issues/5556, issues/5557, issues 5558, and issues/5559 have been closed.But I still have a question. Issue Comment #385: Issue comment #5560 (comment) created by G279zhu
9s
9s
The issues related to issues/5556, issues/5557, issues 5558, and issues/5559 have been closed.But I still have a question. Issue Comment #384: Issue comment #5560 (comment) created by harsh62
6s
6s
The issues related to issues/5556, issues/5557, issues 5558, and issues/5559 have been closed.But I still have a question. Issue Comment #383: Issue comment #5560 (comment) created by G279zhu
8s
8s
The issues related to issues/5556, issues/5557, issues 5558, and issues/5559 have been closed.But I still have a question. Issue Comment #382: Issue comment #5560 (comment) created by harsh62
8s
8s
During the closure process of the underlying CFStream (or when the CF is internally unscheduled), there is a problem where the same stream is repeatedly closed/unscheduled by different threads/objects, and the internal state of the CF is disrupted. Issue Comment #381: Issue comment #5559 (comment) created by G279zhu
6s
6s
In the webSocket: didCloseWithCode: reason: wasClean: method of AWSIoTMQTTClient. m, there is a competition between AWSIoTStreamThread and the encoderOutputStream/webSocket closure during stream cleaning. Issue Comment #380: Issue comment #5558 (comment) created by G279zhu
6s
6s
Simultaneous operation of the same NSOutStream in multiple threads/locations leads to a crash in _CFStreamUnsucheduleFromRunLoop. Issue Comment #379: Issue comment #5557 (comment) created by G279zhu
7s
7s
The AWS IoT MQTT client encountered a race condition while clearing WebSocket connections, causing access to released objects and crashing. Issue Comment #378: Issue comment #5556 (comment) created by G279zhu
9s
9s
During the closure process of the underlying CFStream (or when the CF is internally unscheduled), there is a problem where the same stream is repeatedly closed/unscheduled by different threads/objects, and the internal state of the CF is disrupted. Issue Comment #377: Issue comment #5559 (comment) created by harsh62
1s
1s
In the webSocket: didCloseWithCode: reason: wasClean: method of AWSIoTMQTTClient. m, there is a competition between AWSIoTStreamThread and the encoderOutputStream/webSocket closure during stream cleaning. Issue Comment #376: Issue comment #5558 (comment) created by harsh62
1s
1s
Simultaneous operation of the same NSOutStream in multiple threads/locations leads to a crash in _CFStreamUnsucheduleFromRunLoop. Issue Comment #375: Issue comment #5557 (comment) created by harsh62
1s
1s
The AWS IoT MQTT client encountered a race condition while clearing WebSocket connections, causing access to released objects and crashing. Issue Comment #374: Issue comment #5556 (comment) created by harsh62
9s
9s
#1 0x000000010428eebc in -[AWSIoTMQTTClient webSocketDidOpen:] at AWSIoTMQTTClient.m:1235 Issue Comment #373: Issue comment #5555 (comment) created by harsh62
10s
10s
AWSTranscribeStreamingItem should contains 'confidence' attribute according docs Issue Comment #372: Issue comment #5553 (comment) created by tylerjroach
10s
10s