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

Pre 1.2.5-beta Xamarin.Forms problem with dependencies on Xamarin.Android.Support.v4 >= 25.1.1 #119

Open
lecnierfreeman opened this issue Apr 14, 2017 · 4 comments

Comments

@lecnierfreeman
Copy link

Currently Xamarin.Forms projects only support version 23.3.0 for Android libraries:

  • Xamarin.Android.Support.v4
  • Xamarin.Android.Support.Design
    ...
  • Xamarin.GooglePlayServices.Base.25.0.0
  • Xamarin.GooglePlayServices.Gcm.25.0.0

New -pre version 1.2.5 beta has dependencies on higher versions not compatibles with Xamarin.Forms projects, making impossible to try this version and check if it fix the null bundle error.

@benevbright
Copy link

same here.

There is no Xamarin.GooglePlayServices.measurement 42.1001 but when I try to update GCM 42.1001, it requires Xamarin.GooglePlayServices.measurement 42.1001.

So, I can't update this nuget to 1.2.5-beta

@pboisso
Copy link

pboisso commented Jul 28, 2017

Having the same issue here. Any plan to support latest version of GooglePlayServices by this plugin?

@rdelrosario
Copy link
Owner

I will actually be releasing a new refactored version of this plugin based on my work with: https://github.com/CrossGeeks/FirebasePushNotificationPlugin

That one is firebase dependant on iOS and Android. But planning to make a new version of it that on iOS doesn't depend of firebase. You can try using that one meanwhile.

@pboisso
Copy link

pboisso commented Jul 29, 2017

Well, our backend still uses and send GCM messages payload (through SNS), so this plugin was much more appropriate for our need. Is this a big task to fix this plugin to support 42.x? Or what would be the lowest version that could use? Nuget package says 25+, but the breaking changes in 42 does not let it link properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants