Closed pregress closed 7 months ago
/azp run
Any reason why .NET 6 pipelines fail? Can't view the error since it azure devops.
/azp run
/azp run
We have some security rules in place that make it so forked PRs (like this one) can't access the credentials we use during our integration testing. Could you convert these changes into a branch on this repo instead?
We have some security rules in place that make it so forked PRs (like this one) can't access the credentials we use during our integration testing. Could you convert these changes into a branch on this repo instead?
@timtay-microsoft I do not have permissions to create a branch on this repo
Ah, my apologies. I'll go ahead and create that branch for you. #3450 should be merged in shortly
Your fix has been merged in #3450, so I'll close this PR
Checklist
main
branch.Description of the changes
Added the error code: 404103 for Device online. So users can handle this error gracefully.
Reference/Link to the issue solved with this PR (if any)
Fixes: https://github.com/Azure/azure-iot-sdk-csharp/issues/3442