Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the need for the huge .bundle files? #894

Closed
andypoly opened this issue Nov 7, 2023 · 5 comments
Closed

What is the need for the huge .bundle files? #894

andypoly opened this issue Nov 7, 2023 · 5 comments

Comments

@andypoly
Copy link

andypoly commented Nov 7, 2023

[REQUIRED] Please fill in the following fields:

  • Unity editor version: Any
  • Firebase Unity SDK version: latest 11.6.0
  • Source you installed the SDK: .unitypackage (.unitypackage or Unity Package Manager)
  • Problematic Firebase Component: All - .bundle (Auth, Database, etc.)
  • Other Firebase Components in use: Analytics (Auth, Database, etc.)
  • Additional SDKs you are using: na (Facebook, AdMob, etc.)
  • Platform you are using the Unity editor on: Win/Mac (Mac, Windows, or Linux)
  • Platform you are targeting: all except Linux (iOS, Android, and/or desktop)
  • Scripting Runtime: both (Mono, and/or IL2CPP)
  • Pre-built SDK from the website or open-source from this repo: prebuilt

[REQUIRED] Please describe the question here:

Please explain the need for the .bundle files which make this plugin unusable on some source-control systems without LFS/custom-changes because of the enormous size (FirebaseCppApp-11_6_0.bundle is over 100mb)
GitLab for instance has 100mb max commit size by default and on free tier.

You must remove the need for such big files for a code-only plugin.
What are the .bundle files needed for?

@paulinon paulinon removed the new New issue. label Nov 7, 2023
@chanon
Copy link

chanon commented Nov 9, 2023

I am running into the same issue.
Is this 160MB file really needed?

@a-maurice
Copy link
Collaborator

There are a couple reasons for this, none of which are great. The bundle file has support for both Mac architectures combined in the single file, which basically doubles the size. I believe Unity does let you specify which architecture the bundle should be for, so it is possible to split them, we need to update our packaging logic to handle that case, across all the Unity versions we support.

The other problem is some of our dependencies are just big. We've tried reducing them in size, and will continue to attempt so in the future.

For a workaround, you could edit the files yourself, using the lipo tool to split the architectures, and setting up your project with the one you want.

@Danejw
Copy link

Danejw commented Nov 17, 2023

Use Git LFS, open the folder with the .bundle file in it from a command line then enter git lfs track “*.bundle”

@andypoly
Copy link
Author

Use Git LFS, open the folder with the .bundle file in it from a command line then enter git lfs track “*.bundle”

Yes this is the solution - unless you have a free/cheap host with no or limited lfs supported...

@argzdev
Copy link

argzdev commented Jun 5, 2024

Hey folks, I believe this question has been answered with suggestions of possible alternative solutions. And since file size reductions are already in the works, I'll go ahead and close this thread.

@argzdev argzdev closed this as completed Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants