Skip to content

[Bug]: NU3012 restore failure: ReactiveUI.Avalonia 11.4.12 author signing certificate revoked #113

@xujiegb

Description

@xujiegb

Describe the bug 🐞

ReactiveUI.Avalonia 11.4.12 currently fails during NuGet restore because the author signing certificate is reported as revoked.

The error is:

text error NU3012: Package 'ReactiveUI.Avalonia 11.4.12' from source 'https://api.nuget.org/v3/index.json': The author primary signature found a chain building issue: Revoked: certificate revoked

In the same restore operation, related ReactiveUI/Splat packages signed with the same certificate also fail with NU3012, for example:

text ReactiveUI 23.2.27 Splat 19.3.1 Splat.Core 19.3.1 Splat.Logging 19.3.1 Splat.Builder 19.3.1

This breaks CI for existing projects that still depend on the ReactiveUI.Avalonia 11.4.x line.

Step to reproduce

  1. Use a project depending on ReactiveUI.Avalonia 11.4.12.
  2. Run dotnet restore or dotnet publish in CI.
  3. NuGet validates the package author signature.
  4. Restore fails with NU3012 because the author signing certificate is revoked.

Reproduction repository

https://github.com/2dust/v2rayN

Expected behavior

NuGet restore should succeed for the previously released ReactiveUI.Avalonia 11.4.12 package.

If possible, could you please consider publishing a re-signed 11.4.x patch release, for example 11.4.13, using the same source/content as 11.4.12 but with a valid package signature?

Screenshots 🖼️

Not applicable.

IDE

No response

Operating system

Windows, Linux, macOS

Version

No response

Device

No response

ReactiveUI.Avalonia Version

11.4.12

Additional information ℹ️

I noticed that ReactiveUI.Avalonia 12.0.2 is available and re-signed.

However, 12.0.2 appears to include dependency and compatibility changes, so it is not a safe drop-in replacement for existing Avalonia 11.3.x projects. In our case, upgrading to ReactiveUI.Avalonia 12.0.2 introduces additional Avalonia AXAML/DataGrid binding compatibility issues during build.

For projects that intentionally remain on the Avalonia 11.3.x stack, a re-signed 11.4.x patch release would be very helpful.

No new feature or code change is requested here. The request is only about restoring package usability after the signing certificate revocation

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions