AndroidX: Problem with Dotfuscator

I couldn’t compile my project using Dotfuscator:

Symbols were found but are not matching the assembly at Mono.Cecil.ModuleDefinition.ReadSymbols(ISymbolReader reader, Boolean throwIfSymbolsAreNotMaching) at Mono.Cecil.ModuleReader.ReadSymbols(ModuleDefinition module, ReaderParameters parameters) at Mono.Cecil.ModuleReader.CreateModule(Image image, ReaderParameters parameters) at Mono.Cecil.ModuleDefinition.ReadModule(String fileName, ReaderParameters parameters) at Xamarin.AndroidX.Migration.CecilMigrator.Migrate(String source, String destination) in D:\a\1\s\source\Xamarin.AndroidX.Migration\CecilMigrator.cs:line 85 at Xamarin.AndroidX.Migration.CecilMigrator.Migrate(IEnumerable`1 assemblies) in D:\a\1\s\source\Xamarin.AndroidX.Migration\CecilMigrator.cs:line 50 at Xamarin.AndroidX.Migration.BuildTasks.CecilfyFiles.Execute() in D:\a\1\s\source\Xamarin.AndroidX.Migration.BuildTasks\CecilfyFiles.cs:line 35 x2Apps.CheckPlaca.App.Android C:\Users\mario.nuget\packages\xamarin.androidx.migration\1.0.0-preview02\build\Xamarin.AndroidX.Migration.targets 182

Setting the DotfuscatorXamarinEnabled option to FALSE in my csproj solves the problem.

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 2
Comments: 15 (1 by maintainers)

Commits related to this issue

Allow migration to continue when symbols are bad Fixes #38 Fixes #8 Fixes #79 Fixes #93 — committed to xamarin/AndroidX by mattleibow 4 years ago
Allow migration to continue when symbols are bad (#98) Allow migration to continue when symbols are bad: - Fixes #38 - Fixes #8 - Fixes #79 - Fixes #93 — committed to xamarin/AndroidX by mattleibow 4 years ago

Most upvoted comments

I know. But we had to migrate because the newest instabug xamarin version dependes on these packages and wen needed to update instabug because it includes some critical bug fixes. Instabug shouldn’t release release updates depending on prerelease packages. Anyways, i fixed it. Here is the solution if anybody is interested in the future:

I commented out the following part inside the PreEmptive.Dotfuscator.Xamarin.targets file.

  <!--<_DotfuscatorXamarinOriginalFiles Include="@(_DebugSymbolsIntermediatePath)"
                                        Condition="'$(_DebugSymbolsProduced)'=='true' and '$(SkipCopyingSymbolsToOutputDirectory)' != 'true' and '$(CopyOutputSymbolsToOutputDirectory)'=='true'">
        <Destination>%(_DebugSymbolsIntermediatePath.Filename)%(_DebugSymbolsIntermediatePath.Extension)</Destination>
      </_DotfuscatorXamarinOriginalFiles>-->

Then it runs fine.

MarvinFrankenfeld on Jan 8, 2020

Are there any news? We are having the same problem since updating to AndroidX and this is stopping us from delivering an important update to our users.

MarvinFrankenfeld on Jan 3, 2020

Hello everyone,

I am using Babel and I am having the same problems in building the release version but I am using the stable versions of AndroidX (1.0.0)

Xamarin.AndroidX.Migration.1.0.0/build/monoandroid90/Xamarin.AndroidX.Migration.targets(227,9): error : Symbols were found but are not matching the assembly

Can anybody help me with this?

maneca on Feb 24, 2020