Facebook-sdk-for-unity: Facebook SDK in Unity Package Manager

I agree! Now the .unitypackage is not so good for Unity2019.

Please, give visibility to this issue

It should first be made compatible with Unity 2019.4 that on Current Version still is not (Cannot finish an iOS build with it). And then added to Package Manager would be a must have!

@wagenheimer
Agree!, we are also facing that too, but if it was a package already, the only thing you should do when they fix is to only update the version instead of reimporting again the unitypackage that may lead to bugs/configuration errors

@wagenheimer Is there an issue with that info you shared?

@MartinGonzalez Yes, here is it.
https://github.com/facebook/facebook-sdk-for-unity/issues/450

Package manager, yes! It would be an amazing addition

It would be great to have facebook plugin in UPM.

I think it is essential to start deprecating .unitypackages in favor of UPM packages

I would love to have UPM support.

it would be great to have this in UPM, to reduce repo size and segregate dependencies from actual code.

+1

+1

+1

+1

It would be great to have some visibility from the team, if this is in the roadmap or something...

Surely would be good, there are alternatives but still would be better to have a official repo https://github.com/oae/unity-package-facebook-sdk

Adding support for this would be greatly appreciated. All the other major plugins have migrated to Unity Package Manager. Please consider prioritizing this!

+1

+1

+1

When this issue will be fixed

+1

Just for your information guys: not only Google moved their Firebase SDKs to Unity Package Manager (UPM), but also OneSignal is going to provide their SDK via UPM starting from April 26th. So more and more major 3rd-party developers move their SDKs to UPM. It would be great if someone from Facebook Unity SDK dev team reply here.

+1

Not to hijack the issue thread but for @VasylRomanets-MoonActive and others who may not know yet, Google is going backwards now for some reason. See thread: https://github.com/firebase/quickstart-unity/issues/1028 and https://github.com/firebase/quickstart-unity/issues/1030

This is obviously not the way forward and I agree Facebook and others should work on switching to UPM asap instead of the .unitypackage insanity.

Edit: Turns out Unity is the one at fault here, not sure if it will impact FB bringing the sdk to UPM but Unity has made things annoying to say the least, see thread: https://forum.unity.com/threads/updates-to-our-terms-of-service-and-new-package-guidelines.999940/

@HitCache yep indeed I've got calls with both Google and Unity now and there is nothing Google can do to avoid infringing upon the new Unity guidelines. However I hope Unity will revert back, I've let them know this is not the way to go and I am sure not the only one that voiced his opinion on this issue. And indeed these new guidelines would basically block Facebook SDK as well.

PS: For now we are basically taking Google tarballs and publishing them to our own UPM registry which we then link in Unity package manager as this doesn't break the new guidelines. 🤦

At least publish it as tarball. Would be much simpler to intergrate it in our projects

Or release a git repo please like proposed as a workaround for Google here: https://github.com/firebase/quickstart-unity/issues/1052