Skip to content
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

Compile issues after updating to 6.3.0 #3420

Closed
danieleardissone opened this issue Jun 3, 2019 · 7 comments

Comments

@danieleardissone
Copy link

commented Jun 3, 2019

馃敊 Regression

Updating to v. 6.3.0 produced some compile issues in my Xamarin Android project.
I've already cleaned obj and bin folders but nothing changes.

"LinkAssemblies" task fails unexpectedly. System.IO.FileNotFoundException: Could not load assembly 'NovusMobile.Droid, Version=0.0.0.0, Culture=neutral, PublicKeyToken='. Perhaps it doesn't exist in the Mono for Android profile? Nome file: 'NovusMobile.Droid.dll' in Java.Interop.Tools.Cecil.DirectoryAssemblyResolver.Resolve(AssemblyNameReference reference, ReaderParameters parameters) in Java.Interop.Tools.Cecil.DirectoryAssemblyResolver.GetAssembly(String fileName) in Xamarin.Android.Tasks.LinkAssemblies.Execute(DirectoryAssemblyResolver res) in Xamarin.Android.Tasks.LinkAssemblies.Execute() in Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute() in Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()

Failed to generate resource table for split '' "Failed to generate resource table for split ''".

Attribute "statusBarBackground" already defined with incompatible format.
Attribute "layout_anchorGravity" already defined with incompatible format.
Attribute "layout_insetEdge" already defined with incompatible format.
Attribute "layout_dodgeInsetEdges" already defined with incompatible format.
Attribute "layout_dodgeInsetEdges" already defined with incompatible format.

Old (and correct) behavior

v6.2.3 works as expected

Current behavior

Reproduction steps

Update MVVMCross NuGet packages from version 6.2.3 to 6.3.0

Configuration

Version: 6.3

Platform:

  • 馃摫 iOS
  • [x ] 馃 Android
  • 馃弫 WPF
  • 馃寧 UWP
  • 馃崕 MacOS
  • 馃摵 tvOS
  • 馃悞 Xamarin.Forms
@danieleardissone danieleardissone changed the title Compile issue after updating to 6.3.0 Compile issues after updating to 6.3.0 Jun 3, 2019
@martijn00

This comment has been minimized.

Copy link
Member

commented Jun 3, 2019

Do you set your Android target and compile framework to 9.0?

@danieleardissone

This comment has been minimized.

Copy link
Author

commented Jun 3, 2019

@martijn00 Yes, with 8.1 I was not able to update NuGet packages.

@Cheesebaron

This comment has been minimized.

Copy link
Member

commented Jun 4, 2019

None of the attributes it complains about are related to MvvmCross. Make sure you clean your project thoroughly. Try remove all bin and obj folders.

I usually run:

git clean -fdx
@danieleardissone

This comment has been minimized.

Copy link
Author

commented Jun 5, 2019

Unfortunately git clean -fdx didn't help me, compile issues stay the same.
I'm trying to find if there are some packages that could create conflicts with the new version of MvvmCross.
I cannot update to v. 6.3.0 at the moment.

@Anil86

This comment has been minimized.

Copy link

commented Jun 5, 2019

Steps:

  1. Clean the solution.
  2. Build using Visual Studio Build (not ReSharper build)

I hope this will resolve the issue.

@Cheesebaron

This comment has been minimized.

Copy link
Member

commented Jun 6, 2019

@danieleardissone dunno. It is hard to help you with the information you provide. I have a couple of apps on 6.3.0 that build just fine.

If you want, we can try set up a session where you show it to me while you share your screen. Send me an e-mail or DM me on twitter and we can find a time to do that.

@danieleardissone

This comment has been minimized.

Copy link
Author

commented Jun 11, 2019

@Cheesebaron thanks for you time! I finally solved it migrating the default package manager format from packages.config to PackageReference. I don't know exacly why but it solved this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can鈥檛 perform that action at this time.