Bug report: Cannot add SpeziLLM as a dependency

[vishnuravi]

Description

Adding SpeziLLM as a dependency fails following the bump of SpeziAccount to 2.x-beta in the template application. This issue does not occur with previous versions of the template application that use SpeziAccount 1.x. Downgrading SpeziAccount causes build errors due to breaking changes in the template.

See error message below which occurs upon trying to add SpeziLLM to the Template Application via Package Dependencies:

Failed to resolve dependencies. Dependencies could not be resolved because root depends on 'speziaccount' 2.0.0-beta.7..<3.0.0.

Reproduction

Attempt to add SpeziLLM as a dependency to the latest release of SpeziTemplateApplication.

Expected behavior

SpeziLLM should be added as a dependency without any errors.

Additional context

Issue discussed with @pauljohanneskraft

Code of Conduct

• I agree to follow this project's Code of Conduct and Contributing Guidelines

[vishnuravi]

Note: This issue also occurs with SpeziChat.

[PSchmiedmayer]

Thank you @vishnuravi for reporting this! This is unfortunate and should not be the case.

As noted in StanfordSpezi/SpeziLLM#70 and in StanfordSpezi/SpeziChat#17 this might be a simple dependency mismatch with Spezi Foundation 2.0. After we merged this PRs adding these repos to the template app should be easy to do.

@Supereg We should start to tag a full release for Spezi Foundation in the near future & then start to tag full releases to Account? I am wondering if we have any elements that still need additional work that we should wait for; maybe also in correlation with @pauljohanneskraft's work on Android.

@Supereg @pauljohanneskraft feel free to chime in here.
For anyone else encountering these errors:

1. Please ensure that you utilize the latest prerelease version of Spezi Account (e.g. 2.0.0-beta.8); Spezi Firebase (2.0.0-beta.4) and others; all of them should be quite stable and we can tag releases there in the next weeks.
2. Please ensure that you updated all package dependencies using the Xcode Package update menu; Xcode and SPM are not really great at reporting errors and recently caused a few hiccups along they way, a bit unfortunate as well.
3. If you use Spezi Chat or Spezi LLM you can temporarily reference the feature/foundation branches noted in the PRs above to easily resolve errors.

Sorry about this; this is a temporary workaround for an underlying issue we should have resolved earlier; with Spezi LLM getting more attention from @paulhdk and @LeonNissen in the near future 🚀

[PSchmiedmayer]

The relevant PRs have been merged and tagged for Spezi Chat & Spezi LLM; this will resolve the issue in this repository.

If someone is running into any current issues they should update to the following packages:

• Please ensure that you utilize the latest prerelease version of Spezi Account (e.g. 2.0.0-beta.8); Spezi Firebase (2.0.0-beta.4) and others; all of them should be quite stable and we can tag releases there in the next weeks.
• Please ensure that you updated all package dependencies using the Xcode Package update menu; Xcode and SPM are not really great at reporting errors and recently caused a few hiccups along they way, a bit unfortunate as well.

The key element is that we should eventually tag stable version for most of the dependencies; and we can keep this issue open until then.