This behavior is an expected one as the respective package is targeted only to Windows - Legacy (.Net Framework 4.6.1)
The only solutions are these:
- Ask the developer to target this package to Windows or Cross-Platform compatibilities
- Use the Windows-Legacy projects until the package is targetted to Windows or Cross-Platform compatibilities
- Use Rest API calls to achieve the same results in Windows or Cross-Platform compatibilities
