-
Notifications
You must be signed in to change notification settings - Fork 53
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
Does this work with .NET MAUI Blazor-App? #96
Comments
Unfortunately I don't have any experience regarding to .NET MAUI Blazor apps, so I'm not sure whether this should work or not. Theoretically it could work since in combination with .NET MAUI is Blazor is just another UI framework solution for creating an android or iOS app as far as I understand it. Maybe referencing |
I am getting the same error, but with a normal .NET 7.0 MAUI app (not Blazor). Installing version 1.2.3 via NuGet fails with the following error:
I tried versions 1.2.2 and 1.2.1, but the error occurs with different iOS header files. This started happening after I updated Visual Studio 2022 and installed .NET 7.0. I was able to successfully install it on a .NET 6.0 MAUI app prior to the updates, but now neither .NET 6.0 or 7.0 work. |
The same issue when trying to upgrade from 1.2.2 to 1.2.3 .NET MAUI (whitout blazor) |
This is a nuget problem. Nuget has problems with long directory names. As a workaround create a environment valriable |
Thanks @AlleSchonWeg - the workaround works for version 1.2.2 and MAUI 7.0 (which is good enough for me). I tried it with version 1.2.3 though, and it still fails with the same error. |
Get this project working with blazor maui .NET 7, thanks so much |
xamarin/GoogleApisForiOSComponents#555 (comment) PowerShell:
see this: I was able to update successfully |
The path length is limited to 260 chars per default: NuGet/Home#11953 |
It's working now on my Windows 11 machine for Android. I successfully received a fcm-token, YAY! I had to install the package with the terminal tho. I put the builder.RegisterFirebaseServices() to the end of my service registrations:
When I try to run the app on a iOS Device, I get the following error:
I think the state of the app has a different behavior with Blazor Maui - mode. Any Ideas about iOS? |
The Issue Happens in iOS/Auth/ FirebaseAuthImplementation.cs -> 29 The binding for the GoogleService-INfo.plist seems to fail, Ideas? |
Did you put the <ItemGroup Condition="'$(TargetFramework)' == 'net6.0-ios'">
<BundleResource Include="GoogleService-Info.plist" />
</ItemGroup> If you are targetting .net7 you also need to change the ItemGroup Condition to |
I checked that but unfortunately it's not working. I also tried different combinations with putting it inside the iOS folder or changing the Configuration like this:
without luck :-( |
It is a an issue with Blazor MAUI.
|
Can you explain in some more detail about this? Still a struggle to get it working. For now it seems that Blazor only accepts the files in the wwwroot folder. By putting the google-services.json and the GoogleService-info.plist in there and referencing it through a MauiAsset like below.
The original error that started this was: |
Did they get it to work? |
@PhilippRoessner |
Two separate issues in here. One is a duplicate of the long filenames issue: #240 (comment) The other is how to use Firebase in a MAUI Blazor app. Yes, it should work. However, putting GoogleService-info.plist/GoogleServices.json in the wwwroot folder is the wrong approach. To use this plugin in a MAUI Blazor app, you should set it up and initialize it just like a non-Blazor MAUI app, register the firebase services, and then inject them into your Blazor components. |
Does this work with .NET MAUI Blazor-App?
Or is this only for the Xamarin .NET MAUI-App?
I used it in an MAUI BLazor-App and an Error happend as I installed the Nugetpacket via manager.
....
System.IO.DirectoryNotFoundException: Ein Teil des Pfades "C:\Users\Are.nuget\packages\xamarin.firebase.ios.installations\8.10.0.1\lib\net6.0-ios15.4\Firebase.Installations.resources\FirebaseInstallations.xcframework\ios-arm64_i386_x86_64-simulator\FirebaseInstallations.framework\Headers\FirebaseInstallations-umbrella.h" konnte nicht gefunden werden.
bei System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
bei System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
bei System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)
bei System.IO.File.Create(String path)
bei NuGet.Packaging.StreamExtensions.Testable.MmapCopy(Stream inputStream, String fileFullPath, Int64 size)
bei NuGet.Packaging.StreamExtensions.Testable.CopyToFile(Stream inputStream, String fileFullPath)
bei NuGet.Packaging.PackageFileExtractor.ExtractPackageFile(String source, String target, Stream stream)
bei NuGet.Packaging.PackageArchiveReader.CopyFiles(String destination, IEnumerable
1 packageFiles, ExtractPackageFileDelegate extractFile, ILogger logger, CancellationToken token) bei NuGet.Packaging.PackageReaderBase.CopyFilesAsync(String destination, IEnumerable
1 packageFiles, ExtractPackageFileDelegate extractFile, ILogger logger, CancellationToken cancellationToken)bei NuGet.Packaging.PackageExtractor.<>c__DisplayClass5_0.<b__0>d.MoveNext()
--- Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde ---
....
The text was updated successfully, but these errors were encountered: