-
Notifications
You must be signed in to change notification settings - Fork 5
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
'iOS" is a namespace but is used like a type error when adding the NewRelic nuget #45
Labels
bug
Something isn't working
Comments
@robin-schroeder-merc i will look into it. |
@robin-schroeder-merc we created internal ticket for this, it will fix in next maui agent release. |
ndesai-newrelic
added a commit
that referenced
this issue
Sep 23, 2024
@robin-schroeder-merc the issue is fixed in 1.1.2 release. |
ndesai-newrelic
added a commit
that referenced
this issue
Sep 23, 2024
ndesai-newrelic
added a commit
that referenced
this issue
Sep 23, 2024
Thank you! It works! |
ndesai-newrelic
added a commit
that referenced
this issue
Sep 27, 2024
* fix:iOS namespace issue #45 * fix: added missing info.plist file in iOS bindings
ndesai-newrelic
added a commit
that referenced
this issue
Oct 22, 2024
* fix:iOS namespace issue #45 * fix: added missing info.plist file in iOS bindings * release 1.1.4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After I add the NewRelic.MAUI.Plugin to my .Net MAUI solution, I get compiler errors. I was also able to reproduce this with a brand new .Net MAUI sln. If I remove the NewRelic.MAUI.Plugin nuget package, the following compiler errors disappear.
Description
Steps to Reproduce
var safeInsets = On().SafeAreaInsets();
Expected Behavior
I would expect it to compile successfully.
Relevant Logs / Console output
Your Environment
Visual Studio (PC) Version 17.11.0
Additional context
You can read more about the Safe Insets feature in MAUI here: https://learn.microsoft.com/en-us/dotnet/maui/ios/platform-specifics/page-safe-area-layout?view=net-maui-8.0
The text was updated successfully, but these errors were encountered: