- 小程序硬件框架从体验版切换为开发版的情况下,小程序会出现白屏?
设备端应用启动小程序,第三个参数为体验版可以正常启动,第三个参数为开发版的情况下就会白屏 完整日志内容在链接里 WMPFStartAppParams params = new WMPFStartAppParams("XXXXXXXXXX", path, WMPFStartAppParams.WMPFAppType.APP_TYPE_DEV); WMPF.getInstance().getMiniProgramApi().launchMiniProgram(params); [图片] https://vs-care.oss-cn-shenzhen.aliyuncs.com/vs-care/log.txt
04-24 - 体验版小程序扫码界面,未扫码点击返回回到我们自己的应用会出现闪退?
完整日志如下,操作过程,体验版小程序,在需要扫码登录的界面,不扫码直接点击返回,会导致应用闪退,截图和完整日志如下,请问该如何避免 [图片] 2024-04-22 11:35:06.133 341-341 libperfmgr and...power.aidl-service.droidlogic I Do Powerhint: INTERACTION 2024-04-22 11:35:06.133 516-681 WindowManager system_server E press keyCode: 4 2024-04-22 11:35:06.134 2480-2480 SogouIME com.sohu.inputmethod.sogou.tv I onKeyUp: keyoCode=4 2024-04-22 11:35:06.134 2480-2480 DefaultIMS com.sohu.inputmethod.sogou.tv I onKeyUp: keyoCode=4 2024-04-22 11:35:06.141 374-415 PermissionCache surfaceflinger D checking android.permission.READ_FRAME_BUFFER for uid=1000 => granted (167 us) 2024-04-22 11:35:06.175 516-1539 ActivityTaskManager system_server W Finishing task with all activities already finished 2024-04-22 11:35:06.175 516-1539 ActivityTaskManager system_server W Duplicate finish request for r=ActivityRecord{b1ad045 u0 com.tencent.wmpf/.wakeup.WMPFWakeUpInvokeActivity t172 f}} 2024-04-22 11:35:06.181 516-1056 WindowManager system_server V force to landscape 2024-04-22 11:35:06.182 215-215 hwservicemanager hwservicemanager I getTransport: Cannot find entry android.hardware.configstore@1.0::ISurfaceFlingerConfigs/default in either framework or device manifest. 2024-04-22 11:35:06.192 1450-2271 [ui]AppFor...undWatcher com.vs.eldertv I 2/app on foreground 2024-04-22 11:35:06.196 1450-2271 [ui]LocalAgent com.vs.eldertv I 2/sender = android.os.Messenger@712dd3a 2024-04-22 11:35:06.203 2282-2433 [push]core com.vs.eldertv I 2/app on foreground 2024-04-22 11:35:06.218 1450-2908 WMPFCli.IPCInvoker com.vs.eldertv I invokeSync <<<< response [AbstractWMPFSyncInvokeResponse{errCode=-11, errMsg='cancel', errType=1}] rId [11] 2024-04-22 11:35:06.220 374-415 BufferQueueProducer surfaceflinger E [com.tencent.wmpf/com.tencent.wmpf.wakeup.WMPFWakeUpInvokeActivity#0](id:1760000000c,api:0,p:-1,c:374) disconnect: not connected (req=1) 2024-04-22 11:35:06.221 2502-2918 libEGL com.tencent.wmpf W EGLNativeWindowType 0xf24c9738 disconnect failed 2024-04-22 11:35:06.223 1450-1450 ContactCallActivity com.vs.eldertv E 81 requestFocus:false 2024-04-22 11:35:06.228 2282-2433 [push]core com.vs.eldertv D 2/checkLinkStateShouldReLogin: SDKState=LOGINED,reconnectTimer=null,reconnectCount=0,deltaTime=21549,shouldRelogin=false 2024-04-22 11:35:06.249 2282-2433 [push]core com.vs.eldertv I 2/force check heart... 2024-04-22 11:35:06.258 1450-2271 [ui]LocalAgent com.vs.eldertv I 2/sendAppStatus isAppOnForeground:true sent:true 2024-04-22 11:35:06.265 2282-2433 [push]core com.vs.eldertv I 196/send PacketHeader [SID 1 , CID 2 , SER 0 , RES 200 , TAG 0 , LEN 5] --------- beginning of crash 2024-04-22 11:35:06.266 2480-2480 DefaultIMS com.sohu.inputmethod.sogou.tv I onStartInput attribute=android.view.inputmethod.EditorInfo@37760bf restarting=false inputType: 0 2024-04-22 11:35:06.267 1450-2908 AndroidRuntime com.vs.eldertv E FATAL EXCEPTION: pool-6-thread-1 Process: com.vs.eldertv, PID: 1450 java.lang.RuntimeException: com.tencent.wmpf.cli.api.WMPFApiException: errType: 1, errCode: -11, errMsg: cancel at com.vs.eldertv.activity.ContactListActivity$3.run(ContactListActivity.java:210) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:923) Caused by: com.tencent.wmpf.cli.api.WMPFApiException: errType: 1, errCode: -11, errMsg: cancel at com.tencent.wmpf.cli.task.pb.WMPFIPCInvoker.invokeSync(WMPFIPCInvoker.java:170) at com.tencent.wmpf.cli.task.pb.AbstractWMPFSyncInvokeRequest.call(AbstractWMPFSyncInvokeRequest.java:94) at com.tencent.wmpf.cli.api.WMPFAccountApi.login(WMPFAccountApi.java:36) at com.vs.eldertv.activity.ContactListActivity.launchMiniProgram(ContactListActivity.java:231) at com.vs.eldertv.activity.ContactListActivity.access$400(ContactListActivity.java:61) at com.vs.eldertv.activity.ContactListActivity$3.run(ContactListActivity.java:208) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:923) 2024-04-22 11:35:06.275 2282-2433 [push]core com.vs.eldertv I 196/send PacketHeader [SID 3 , CID 2 , SER 1007 , RES 200 , TAG 0 , LEN 10] 2024-04-22 11:35:06.279 1450-2271 [ui]core com.vs.eldertv I 2/add send task: Request [SID 3 , CID 2] 2024-04-22 11:35:06.280 2282-2433 [push]core com.vs.eldertv V 196/received packetSize: 8, readableBytes: 4 2024-04-22 11:35:06.280 2282-2433 [push]core com.vs.eldertv I 196/received PacketHeader [SID 1 , CID 2 , SER 0 , RES 200 , TAG 2 , LEN 7] 2024-04-22 11:35:06.287 2282-2433 [push]core com.vs.eldertv V 196/received packetSize: 8, readableBytes: 4 2024-04-22 11:35:06.292 2282-2433 [push]core com.vs.eldertv I 196/received PacketHeader [SID 3 , CID 2 , SER 1007 , RES 200 , TAG 2 , LEN 7] 2024-04-22 11:35:06.296 1450-2271 [ui]core com.vs.eldertv I 2/pend task: Request [SID 3 , CID 2] 2024-04-22 11:35:06.181 516-1056 chatty system_server I uid=1000(system) Binder:516_8 identical 1 line 2024-04-22 11:35:06.191 516-1056 WindowManager system_server V force to landscape
04-22 - 设备使用小程序硬件框架的找不到camera会崩溃?
在测试的时候发现,频繁的操作会出现闪退的情况,抓取日志看到如下内容,想问下这个方法和是做了什么,如何避免此情况引发的系统崩溃 在日志中发现,即日志标记的后面约30行有个调用com.tencent.mars相关内容,想问下这是在哪个地方,在这里做了什么操作,因为在aar里面未发现这个命名空间 [图片][图片] XLOG链接 https://micro-api.elifestrong.com/admin/sys-file/local/07006e21ea6743d7b935d2236f939e6d.zip 本地抓取的logcat https://micro-api.elifestrong.com/admin/sys-file/local/07006e21ea6743d7b935d2236f939e6d.zip
04-12 - 在启动VIOP的时候,会出现导致系统崩溃重启的问题,腾讯XLOG和logcat放在正文,如何解决?
XLOG链接 https://micro-api.elifestrong.com/admin/sys-file/local/07006e21ea6743d7b935d2236f939e6d.zip 本地抓取的logcat https://micro-api.elifestrong.com/admin/sys-file/local/07006e21ea6743d7b935d2236f939e6d.zip 搜索内容 fatal,报错日志内容和大致位置如下 [图片]
04-09 - 设备拨打小程序,设备端吊起通话之后,小程序未接听/挂断,3S后小程序自动挂断,这是什么问题?
1.设备箱小程序拨打音视频通话,微信小程序出现接听、挂断的页面,然后不操作微信小程序,等待约3秒后自动挂断,完整的日志文件在XLog里面 https://micro-api.elifestrong.com/admin/sys-file/local/6435cf5c37c34195bf8c45ad69700882.zip
04-08 - 从RPMBD方式转换为tee认证方式之后出现了如下问题?
1.使用rpmbd方式认证成功并且完成通话,但是我们的系统需要在rpmdb分区中写入key以保证系统运行的稳定性 2.修改为tee方式认证后,在没有烧录我们的key的情况下是可以正常进行通话的,但是有一台盒子为了做验证,烧录进我们的key以后,在registerMiniProgramDevice的时候就出现了如下的日志 [图片] 请问,腾讯在读取这个分区key的时候是只读自己写入的 还是会读所有的内容?下图是我们用adb shell命令读取的rpmbd分区下的内容 [图片]
03-11 - 设备端向小程序拨打音视频通话的时候页面白屏?
[图片] 1,微信框架小程序(TV端)退出登录 2,扫码登录成功 3,呼叫小程序(有概率会白屏) 4,重启几次 5,退出登录,再次扫码登录成功 6,就出现页面不存在 设备端日志如下 2024-01-29 16:54:40.010 1372-2729 ContactCallActivity com.vs.eldertv E 163 path:plugin-private://wxf830863afde621eb/pages/call-page-plugin/call-page-plugin?sn=hc18096a0244261112c&showName=15347325284&callOpenId=oRqK-6wk628vjk7Q0HJOZ9lFoPO8&roomType=video&miniprogramState=1&isPreLaunch=1&callSeq=261b6d43-3831-4d3d-a12d-002f091c7d2a&userId=1727905538554978306&tvUserId=1744301634894151681 2024-01-29 16:54:40.011 1372-2729 WMPFCli.IPCInvoker com.vs.eldertv I invokeSync >>>> request [IS_DEVICE_ACTIVATED] [AbstractWMPFSyncInvokeRequest{clientVersion=0, clientApplicationId='null', clientInvokeToken='null', invokeTimestamp=-1, clientProcessName='null'}] rId [20] 2024-01-29 16:54:40.013 1372-2113 IPC.IPCBridgeManager com.vs.eldertv I [getIPCBridge] tid=[140] com.vs.eldertv -> com.tencent.wmpf 2024-01-29 16:54:40.014 1372-2113 IPC.IPCBridgeManager com.vs.eldertv I [getIPCBridge] bw:263834236, id:643006263305, process:com.tencent.wmpf pingBinder:true 2024-01-29 16:54:40.016 1372-2113 IPC.ObjectRecycler com.vs.eldertv I addIntoSet(com.tencent.wmpf) 2024-01-29 16:54:40.016 1372-2113 IPC.IPCInv...ackWrapper com.vs.eldertv I keep ref of callback(156181725) 2024-01-29 16:54:40.024 1372-2729 WMPFCli.IPCInvoker com.vs.eldertv I invokeSync <<<< response [WMPFIsDeviceActivatedResponse{isActivated=true}] rId [20] 2024-01-29 16:54:40.024 1372-2729 WMPFCli.Device com.vs.eldertv I activated. just return 2024-01-29 16:54:40.024 1372-2729 WMPFCli.IPCInvoker com.vs.eldertv I invokeSync >>>> request [AUTHORIZE_STATUS] [AbstractWMPFSyncInvokeRequest{clientVersion=0, clientApplicationId='null', clientInvokeToken='null', invokeTimestamp=-1, clientProcessName='null'}] rId [21] 2024-01-29 16:54:40.026 1372-2235 IPC.IPCBridgeManager com.vs.eldertv I [getIPCBridge] tid=[157] com.vs.eldertv -> com.tencent.wmpf 2024-01-29 16:54:40.027 1372-2235 IPC.IPCBridgeManager com.vs.eldertv I [getIPCBridge] bw:263834236, id:643019643014, process:com.tencent.wmpf pingBinder:true 2024-01-29 16:54:40.028 1372-2235 IPC.ObjectRecycler com.vs.eldertv I addIntoSet(com.tencent.wmpf) 2024-01-29 16:54:40.028 1372-2235 IPC.IPCInv...ackWrapper com.vs.eldertv I keep ref of callback(257500963) 2024-01-29 16:54:40.036 1372-2729 WMPFCli.IPCInvoker com.vs.eldertv I invokeSync <<<< response [AbstractWMPFSyncInvokeResponse{errCode=0, errMsg='ok', errType=0}] rId [21] 2024-01-29 16:54:40.037 1372-2729 WMPFCli.IPCInvoker com.vs.eldertv I invokeSync >>>> request [IS_DEVICE_ACTIVATED] [AbstractWMPFSyncInvokeRequest{clientVersion=0, clientApplicationId='null', clientInvokeToken='null', invokeTimestamp=-1, clientProcessName='null'}] rId [22] 2024-01-29 16:54:40.039 1372-2237 IPC.IPCBridgeManager com.vs.eldertv I [getIPCBridge] tid=[158] com.vs.eldertv -> com.tencent.wmpf 2024-01-29 16:54:40.040 1372-2237 IPC.IPCBridgeManager com.vs.eldertv I [getIPCBridge] bw:263834236, id:643032578930, process:com.tencent.wmpf pingBinder:true 2024-01-29 16:54:40.040 1372-2237 IPC.ObjectRecycler com.vs.eldertv I addIntoSet(com.tencent.wmpf) 2024-01-29 16:54:40.041 1372-2237 IPC.IPCInv...ackWrapper com.vs.eldertv I keep ref of callback(186528217) 2024-01-29 16:54:40.047 1372-2729 WMPFCli.IPCInvoker com.vs.eldertv I invokeSync <<<< response [WMPFIsDeviceActivatedResponse{isActivated=true}] rId [22] 2024-01-29 16:54:40.047 1372-2729 WMPFCli.Device com.vs.eldertv I activated. just return 2024-01-29 16:54:40.048 1372-2729 WMPFCli.IPCInvoker com.vs.eldertv I invokeSync >>>> request [START_APP] [WMPFStartAppRequest{params=WMPFStartAppParams{appId='wx302fdaf7bf0df089', path='plugin-private://wxf830863afde621eb/pages/call-page-plugin/call-page-plugin?sn=hc18096a0244261112c&showName=15347325284&callOpenId=oRqK-6wk628vjk7Q0HJOZ9lFoPO8&roomType=video&miniprogramState=1&isPreLaunch=1&callSeq=261b6d43-3831-4d3d-a12d-002f091c7d2a&userId=1727905538554978306&tvUserId=1744301634894151681', appType=APP_TYPE_DEV}, forceFullScreen=false, landscapeMode=NORMAL, displayId=0, enterPictureInPicture=false}] rId [23] 2024-01-29 16:54:40.049 1372-2113 IPC.IPCBridgeManager com.vs.eldertv I [getIPCBridge] tid=[140] com.vs.eldertv -> com.tencent.wmpf 2024-01-29 16:54:40.051 1372-2113 IPC.IPCBridgeManager com.vs.eldertv I [getIPCBridge] bw:263834236, id:643042815930, process:com.tencent.wmpf pingBinder:true 2024-01-29 16:54:40.052 1372-2113 IPC.ObjectRecycler com.vs.eldertv I addIntoSet(com.tencent.wmpf) 2024-01-29 16:54:40.053 1372-2113 IPC.IPCInv...ackWrapper com.vs.eldertv I keep ref of callback(177017471) 2024-01-29 16:54:40.063 1372-2729 WMPFCli.IPCInvoker com.vs.eldertv I invokeSync <<<< response [AbstractWMPFSyncInvokeResponse{errCode=0, errMsg='ok', errType=0}] rId [23] 2024-01-29 16:54:40.122 1968-2038 [push]JobCore com.vs.eldertv I 2/onStartJob 1 2024-01-29 16:54:40.154 1968-2038 [push]JobCore com.vs.eldertv I 2/onStartJob 0 2024-01-29 16:54:40.162 1372-1416 IPC.BaseIPCService com.vs.eldertv I invokeAsync in target process, before ThreadPool.post, clazz=com.tencent.wmpf.cli.event.WMPFClientEventHandlerHub$WMPFClientReceiver 2024-01-29 16:54:40.162 1372-2235 IPC.IPCInv...lbackProxy com.vs.eldertv I keep ref of callback(240811946) 2024-01-29 16:54:40.529 365-1100 BufferQueueProducer surfaceflinger E [com.vs.eldertv/com.vs.eldertv.activity.ContactListActivity#0](id:16d00000012,api:0,p:-1,c:365) disconnect: not connected (req=1) 2024-01-29 16:54:40.529 1372-2034 libEGL com.vs.eldertv W EGLNativeWindowType 0xe49cb068 disconnect failed 2024-01-29 16:54:40.597 1372-1961 [ui]AppFor...undWatcher com.vs.eldertv I 2/app in background 2024-01-29 16:54:40.615 1372-1961 [ui]LocalAgent com.vs.eldertv I 2/sender = android.os.Messenger@2f32fee 2024-01-29 16:54:40.617 1968-2038 [push]core com.vs.eldertv I 2/app in background 2024-01-29 16:54:40.622 1372-1961 [ui]LocalAgent com.vs.eldertv I 2/sendAppStatus isAppOnForeground:false sent:true 2024-01-29 16:54:40.626 1372-1961 [ui]core com.vs.eldertv I 2/add send task: Request [SID 3 , CID 2] 2024-01-29 16:54:40.627 1968-2038 [push]core com.vs.eldertv I 193/send PacketHeader [SID 3 , CID 2 , SER 1017 , RES 200 , TAG 0 , LEN 10] 2024-01-29 16:54:40.629 1372-1961 [ui]core com.vs.eldertv I 2/pend task: Request [SID 3 , CID 2] 2024-01-29 16:54:40.632 1372-1961 [ui]LocalAgent com.vs.eldertv I 2/sender = android.os.Messenger@2f32fee 2024-01-29 16:54:40.642 1372-1961 [ui]ui com.vs.eldertv I 161/current unread: 0 comes from {} 2024-01-29 16:54:40.663 1968-2038 [push]core com.vs.eldertv V 193/received packetSize: 8, readableBytes: 4 2024-01-29 16:54:40.665 1968-2038 [push]core com.vs.eldertv I 193/received PacketHeader [SID 3 , CID 2 , SER 1017 , RES 200 , TAG 2 , LEN 7] 2024-01-29 16:54:40.677 1372-1961 [ui]core com.vs.eldertv V 99/handle packet: PacketHeader [SID 3 , CID 2 , SER 1017 , RES 200 , TAG 2 , LEN 7] 2024-01-29 16:54:41.518 1372-2175 Coap com.vs.eldertv D thread_routine, loop count=1900 2024-01-29 16:54:45.134 1372-1486 com.vs.eldertv com.vs.eldertv W Couldn't lock the profile file /data/user/0/com.vs.eldertv/files/iflytek/idata/cache/oat/386cf139a9d1423b99384319bb9c3b45.zip.cur.prof: Failed to open file '/data/user/0/com.vs.eldertv/files/iflytek/idata/cache/oat/386cf139a9d1423b99384319bb9c3b45.zip.cur.prof': No such file or directory 2024-01-29 16:54:45.134 1372-1486 com.vs.eldertv com.vs.eldertv W Could not forcefully load profile /data/user/0/com.vs.eldertv/files/iflytek/idata/cache/oat/386cf139a9d1423b99384319bb9c3b45.zip.cur.prof
01-29 - 设备端呼叫小程序,在HC1退出小程序依旧能呼叫通话,详情请看附件?
1.设备拨打小程序,在房间还未创建成功的时候通过右上角关闭小程序,然后呼叫申请未中断,仍然拨通了小程序端,此时应该如何处理,避免这种情况出现? [图片] [图片]
01-29 - 小程序硬件框架清除数据后出现奇怪的问题?
一开始 设备端呼叫小程序 小程序呼叫设备端 双向通信都是正常的 此时在系统 设置里面 清理小程序硬件框架如图进行操作 [图片] 然后再次扫码登录之后,设备端无法呼出 也无法接到呼入的请求,页面是这样的效果,请问这个问题该如何排查? [图片]
01-24 - WMPF2.2.0使用VIOP通话的时候报错说 get voipToken error?
看文档里说,使用WMPF注册设备的话,在使用viop视频通话的时候是不需要传viopToken的,在设备A上是可以拨打小程序的,后面又搞了一个设备B,在设备B上运行相同的应用,没有修改代码的情况下拨通音视频通话报这个错 [图片]
01-11