You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing changes to our Azure Function App that utilizes the Svix C# client, we began getting 404 errors trying to send messages. After much headache, we realized the issue was that the URL we had provided to the client had a "/" at the end (https://api.us.svix.com/). The message returned by the client simply stated the following: "Error calling CreateMessageApiV1AppAppIdMsgPost:", with no other indication of what might be going on.
It might be helpful to include more specific information after the colon, indicating that the provided URL is causing issues when making calls to the API.
The text was updated successfully, but these errors were encountered:
One thing worth noting: you don't need to actually set a URL, it's automatically done by the libs based on the auth token. Though this is a good point about URL normalization and error messages!
I saw that the URL is optional in the documentation, but in implementation, it appeared to be required for the SvixOptions class, which is required for the SvixClient. Perhaps I missed something in the documentation outlining a different way of creating the client that didn't require the SvixOptions as a parameter.
Bug Report
Version
0.83.1
Platform
Windows 64-bit, Azure Function App
Description
While testing changes to our Azure Function App that utilizes the Svix C# client, we began getting 404 errors trying to send messages. After much headache, we realized the issue was that the URL we had provided to the client had a "/" at the end (https://api.us.svix.com/). The message returned by the client simply stated the following: "Error calling CreateMessageApiV1AppAppIdMsgPost:", with no other indication of what might be going on.
It might be helpful to include more specific information after the colon, indicating that the provided URL is causing issues when making calls to the API.
The text was updated successfully, but these errors were encountered: