You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2024. It is now read-only.
I have configured FCM in my xamarin forms project. Working fine on debug mode. But when i try to archive in release mode it gives me native linking error.
Native linking failed, undefined symbol: _kFIRLoggerMessaging. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. Error: linker command failed with exit code 1 (use -v to see invocation) Native linking failed. Please review the build log and the user flags provided to gcc: -ObjC -lc++ -lsqlite3 -lz -ObjC -lc++ -lsqlite3 -lz (MT5201)
Installed Packages in my App for FCM
Xamarin.Firebase.iOS.CloudMessaging(3.1.2)
Xamarin.Firebase.iOS.Core(6.6.6)
Xamarin.Firebase.iOS.Analytics(6.4.1)
Xamarin.Firebase.iOS.InstanceID(4.3.3)
Xamarin.Firebase.iOS.Installation(1.1.1)
Xamarin.Build.Download(0.10.0)
The text was updated successfully, but these errors were encountered:
I have configured FCM in my xamarin forms project. Working fine on debug mode. But when i try to archive in release mode it gives me native linking error.
Native linking failed, undefined symbol: _kFIRLoggerMessaging. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in.
Error: linker command failed with exit code 1 (use -v to see invocation)
Native linking failed. Please review the build log and the user flags provided to gcc: -ObjC -lc++ -lsqlite3 -lz -ObjC -lc++ -lsqlite3 -lz (MT5201)
Installed Packages in my App for FCM
Xamarin.Firebase.iOS.CloudMessaging(3.1.2)
Xamarin.Firebase.iOS.Core(6.6.6)
Xamarin.Firebase.iOS.Analytics(6.4.1)
Xamarin.Firebase.iOS.InstanceID(4.3.3)
Xamarin.Firebase.iOS.Installation(1.1.1)
Xamarin.Build.Download(0.10.0)
The text was updated successfully, but these errors were encountered: