Lawrence Forooghian

Results 95 issues of Lawrence Forooghian

## Issue description `ARTRealtime` will sometimes perform one more connection retry than it should — that is, it will perform a connection retry after `connectionStateTtl` has been exceeded, violating [RTN14e](https://sdk.ably.com/builds/ably/specification/main/features/#RTN14e)....

bug

┆Issue is synchronized with this [Jira Task](https://ably.atlassian.net/browse/ECO-4366) by [Unito](https://www.unito.io)

This issue aims to understand what we can do to avoid performing costly logging-related work that ultimately will not be of any use. For example, serializing a large object but...

## Background As described in #1618, there are some logging solutions that SDK users might commonly be using (e.g. `Logger`, `OSLog`). Part of the aim of #1618 and #1628 is...

[SDK-3478](https://ably.atlassian.net/browse/SDK-3478) investigated OS version usage of the ably-cocoa SDK, and concluded that we can, in the next major release, increase our deployment targets to the following: * iOS 13 *...

#1620 introduces the `Version2Log` protocol, which will replace `ARTLog` in the next major version of the SDK. However, we should think about whether we wish to introduce it earlier as...

## Background The issues #1618 and #1625 will define the requirements for an (SDK user-provided) object that receives log output from the SDK and is responsible for writing it to...

## Background The issues in the [Logging milestone](https://github.com/ably/ably-cocoa/milestone/6) seek to give users more control over how to output the log messages emitted by the SDK. However, there will also be...

## Background #1623 describes the situations in which Ably SDK developers might wish to read the log messages emitted by the SDK. For a developer to be able to read...

## Background Here, “SDK users” means users of the SDK who aren’t Ably SDK developers. As described in #1623, Ably SDK developers are the primary consumers of the log messages...