Skip to content

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

Closed

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

Activity

  1. nan-li commented on Sep 29, 2025

    @nan-li
    Contributor

    Hi @piercifani thanks for your feedback. Does using https://github.com/OneSignal/OneSignal-XCFramework instead help with performance and size for you?

  2. piercifani commented on Sep 30, 2025

    @piercifani
    Author

    Thanks a lot @nan-li ! that works a lot better. I did not see that referenced in any documentation, great find!

  3. nan-li commented on Oct 10, 2025

    @nan-li
    Contributor

    Good to hear @piercifani we'll update our SPM documentation to recommend that package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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