Reputation: 89
My currently methodology for downloading message attachments through Graph API is this:
From testing, I have found that the time it takes to get the API request in step 3 is my bottleneck. This is due to the large amount of data being returned in the field contentBytes. I will call this the "download".
A file of 2MB can take up to 10 seconds to download on a good connection. When I am limited to a download speed of 5mbps, this can take over a minute to retrieve.
So I have two thoughts I would like to explore:
Upvotes: 2
Views: 1155
Reputation: 1138
contentLocation is always null. From my understanding, these file attachments should have a URI here for me to download from. Does anyone know why I am not provided a contentLocation?
I have tried this, and it is null in the response body, we can submit the issue on the github issue
Upvotes: 1