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

[Refactoring] Replace Xamarin.Firebase.iOS.CloudMessaging #19

Open
thomasgalliker opened this issue May 11, 2024 · 9 comments · May be fixed by #74
Open

[Refactoring] Replace Xamarin.Firebase.iOS.CloudMessaging #19

thomasgalliker opened this issue May 11, 2024 · 9 comments · May be fixed by #74
Assignees
Labels
platform/ios refactoring s/needs-info Issue needs more info from the author

Comments

@thomasgalliker
Copy link
Owner

thomasgalliker commented May 11, 2024

Summary

It looks like the referenced nuget Xamarin.Firebase.iOS.CloudMessaging is no longer maintained and must be replaced by an updated Firebase iOS binding library.

Proposed change

Replace the nuget with one of the following substitutes:

References

@gabsamples6
Copy link

Alternative
https://github.com/Redth/DotNet.Platform.SlimBindings that is what MS reccomends which might fit in with Notification has there isnt much binding

@mrhery

This comment was marked as off-topic.

@thomasgalliker

This comment was marked as off-topic.

@gaurav-bagga
Copy link

@thomasgalliker When can we expect this issue to be complete, as mentioned in referenced ticket from CrossGeek's original project, old iOS bindings are not maintained and will get redundant in June 2024 and as we are close to the end date any pointers to when can we expect this would really help.

@thomasgalliker
Copy link
Owner Author

Did Google mention that you no longer receive push notifications when we dont update these bindings? They just say we have to update this at one point but the change in June 2024 SHOULD only affect the send API in the backend.

@gaurav-bagga
Copy link

@thomasgalliker I not a seasoned Xamarin developer, I have an old Xamarin app which I am trying to upgrade to MAUI.Net. I was using https://github.com/CrossGeeks/FirebasePushNotificationPlugin project. I was searching for a new library and stumbled upon some links which pointed to project https://github.com/AdamEssenmacher/GoogleApisForiOSComponents similar to this ticket.

When you visit the above project it says in overview old

App Store compliance requires native SDK versions 10.24+, while the Xamarin packages are stuck on 8.10.

Now I am confused if I use a project using Xamarin.Firebase.iOS.* will it impact me when I submit the application to App Store.

What you replied above to my query earlier sorry I could not follow, what I earlier meant was every other library you search for Firebase they are trying to use https://github.com/AdamEssenmacher/GoogleApisForiOSComponents.

As far as any notice from Google I did not get any when using old Xamarin app, I just wanted to upgrade before App Store and Play Store stop accepting it because of using obsolete libraries and SDK.

@thomasgalliker
Copy link
Owner Author

Yes, @gaurav-bagga we also have to go this way and replace the iOS bindings. As far as I understand google‘s info mail, you will kerp receiving push notifications even after June 2024. Correct me if I‘m wrong.
So, the only thing missing here is some free time to do this change.

@AlleSchonWeg
Copy link

In my opinion the biggest benefit is that with the new bindings you can receive notifications in the iOS simulator. Makes debugging easier.

@thomasgalliker
Copy link
Owner Author

@AlleSchonWeg @gaurav-bagga @gabsamples6 @mrhery
Do you like to test the latest version 3.0.x? It contains the firebase ios sdk 10.27.

@thomasgalliker thomasgalliker added the s/needs-info Issue needs more info from the author label Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform/ios refactoring s/needs-info Issue needs more info from the author
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants