-
Notifications
You must be signed in to change notification settings - Fork 336
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: : XamlC error XFC0000 : Cannot resolve type "PopupPage" when using xmlns:rg="http://rotorgames.com" #619
Comments
Any update on this issue? Here is one sample project which I have created to reproduce this issue. Seems like this issue is coming because of the latest stable release i.e. Xamarin.Forms 4.8.0.1687 |
@shweta1915 thank you for the demo, I have provided a 'fixed' example Here this is indeed unusual, it does seem that Xamarin.Forms 4.8.0.1687 is causing some issue. I also noticed that if you convert the popup pages to use the older @dansiegel do you have any idea why this would be so? Would the latest Xamarin.Forms somehow be interfering with your xmlns definition? any use of |
@LuckyDucko Thank you for the solution, it worked |
This solution is temporally since you always have to do it by hand. I am using xamarin 5 and having same issue. |
@valentasm1 ill reopen and change the title of the bug to better reflect the bug thats happening here |
this error does not let me work with the hot reload |
I was able to fix the XamlC error and hot reload problem by:
|
@tkefauver it's made me crazy for days, can you share it as a small sample code please? |
Try this
|
It wasn't about the popup page, It resolved when I add the xmlns to the App.xaml. |
I am using Prism with DryIoc (and not unity). Following a suggestion from another thread I replaced
with
in my App.xaml file and the error disappeared. I had the same error with PopupPage from Rg.Plugins.Popup, so I also replaced
with
and that error disappeared as well. As these are two different libraries, acting similarly, it might be a general VS issue. But could also be the same error in two libraries. The link from @ysmoradi says that using a custom namespace requires a direct reference to the assembly through C# code in order for VS to find it and not show this error. I haven't tried it but that might also be a possible solution. |
Quote - .."this is indeed unusual, it does seem that Xamarin.Forms 4.8.0.1687 is causing some issue."... We are up to version 5.0.0.2515 of Xamarin.Forms. Are you planning to resolve this issue as we cannot keep using alternative code and "tricks" to work around this surely ? |
@Krammig the alternative code is actually I believe the original code that was within Rg. I no longer maintain Rg as I have been putting my limited time into Mopups, however its interesting that Prism has this issue as well, as @dansiegel was the one who originally introduced the I have always relied on using the older version of xmlns:pages="clr-namespace:Rg.Plugins.Popup.Pages;assembly=Rg.Plugins.Popup" |
馃悰 Bug Report
Getting the exception in the error window for each created view "Error: : XamlC error XFC0000 : Cannot resolve type "PopupPage""
Due to this reason application is not running from the app launcher. It keeps crashing.
Note: If the app connected to debugging mode then there is no issue.
Expected behavior
The app should not crash in any mode
Reproduction steps
Version: 2.0.0.9
Platform:
The text was updated successfully, but these errors were encountered: