https://support.huawei.com/enterprise/zh/integrated-communications-platform/cloudipcc-pid-21796204?category=developer-documents《CloudIPCC V600R006C10 二次开发培训套件》下载包里面的pdf文档《华为CloudIPCC联络中心解决方案二次开发&集成培训.pdf》文档里面的“用户侧”部分：要实现语音和视频功能1. PC端是否只支持windows环境下的IE浏览器，chrom，firefox是否支持？2. Mobile SDK 移动端接入手机Mobile SDK是否只支持原生APP应用，如果是手机H5应用（手机上的网页）如何接入？谢谢。下面是文档中的截图

使用eSDK CloudVC 20.1.RC1 接口参考(SMC, Java Native)   后端发起登录，错误日志如下esdk_tp_config.properties配置文件中  sdkserver.url中的ip和端口号是SMC的ip地址和端口号吗

//cpp code //设备抓拍图片上传 int iPicNum = 4;  //4M,保存图片内容 char* pAllPicBuff = new char[4 * 1024 * 1024]; if (NULL == pAllPicBuff) {     printf("NULL == pAllPicBuff\n");     return 0; } memset(pAllPicBuff, 0, 4 * 1024 * 1024); //抓拍上传4张1M图片 IVS_UINT32 uiSnapImgInfoLen = sizeof(IVS_FACE_SNAPSHOT_INFO) +                  4*sizeof(IVS_FACE_SNAPSHOT_IMG_INFO)+ 4*1024*1024; char* pSnapImgInfo = new char[uiSnapImgInfoLen]; if (NULL == pSnapImgInfo) {     return 0; } memset(pSnapImgInfo, 0, uiSnapImgInfoLen); //抓拍上传4张1M图片 IVS_FACE_SNAPSHOT_INFO* stSnapImgInfo = (IVS_FACE_SNAPSHOT_INFO*)pSnapImgInfo; IVS_CHAR cCameraDomainCode[IVS_DEV_CODE_LEN + 1] = "00956440000000000101#265773b842b143d396299f7b7c9c310f"; memcpy(stSnapImgInfo->cCameraCode,cCameraDomainCode,sizeof(cCameraDomainCode)); stSnapImgInfo->iPicNum = iPicNum; for(int i=0; i<iPicNum; i++) {     //图片抓拍时间YYYYMMDDHHMMSSmmm，24小时制，UTC时间     stSnapImgInfo->stSnapInfo[i].stFaceInfo.ullSnapTime = 20171101072130666; //即抓拍时间是 20171101152130666     //都是大图，没有抠图     stSnapImgInfo->stSnapInfo[i].stFaceInfo.eITSType = ITS_PICTURE_TYPE_FACE_SCENE;     //抓拍组别     stSnapImgInfo->stSnapInfo[i].stFaceInfo.uiSnapshotGroup = i;     //用于存放图片内容     char* pStreamInfoCopy = pAllPicBuff;       unsigned long uiPicLen = 0;     char cPicName[256] = {0};     snprintf(cPicName, 256, "/home/ivs_imgu/bin/test_%d.jpg", i);       FILE *fSnapPic=NULL;     fSnapPic = fopen(cPicName, "rb");     if ( NULL == fSnapPic )     {         printf("fopen failed\n");         return 0;     }     while(!feof(fSnapPic))     {         uiPicLen += fread(pStreamInfoCopy + uiPicLen, 1, 1024,                            fSnapPic);     }     fclose(fSnapPic);     //单张图片实际长度     stSnapImgInfo->stSnapInfo[i].stSnapImg.ulPicLen = uiPicLen;     //图片数据     stSnapImgInfo->stSnapInfo[i].stSnapImg.pPictureBuf = pAllPicBuff; }   iRet = IVS_SDK_UploadDeviceImg(iSessionID, IVS_SNAPSHOT_TYPE_FACE, pSnapImgInfo);

请问，使用eSDK CloudVC Demo时，总是出现：Program type already present: android.support.annotation.AnyRes是什么原因？怎么破解...

现在客户端想使用TestFlight测试，通过后准备上架。但是apple在审查过程中报ITMS-90809: Deprecated API Usage - App updates that use UIWebView will no longer be accepted as of December 2020. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview).经代码审查和修改后，发现基线集成的FacebookSDK中有使用UIWebView,具体如下：./Pods/OpenFramework/FacebookSDK/FBSDKShareKit.framework/Headers/FBSDKShareDialogMode.h:   @Displays the dialog in a UIWebView within the app../Pods/OpenFramework/FacebookSDK/FBSDKShareKit.framework/Headers/FBSDKShareDialogMode.h:   @Displays the feed dialog in a UIWebView within the app.Binary file ./Pods/OpenFramework/FacebookSDK/FBSDKCoreKit.framework/FBSDKCoreKit matchesBinary file ./Pods/OpenFramework/FacebookSDK/Bolts.framework/Bolts matches./Pods/OpenFramework/FacebookSDK/Bolts.framework/Headers/BFWebViewAppLinkResolver.h: A reference implementation for an App Link resolver that uses a hidden UIWebView现在的疑问是：基线是否使用FacebookSDK的功能如果将FacebookSDK更新的最新的版本，对我们客户端有什么影响吗？    谢谢~！

在使用sdk-c接入华为物联网平台时，出现错误 连接失败，retcode -15的错误代码，分析错误到device_demo.c中的int MqttBase_CreateConnection函数中的MQTTAsync_connect 函数调用。这个函数在sdk-c中没有源代码，它直接调用 MQTT的 DLL文件中对应的函数文件。在头文件MQTTAsyn.h中有声明声明中给出了函数的一些返回的错误代码的原因解释，可是怎么也没有找到 -15的错误返回代码。git 下载paho.mqtt.c代码，找到MQTTAsync.c文件中的int MQTTAsync_connect(MQTTAsync handle, const MQTTAsync_connectOptions* options)分析函数体中的 返回错误代码，发现，原来在MQTTAsync.h还有如下的一类返回值为-1~-17的错误代码的定义及错误原因说明：/** * Return code: No error. Indicates successful completion of an MQTT client * operation. */#define MQTTASYNC_SUCCESS 0/** * Return code: A generic error code indicating the failure of an MQTT client * operation. */#define MQTTASYNC_FAILURE -1/* error code -2 is MQTTAsync_PERSISTENCE_ERROR */#define MQTTASYNC_PERSISTENCE_ERROR -2/** * Return code: The client is disconnected. */#define MQTTASYNC_DISCONNECTED -3/** * Return code: The maximum number of messages allowed to be simultaneously * in-flight has been reached. */#define MQTTASYNC_MAX_MESSAGES_INFLIGHT -4/** * Return code: An invalid UTF-8 string has been detected. */#define MQTTASYNC_BAD_UTF8_STRING -5/** * Return code: A NULL parameter has been supplied when this is invalid. */#define MQTTASYNC_NULL_PARAMETER -6/** * Return code: The topic has been truncated (the topic string includes * embedded NULL characters). String functions will not access the full topic. * Use the topic length value to access the full topic. */#define MQTTASYNC_TOPICNAME_TRUNCATED -7/** * Return code: A structure parameter does not have the correct eyecatcher * and version number. */#define MQTTASYNC_BAD_STRUCTURE -8/** * Return code: A qos parameter is not 0, 1 or 2 */#define MQTTASYNC_BAD_QOS -9/** * Return code: All 65535 MQTT msgids are being used */#define MQTTASYNC_NO_MORE_MSGIDS -10/** * Return code: the request is being discarded when not complete */#define MQTTASYNC_OPERATION_INCOMPLETE -11/** * Return code: no more messages can be buffered */#define MQTTASYNC_MAX_BUFFERED_MESSAGES -12/** * Return code: Attempting SSL connection using non-SSL version of library */#define MQTTASYNC_SSL_NOT_SUPPORTED -13 /**  * Return code: protocol prefix in serverURI should be tcp://, ssl://, ws:// or wss://  * The TLS enabled prefixes (ssl, wss) are only valid if the TLS version of the library  * is linked with.  */#define MQTTASYNC_BAD_PROTOCOL -14 /**  * Return code: don't use options for another version of MQTT  */ #define MQTTASYNC_BAD_MQTT_OPTION -15 /**  * Return code: call not applicable to the client's version of MQTT  */ #define MQTTASYNC_WRONG_MQTT_VERSION -16 /**  *  Return code: 0 length will topic  */ #define MQTTASYNC_0_LEN_WILL_TOPIC -17至此，终于找到了  -15的对应的错误原因了。或许以后还会遇到其他的错误原因，记录并交流分享一下。

Response Code: 400Error Message: The  location constraint is incompatible for the region specific endpoint this request was sent to.Error Code:       IllegalLocationConstraintExceptionRequest ID:      00000171D44061F59011D81F3F8FC8AFHost ID:           gVNXYhZIxXzQmJYAuEry2vbWxP2mbdVkv5B4mJHidhajjxwhLnnvY73GmrbiYlq7

[2020-04-27 12:07:05.593|DEBUG|App|:0|111943] [DEBUG][2020/04/27 12:07:05.593367][MsaAccess.m:167][MSASDK] -[MsaAccess multiHttpCallBack:] uniqueId=1587982024911510, request.url=https://vsc07.prd.tv.t-mobilethuis.nl:443/VSP/V3/QueryRecmContent?from=throughMSAAccess, retCode=503, originCode=503, result=(null)[2020-04-27 12:07:05.593|DEBUG|App|:0|42815] [DEBUG][2020/04/27 12:07:05.593499][SQMLogImpl.m:15]SQMService [SQMService.m:236]getUIService[2020-04-27 12:07:05.593|DEBUG|App|:0|42815] [DEBUG][2020/04/27 12:07:05.593574][SQMLogImpl.m:15]SQMService [SQMUIServiceImpl.m:103]onReportInterface, onReportInterface: {  "Result" : 503,  "Code" : 503,  "Type" : "2",  "Cache" : "0",  "Name" : "QueryRecmContent",  "Page" : "LiveTVHomeViewController",  "Delay" : 723}[2020-04-27 12:07:05.593|DEBUG|App|:0|111943] [DEBUG][2020/04/27 12:07:05.593597][SNetTask.m:151]请求接口:QueryRecmContentReq,请求数据：{    queryDynamicRecmContent =     {        ratingID = 7;        recmScenarios =         (                        {                businessType = BTV;                contentType = PROGRAM;                count = 12;                entrance = "Program_Whats_On";                offset = 0;            }        );    };}，返回数据:(null)

Exceeded retry limitation, max retry count:3, error message:cURL error 6: Could not resolve host: william.vju_fub45zvhe0riff1dp-yahjqlgtkxcrrn7ec- (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)

# ServiceComb Java Chassis CSE SDK 报错 Connection Refused > 查看服务的运行日志, 会发现运行是报错 **Connection Refused**  发送连接, 连接被拒绝, 这种通常是发送请求的时候 服务端实例 **不可用** 了. 一般是发生在如下场景: 1. 服务上下线和升级, 造成实例重启. 在重启期间 会短暂有这种报错 2. 服务实例运行期间, 实例发生重启, 也会造成这种报错. > 发生这种报错, CSE 只有以上简单建议, 无法帮助客户 debug 看日志排查问题. 如果客户可以抽出demo 复现问题, 可以找CSE 支撑人员排查

# RPC Server 端支持使用 POSTMAN 直接调用 > 如果服务端 是使用 Java Chassis **RPC 风格开发的**, 如果想是用 `postman` 等工具直接调用时, 需要根据 swagger 契约查找 调用路径 ### 示例 ```java @RpcSchema(schemaId = "test") @SwaggerDefinition(basePath = "/pojo/rest") public class CodeFirstPojo { public Person sayHello(Person user) { user.setName("hello " + user.getName()); return user; } public String sayHi(String name) { return "hello " + name; } } ``` ### POSTMAN 调用 要想知道调用路径, 需要查看 **契约**. > 契约可以在 `日志` 中查看, 也可以在 `服务中心` 中查找. ```yaml swagger: "2.0" info: version: "1.0.0" title: "swagger definition for org.apache.servicecomb.demo.pojo.server.CodeFirstPojo" x-java-interface: "gen.swagger.CodeFirstPojoIntf" basePath: "/pojo/rest" schemes: - "http" consumes: - "application/json" produces: - "application/json" paths: /sayHello: post: operationId: "sayHello" parameters: - in: "body" name: "user" required: false schema: $ref: "#/definitions/Person" responses: "200": description: "response of 200" schema: $ref: "#/definitions/Person" /sayHi: post: operationId: "sayHi" parameters: - in: "body" name: "name" required: false schema: $ref: "#/definitions/sayHiBody" responses: "200": description: "response of 200" schema: type: "string" definitions: Person: type: "object" properties: name: type: "string" x-java-class: "org.apache.servicecomb.demo.compute.Person" sayHiBody: type: "object" properties: name: type: "string" ``` > 根据 `basePath` 和 `path` 进行拼接. 例如 我想调用 **sayHi()** 请求路径是 `/pojo/rest/sayHi` , 调用方法是 `post`  

SDK参考->C->上传对象，我如何去获取这个值？

# ServiceComb Java Chassis 如何自定义 rest 接口的 http status code 在使用 Java Chassis的时候, 有时我们需要自定义 调用返回的 状态码. 详情可参考 **[ServiceComb官方文档](https://docs.servicecomb.io/java-chassis/zh_CN/question-and-answer/faq/)** > 官方文档地址 : https://docs.servicecomb.io/java-chassis/zh_CN/question-and-answer/faq/ ### 设置正常调用自定义 HTTP 状态码 ```java @GetMapping("/userDefinedCode") public String userDefinedCode(@RequestParam(value = "code") int code) { InvocationContext invocationContext = ContextUtils.getInvocationContext(); invocationContext.setStatus(code); return "Set response code : " + code; } ```  ### 设置异常调用 HTTP 状态码 ```java @GetMapping("/throwException") public String testThrowException(@RequestParam(value = "code") int code) { InvocationContext invocationContext = ContextUtils.getInvocationContext(); throwException(code); return "Throw exception with status code :" + code; } public String throwException(int code) { if (code == 200) { return "Success with status code: 200"; } throw new InvocationException(code, "test exception code", "user defined error code"); } ``` 

../lib/libxml2.so.2: undefined reference to `fcntl64@GLIBC_2.28'collect2: error: ld returned 1 exit statusMakefile:22: recipe for target 'demo' failedmake: *** [demo] Error 1

集成华为VR播放器SDK，您的应用可以快速获取：巨幕影院：    在播放普通视频时，让您的用户置身于豪华影院之中，结合华为的实时烘托算法，提供更逼真的影院效果。360度全景视频：    极速起播、码率自适应，抗畸变，给您的用户更好的VR体验。8K FOV视频：    当前许多VR设备对8K视频解码能力不足，华为VR播放器SDK直击用户痛点，仅需4K解码能力即可提供8K视频解码和渲染。这些还不是华为VR播放器SDK的全部，更多功能正在路上。最新VR播放器试用版本已上架，欢迎下载试用：https://developer.huaweicloud.com/resource/video.html华为2020开发者大赛线上codelabs也提供了相关lab，欢迎体验：https://bbs.huaweicloud.com/forum/thread-44686-1-1.html