Skip to content

[Feedback]: Abysmal performance of SPM since adding OneSignal #1590

@piercifani

Description

@piercifani

What's on your mind?

Yes, I know that this is really an SPM bug rather than a OneSignal bug, but adding this dependency to a Package.swift significantly impacts the time that Xcode takes to resolve the dependency graph because it has to clone the whole git repo which is 1.64 GiB.

The XCFramework actually vended by OneSignal is reasonably sized at 5MB, which tells me that a simple solution is possible: clean the git repo's history or use another repo to make the DX pleasant.

Code of Conduct

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions