Skip to content

Actions: aws-amplify/aws-sdk-ios

Actions

All workflows

Actions

Loading...
Loading

Showing runs from all workflows
685 workflow runs
685 workflow runs

Filter by Event

Filter by Status

Filter by Branch

Filter by Actor

Scheduled CodeQL #37: by github-advanced-security bot
46s main
main
46s
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
MQTT connection disconnects when iOS app goes to background and fluctuates between connected/disconnected when app in foreground Issue Opened #70: Issue #5561 opened by DHURIU1
14s
14s
Scheduled CodeQL #36: by github-advanced-security bot
46s main
main
46s
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
The issues related to issues/5556, issues/5557, issues 5558, and issues/5559 have been closed.But I still have a question. Issue Opened #69: Issue #5560 opened by G279zhu
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
AWSTranscribeStreamingItem should contains 'confidence' attribute according docs Issue Closed #51: Issue #5553 closed by harsh62
16s
16s
The AWS IoT MQTT client encountered a race condition while clearing WebSocket connections, causing access to released objects and crashing. Issue Closed #50: Issue #5556 closed by harsh62
18s
18s
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
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 Closed #49: Issue #5559 closed by harsh62
20s
20s
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
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 Closed #48: Issue #5558 closed by harsh62
14s
14s
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
Simultaneous operation of the same NSOutStream in multiple threads/locations leads to a crash in _CFStreamUnsucheduleFromRunLoop. Issue Closed #47: Issue #5557 closed by harsh62
14s
14s
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 Closed #46: Issue #5555 closed by harsh62
22s
22s