简体   繁体   English

OMAPI OpenLogicalChannel 在 Android 13 上失败

[英]OMAPI OpenLogicalChannel failed on Android 13

I work on application that communicate with a custom SIM card with use of Android OMAPI.我致力于使用 Android OMAPI 与自定义 SIM 卡通信的应用程序。 The application had worked, before I updated Google Pixel to Android 13. Since then, when openLogicalChannel of the Session is called, I get the exception below with scarce information:在我将 Google Pixel 更新为 Android 13 之前,该应用程序已经运行。从那时起,当调用SessionopenLogicalChannel时,我得到以下异常信息:

Caused by: java.io.IOException: OpenLogicalChannel() failed
        at android.se.omapi.Session.openLogicalChannel(Session.java:322)
        at android.se.omapi.Session.openLogicalChannel(Session.java:359)

I haven't found any information about OMAPI changes or additional permission in Androdid 13 documentation.我没有在 Android 13 文档中找到任何关于 OMAPI 更改或附加权限的信息。

isSecureElementPresent of Reader returns true. ReaderisSecureElementPresent返回 true。

Does anybody have any clues?有人有任何线索吗?

As you commented you are not using Android carrier privileges.正如您评论的那样,您没有使用 Android 运营商特权。 I'm wondering how this was ever working in your case.我想知道这在您的案例中是如何运作的。 In all my setups I needed it for accessing the SEService .在我所有的设置中,我都需要它来访问SEService The Access Control Enforcer was always checking the access properly in my Pixel devices. Access Control Enforcer 始终在我的 Pixel 设备中正确检查访问权限。 Was your previous Pixel device rooted before?您以前的 Pixel 设备之前是否已植根? Please try to add the hash of your signing certificate to the ARA or use a generic allow all rule.请尝试将您的签名证书的 hash 添加到 ARA 或使用通用的允许所有规则。 Maybe you can install this allow all applet on the SIM.也许你可以安装这个allow all applet on SIM。 For analyzing the APDU traffic I have written an XPosed module displaying additional log messages in the Android radio log.为了分析 APDU 流量,我编写了一个XPosed 模块,在 Android 无线电日志中显示额外的日志消息。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM