-
Notifications
You must be signed in to change notification settings - Fork 32
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
Issues with Template #69
Comments
Hi @guipalazzo - Could you please elaborate on how the using directives are not being recognized? Are you running into specific build errors? If so, could you please share a binlog? |
Hello @rachelkang, When you open the template on your end, does it work out of the box? When I do so on my end, I see a 'Cannot resolve symbol 'NewBindingMaciOS' related to the using directives of 'MauiPage.xaml.cs'. I was expecting it though, as I'm using a PC.
However, even if I remove the iOS, MacOS and PC related directives, as follows, I'm still not able to use 'NewBinding'.
So, the question would be, what are the necessary steps in order to make this work? I tried to compile the native project in Android Studio, but nothing happens, so I'm not sure how to make this slim bindings work at all. |
Hello @rachelkang, When you open the template on your end, does it work out of the box? When I do so on my end, I see a 'Cannot resolve symbol 'NewBindingMaciOS' related to the using directives of 'MauiPage.xaml.cs'. I was expecting it though, as I'm using a PC.
However, even if I remove the iOS, MacOS and PC related directives, as follows, I'm still not able to use 'NewBinding'.
So, the question would be, what are the necessary steps in order to make this work? I tried to compile the native project in Android Studio, but nothing happens, so I'm not sure how to make this slim bindings work at all. |
Description
The template, as is, does not seem to be working. The using directives are not being recognized, apparently due to the declaration of Metadata.xml.
I tried many different approaches to fix this (mostly by trying to add the generated *. aar file somehow to the project, for instance, as an AndroidLibrary or as an EmbeddedReferenceJar), but I'm getting to the conclusion that the original intention was to have something behind the scenes that would make the conversion specified in the Metadata.xml implementation work.
As per the content generated about the template, I was expecting that a simple build in Android Studio would be enough to make it happen. Before trying to fix this as I mentioned above, I was expecting that a simple build of the native Android project, followed by the build of the .Net Maui project, would be enough, as per the high level discussion on this between @rachelkang and @jamesmontemagno.
Steps to Reproduce
Link to public reproduction project repository
No response
Environment
The text was updated successfully, but these errors were encountered: