For example, we didn't catch #436, seemingly because of the way the example app references the SDK (via a workspace member instead of as an SPM dependency). Make sure that the example app build is as realistic as can be. I tried doing this when working on #440 (by making the example app get the SDK as a local SPM dependency and removing the package from the workspace), but this then breaks our Xcode CI builds because the AblyChat scheme is no longer available. And if, on the other hand, we were to remove the workspace, then we'd lose the ability to use test plans (e.g. for just running unit tests). (I also tried keeping the workspace and making the example app get its SDK from a local SPM dependency, but then this no longer reproduced #436.)
┆Issue is synchronized with this Jira Task by Unito
For example, we didn't catch #436, seemingly because of the way the example app references the SDK (via a workspace member instead of as an SPM dependency). Make sure that the example app build is as realistic as can be. I tried doing this when working on #440 (by making the example app get the SDK as a local SPM dependency and removing the package from the workspace), but this then breaks our Xcode CI builds because the AblyChat scheme is no longer available. And if, on the other hand, we were to remove the workspace, then we'd lose the ability to use test plans (e.g. for just running unit tests). (I also tried keeping the workspace and making the example app get its SDK from a local SPM dependency, but then this no longer reproduced #436.)
┆Issue is synchronized with this Jira Task by Unito