Closed ndastur closed 5 years ago
Hello, Thanks for bringing this up. We will fix this in the next update.
Best
@rgomezp can you consider fixing this problem soon? We are about to release new app but now stuck with this notification issue on android.
@mengvisal , I'm sorry this is blocking your release. I will go ahead and elevate to HIGH* priority
Hey guys - any update on this?
This is also affecting one my releases (actually we ended up taking out OneSignal, but i'd love to add it back in again). Even a beta nuget package would be greatly appreciated!
Hello, Sorry for the delay. We are working hard to get this done as soon as possible! Thank you for your patience.
This is also a blocker for us. @rgomezp do you have an ETA for this release?
@omrivm , Late next week
If you're a paying customer, please contact us through our official support channel at OneSignal.com
Any news regarding this issue?
@omrivm , Apologies for the delay. We are trying to release all of our SDKs as soon as possible. We really appreciate everyone's patience here. We're working extra hard to push all of the updates.
The dependency for the OneSignal SDK has been changed to Firebase Messaging (FCM) in the nuspec in 3.4.0. https://github.com/OneSignal/OneSignal-Xamarin-SDK/releases/tag/3.4.0
If GCM is still in your project after the upgrade you can remove it from your packages in your project.
Description: GCM is now depreciated in favour of FCM. The Xamarin.GooglePlayServices.Gcm package causes NuGET conflicts and it would appear is an unnecessary dependancy.
(your description here)
Environment Building a shared Xamarin Forms project Install via NuGET
Steps to Reproduce Issue: Create a blank XF project Add package such as Kinvey for mobile backend. Add OneSignal 3.1.0 package
NuGET error