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
I tried to send with version 1.2 data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABoAAAAaCAYAAACpSkzOAAABfUlEQVRIS72UPU/DMBRF+69hYaJIbBUjfwFRkFCLKFH4iBQWOpeJbMBG5kzGJ+pLbOeFhKbhSkdW/O57t07dTowx/4K6OQaNjfXry9rK7IHInRuGaA011EM0n4PMrkLSNF1bzAhchEGaaTCceuegz68Pdb+NnYI2mzcay1WrazDfC0qSp06KoqCxXLW6BvOrIM0QIqcR8az5Qqz6BXFNGSqnEfHMPnWtT7Dyg57jRxPHcbnyhYeDu4SfPmYIDwm/WydICqvovlwJzvMcU2/hp09mCVbNoOhuVRn+EoaPHj6oILOs6iC36JoxdoVpIS5WfpCEhGHhbQtF3fW7MMuqeSKNLMswt4q61idY1UHL5cK0Eb467VnrE6z6Bck15+pyQdhj5RlRD3tcrLqDeMfyJ6rV2aeOT6uDF3Rze2WuF/uHuV6QZtoXXpBNPmeTT/Ab7itpq7NKyOV8fuAFAVdxWxzMds67zPaCYHY2O52eTM1Avo+OD8uTCF7IeJjJD3xajPLilAzRAAAAAElFTkSuQmCC
But failed with this response b'{"message":"The request could not be fulfilled because of an unknown error. For assistance, please send details about your request and the TrackingID from the response header to our support team: https://developer.ciscospark.com/support.html. TrackingID: ROUTER_5E5471C3-DD2D-01BB-64D7-40687DE464D7","errors":[{"description":"The request could not be fulfilled because of an unknown error. For assistance, please send details about your request and the TrackingID from the response header to our support team: https://developer.ciscospark.com/support.html. TrackingID: ROUTER_5E5471C3-DD2D-01BB-64D7-40687DE464D7"}],"trackingId":"ROUTER_5E5471C3-DD2D-01BB-64D7-40687DE464D7"}'
The text was updated successfully, but these errors were encountered:
hello, yes. normally Webex is expected to support this open standard. example of card is below. currently Messages API refuses Image object with this data in url. On other hand, card is showing normally in Card Designer.
From microsoft/AdaptiveCards#628, AdaptiveCards already supports image data uri.
I tried to send with version 1.2
data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABoAAAAaCAYAAACpSkzOAAABfUlEQVRIS72UPU/DMBRF+69hYaJIbBUjfwFRkFCLKFH4iBQWOpeJbMBG5kzGJ+pLbOeFhKbhSkdW/O57t07dTowx/4K6OQaNjfXry9rK7IHInRuGaA011EM0n4PMrkLSNF1bzAhchEGaaTCceuegz68Pdb+NnYI2mzcay1WrazDfC0qSp06KoqCxXLW6BvOrIM0QIqcR8az5Qqz6BXFNGSqnEfHMPnWtT7Dyg57jRxPHcbnyhYeDu4SfPmYIDwm/WydICqvovlwJzvMcU2/hp09mCVbNoOhuVRn+EoaPHj6oILOs6iC36JoxdoVpIS5WfpCEhGHhbQtF3fW7MMuqeSKNLMswt4q61idY1UHL5cK0Eb467VnrE6z6Bck15+pyQdhj5RlRD3tcrLqDeMfyJ6rV2aeOT6uDF3Rze2WuF/uHuV6QZtoXXpBNPmeTT/Ab7itpq7NKyOV8fuAFAVdxWxzMds67zPaCYHY2O52eTM1Avo+OD8uTCF7IeJjJD3xajPLilAzRAAAAAElFTkSuQmCC
But failed with this response
b'{"message":"The request could not be fulfilled because of an unknown error. For assistance, please send details about your request and the TrackingID from the response header to our support team: https://developer.ciscospark.com/support.html. TrackingID: ROUTER_5E5471C3-DD2D-01BB-64D7-40687DE464D7","errors":[{"description":"The request could not be fulfilled because of an unknown error. For assistance, please send details about your request and the TrackingID from the response header to our support team: https://developer.ciscospark.com/support.html. TrackingID: ROUTER_5E5471C3-DD2D-01BB-64D7-40687DE464D7"}],"trackingId":"ROUTER_5E5471C3-DD2D-01BB-64D7-40687DE464D7"}'
The text was updated successfully, but these errors were encountered: