Firebase LibCppApp is now over 100Mb

[Alex Ferrier]

[I have attempted to post this message from the web view 3 times from 2 different accounts over the last 48 hours. Not sure why it never shows up.]

When pushing to github I now get:

remote: error: File Unity/Assets/Firebase/Plugins/x86_64/FirebaseCppApp-6_8_0.so is 102.08 MB; this exceeds GitHub's file size limit of 100.00 MB.

This is really annoying. Now we have to use git lfs to track a massive binary file. I know that seems minor, but it's a pretty major blow for the workflow of our projects.

Could we please either have this fixed, or have some proper documentation regarding which files of Firebase-Unity are expected to be stored in Git, and which are handled by GooglePlayServicesGradleMavenJarAarResolverWorkspaceVersionHandlerSomething? (So that we can check in what won't automagically be pulled down during a continuous build.) Using git-lfs to handle this is not a very clean solution, plus git-lfs isn't that friendly - a fact you only know after the first time you see an error message like "git smudge filter failed! File that should be a pointer isn't!!!" and embark on a frustrating trip through stackoverflow.

The quickstart-unity examples neatly sidestep this problem by not including the firebase packages at all, but it feels like it's time for some proper documentation of how a production project should be set up, which, if any, folders should be gitignored, etc.

Please?

Also, posting from my personal account. Anything from my work account never seems to get posted on Firebase-talk.

Finally, maybe I'm a grumpy old programmer, but 100Mb?! For a lib, with hundreds of files of external dependencies and (as far as I can see) no large binary assets, textures or 3D models in it? Seriously, the world's gone mad.