-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bouncy Castle - support for 3.1 #8
Comments
Hi! .NET Core apps can consume .NET Framework library, albeit their functionality may be limited when used like that. In our case, however, the required functionality works as expected, so you may safely ignore the warning. It shouldn't prevent you from building and running your application. |
@alexalok Thank you for your response, I was going to use as you said anyway. But I'm trying to add services.AddApns(); And it says that there is no reference for it. |
It seems that you've referenced the main dotAPNS package. Instead, you should reference dotAPNS.AspNetCore package, which contains code that integrates dotAPNS with ASP.NET Core projects. Also, if you reference dotAPNS.AspNetCore, you can safely remove the reference to dotAPNS as it is implicitly added to the project anyway. |
Thank you so much. One more thing, when using the certificate we do need to specify the password. How would we do that after CreateUsingCert |
I have created another certificate with no password, then faced this issue: An error occurred while sending the request. |
Please provide a code sample that you have issues with. Note that |
Well, I have been able to work with the certificate issue. Only this issue is now I'm facing:
`// POST
|
I see. Could you please provide a full stack trace of an exception? Right now I'm not entirely sure as to what can be the cause of the issue you're facing. |
|
Issue is not happening anymore once I have set sandbox to true |
According to the stack trace, I can see that the actual exception happens somewhere inside the HttpClient that dotAPNS uses to make HTTP/2 requests. If possible, create a separate project with the minimum code that reproduces the issue and send it to me at contact@alexalok.me Another option would be to switch to a token-based connection. If you have the proper rights in the Apple Developer Account, I highly suggest to do so as the certificate-based HTTP/2 connection support overall seems to be quite quirky in .NET (see #3, #4). |
Hi, @Faisal0sal, just checking if you still need an assistance. If you're all up and running, perhaps the issue can be closed? |
The issue is closed due to the lack of feedback. |
Warning NU1701: Package 'BouncyCastle 1.8.5' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework '.NETCoreApp,Version=v3.1'. This package may not be fully compatible with your project. (NU1701)
The text was updated successfully, but these errors were encountered: