Find-PSResource doesn't find modules in ADO repository (feed) (Error message: Object reference not set to an instance of an object)

[nbdinara]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.

Steps to reproduce

Find-PSResource -Name {ModuleName}-Repository {ADOFeedName} -Credential $Credentials
Find-PSResource -Repository {ADOFeedName} -Type Module

I tested two different ways and I've got the same result (error):
VERBOSE: Searching in repository {ADOFeedName}
Find-PSResource: Object reference not set to an instance of an object.

Command that we use in our code:
Find-PSResource -Name {ModuleName} -Prerelease:($installPrereleaseModule) -Version $ModuleVersion -Repository {ADOFeedName} -Credential $Credentials -IncludeDependencies

Expected behavior

Find-PSResource retrieves requested Module from ADO feed {ADOFeedName}

Actual behavior

VERBOSE: Searching in repository {ADOFeedName} 
Find-PSResource: Object reference not set to an instance of an object.

Error details

Error started to happen on version 3.0.20.
3.0.19 worked fine

Environment data

ModuleType Version    PreRelease Name                                ExportedCommands
---------- -------    ---------- ----                                ----------------
Binary     3.0.20     beta20     powershellget                       {Find-PSResource, Get-PSResource, Get-PSResourceR…
Script     2.2.5                 PowerShellGet                       {Find-Command, Find-DscResource, Find-Module, Fin…

Key   : PSVersion
Value : 7.3.3
Name  : PSVersion


Key   : PSEdition
Value : Core
Name  : PSEdition


Key   : GitCommitId
Value : 7.3.3
Name  : GitCommitId


Key   : OS
Value : Microsoft Windows 10.0.22621
Name  : OS


Key   : Platform
Value : Win32NT
Name  : Platform


Key   : PSCompatibleVersions
Value : {1.0, 2.0, 3.0, 4.0…}
Name  : PSCompatibleVersions


Key   : PSRemotingProtocolVersion
Value : 2.3
Name  : PSRemotingProtocolVersion


Key   : SerializationVersion
Value : 1.1.0.1
Name  : SerializationVersion


Key   : WSManStackVersion
Value : 3.0
Name  : WSManStackVersion

Visuals

[thisjustin816]

I think this is related to an issue I'm seeing with Install-PSResource. The verbose output of that cmdlet gives a little more. However the params are getting parsed is getting messed up.

Here's how I'm using it. The version param is getting duplicated and then pushing the rest of the param values down a position. (The $module variable is a module object returned from Find-Module)

        $currentOperation = "$($module.Name) - $($module.Version)"
        Write-Host -Object "`n"
        Write-ProgressToHost -Activity $activity -Status 'Installing...' -CurrentOperation $currentOperation
        $installPsResource = @{
            Name                = $module.Name
            Version             = "[$($module. Version)]"
            Repository          = $module.Repository
            Credential          = $psCredential
            SkipDependencyCheck = $true
        }
        Write-Host -Object ( $installPsResource | Out-String )
        Install-PSResource @installPsResource -Verbose

##[info] Installing  Required Modules | Installing... | PSUtils - 1.11.16

Name                           Value                                                                                   
----                           -----                                                                                   
Credential                     System.Management.Automation.PSCredential                                               
SkipDependencyCheck            True                                                                                    
Name                           PSUtils                                                                                 
Version                        [1.11.16]                                                                               
Repository                     PSSiOpsFeed                                                                             



VERBOSE: All paths to search: 'C:\Users\VssAdministrator\Documents\WindowsPowerShell\Modules'
VERBOSE: All paths to search: 'C:\Users\VssAdministrator\Documents\WindowsPowerShell\Scripts'
VERBOSE: Retrieving directories in the path 'C:\Users\VssAdministrator\Documents\WindowsPowerShell\Modules'
VERBOSE: Retrieving directories in the path 'C:\Users\VssAdministrator\Documents\WindowsPowerShell\Scripts'
VERBOSE: Performing the operation "Install-PSResource" on target "package to install: 'PSUtils'".
VERBOSE: Parameters passed in >>> Name: 'PSUtils'; Version: '[1.11.16]'; Prerelease: '[1.11.16]'; Repository: 'False'; 
AcceptLicense: 'PSSiOpsFeed'; Quiet: 'False'; Reinstall: 'False'; TrustRepository: 'False'; NoClobber: 'False'; 
AsNupkg: 'False'; IncludeXml 'False'; SavePackage 'True'; TemporaryPath 'False'
VERBOSE: Attempting to search for packages in 'PSSiOpsFeed'
VERBOSE: Untrusted repository accepted as trusted source.
VERBOSE: Searching in repository PSSiOpsFeed
Install-PSResource : Object reference not set to an instance of an object.

[jorinschramm-truesec]

I'm getting this with beta20 on Install-PSResource and Find-PSResource on both Windows and Linux when using a GitHub Packages-hosted repository, e.g.:

PS> Find-PSResource -Repository MyRepo -Name '*'
VERBOSE: credential successfully read from vault and set for repository: MyRepo
VERBOSE: Searching in repository MyRepo
Find-PSResource: Object reference not set to an instance of an object.

beta19 does not have this issue.

[MVKozlov]

CHANGELOG

Move off of NuGet client APIs and use direct REST API calls for remote repositories (#1023)
Move off of NuGet client APIs for local repositories (#1065)

It seems as of v3.0.20+ nuget compatibility has been completely removed ?

Does this mean #215 or #969 will never be implemented
or
nuget compatibility should be moved to public interface flag instead of
https://github.com/PowerShell/PowerShellGet/blob/8f6a237bdeb6915793a9cfecca19a0d8db35c120/src/code/V3ServerAPICalls.cs#L91