AndroidX for Fabulous.XamarinForms.Templates

[Happypig375]

The pull request I mentioned at https://github.com/dotnet/maui/issues/115#issuecomment-635163230.

[TimLariviere]

I guess the build issue is linked to the missing Xamarin.Android.FSharp.targets.

[Happypig375]

I don't use Shell, and I haven't noticed anything wrong with my app yet.

[Happypig375]

Why is Mac build failing?

[TimLariviere]

From the build logs:

This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ../packages/Xamarin.AndroidX.MultiDex.2.0.1/build/monoandroid90/Xamarin.AndroidX.MultiDex.targets.

[TimLariviere]

/azp run full build

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).

[Happypig375]

I can't figure out why this is failing. The package list should be correct.

[TimLariviere]

I missed that the import of NuGet.targets was removed. So Android weren't restoring its packages. But now, it is complaining about resource style/Theme.AppCompat.Light.Dialog (aka com.companyname:style/Theme.AppCompat.Light.Dialog) not found..

[Happypig375]

/azp run full build

[azure-pipelines[bot]]

Commenter does not have sufficient privileges for PR 750 in repo fsprojects/Fabulous

[Happypig375]

...

[TimLariviere]

Yeah, sorry for that. Azure DevOps is restrictive on that.

[TimLariviere]

/azp run full build

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).

[Happypig375]

This commit should be it. Having that property set to true actually makes Visual Studio set TargetFramework to v9.0 and TargetAndroidSDK to 28 instead of 29.

[TimLariviere]

Hmm. Is it because MSBuild picks the wrong version of the Android Build tools?

_ResolveMonoAndroidSdks:
  MonoAndroid Tools: /Library/Frameworks/Xamarin.Android.framework/Libraries/xbuild/Xamarin/Android/
  Android Platform API level: 29
  TargetFrameworkVersion: v10.0
  Android NDK: /Users/runner/Library/Android/sdk/ndk-bundle/
  Android SDK: /Users/runner/Library/Android/sdk/
  Android SDK Build Tools: /Users/runner/Library/Android/sdk/build-tools/28.0.3/
  Java SDK: /Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home/
  Application Java class: android.app.Application

[Happypig375]

Should be. The template executes fine locally.

[TimLariviere]

It doesn't seem to be that. Let's try bumping Mono to the latest version.

[Happypig375]

@TimLariviere Can you verify that the template executes successfully locally? It does on my side.

[TimLariviere]

I have indeed the same issue locally. I'm investigating why.

[TimLariviere]

/azp run full build

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).

[TimLariviere]

/azp run full build

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).

[TimLariviere]

/azp run full build

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).

[TimLariviere]

/azp run full build

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).

[TimLariviere]

Ok. Seems like it was an issue with the NuGet restore process. I removed the .nuget folder and manually ran nuget restore before building the templates. NuGet.targets was an old way of restoring packages and I finally managed to get rid of it.

[TimLariviere]

/azp run full build

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).

[Happypig375]

:tada:

[TimLariviere]

/azp run full build

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).