-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
Can I use this library together with Xamarin.Firebase.Messaging? #58
Comments
No. AdamE.iOS.Firebase.Core is incompatible with Xamarin.iOS.Firebase.Core, and also with any other package that includes common Firebase/Google iOS dependencies such as GTMSessionFetcher. This is documented in the project readme. |
it's run great when i deploy the project to android device, but the problem is when i deploy the project to ios device i already removed old xamarin firebase messaging packages im sorry, is this the right place to ask about this? thank you |
@AdamEssenmacher |
@suariana I think I misunderstood your first question, so let me try again. The nugets published from this repository are binding libraries for native iOS SDKs--they have nothing to do with Android. They only make sense in the context of iOS. They shouldn't be included in any builds that target any other platform. If you're referencing these packages directly in a multi-target project (e.g. MAUI), then the packages should be conditionally included (see the readme). Based on your screenshot, the build is hanging while XamarinBuildDownload is trying to extract GAppM. Check the project readme for troubleshooting steps around Windows and 7Zip. |
@maonaoda Mixing Xamarin.Google.iOS.SignIn with any AdamE.Firebase.iOS.* NuGet package is not recommended. This is because Xamarin.Google.iOS.SignIn depends on Xamarin.Firebase.iOS.Core, while AdamE.Firebase.iOS.Core is a replacement for Xamarin.Firebase.iOS.Core. Using both in the same project will cause both to link to the same set of native libraries (e.g., GTMSessionFetcher and PromisesObjC) but with different versions. This could lead to build-time issues or, worse, runtime conflicts. For more details about these incompatibilities, please refer to the project README. If you're interested in adding Google Sign-In support to this project, I'd gladly review a community PR. Google Sign-In would likely follow a similar implementation to Google Maps, which was recently added. Reviewing the commit history for that feature could serve as a helpful guide. Alternatively, if you'd like to see this feature prioritized, I offer one-time sponsorship options on my GitHub profile that could cover an afternoon of my time. |
|
Thank you for your detailed explanation, |
Thank you, my project can be built now i cannot receive any notification on debug or release build |
It's important to recognize that the AdamE version of FCM advances the underlying native SDK version two major versions (from 8.10 to 10.16+). Native configuration requirements changed. I'm guessing your problem stems from config changes related to method swizzling. Yes, these bindings work on .net 6 through 9. |
using Firebase.CloudMessaging; namespace FirebaseNotification.Platforms.iOS
} using Foundation; namespace FirebaseNotification.Platforms.iOS
} im sorry may i know that im using method swizzling or not? |
Closing this now because the original issue has been solved and the conversation is starting to sprawl. @suariana the FCM bindings work. If you're not getting notifications, it is almost certainly because your project is just misconfigured somehow. There are a few issues discussing the same sort of problem over at Plugin.Firebase that might push you in the right direction: TobiasBuchholz/Plugin.Firebase#324 |
I have problem when building my project when i use Adame.Firebas.IOS.CloudMessaging
i've followed step of longpath issues but i still cannot build my project
i use Xamarin.Firebase.Messaging for android and Adame.Firebas.IOS.CloudMessaging for iOS
can both of library work together in the same project?
thank you
The text was updated successfully, but these errors were encountered: