You can try overexposing your pfx and make sure the "Include all certificates" option is cleared to exclude the full certificate chain, which may cause some problems.
If this does not help use AssemblyKeyName ("xxx") instead of AssemblyKeyFile. The sn.exe -i key.pfx xxx command must be executed on your build server or development machine first to install the key in CSP. (I think your error message is caused only by the AssemblyKeyFile attribute.)
Let me note that there is no need to use your trusted certificate (signed by some certification authority) to sign (or strong name) the subscription. A strongly named assembly can be digitally signed for authentication / security purposes later.
This way you can also avoid the problem if you create a new key using the strong name tool:
sn -k keyPair.snk
and use the current .pfx only with, for example, SignTool.
source share