AdevintaSpain / AdevintaSpain/Barista
java.lang.SecurityException: Calling from not trusted UID! with 4.1.0 and + version
- 主要語言
- Kotlin
- 星號
- 1.7k
- 分支
- 119
- PR 合併指標
- 30 天內沒有已合併 PR
描述
**Library Version:**
4.1.0 and 4.2.0
**Describe the Bug:**
After the project is successfully compiled, running tests fails on the first test case. The stack trace doesn't show a crash, but by digging through the stack trace, I found some usable things, mainly related to the issue mentioned in the title. Rolling the project back to 4.0.0 fixes the issue, and I can run tests properly. This issue is not device dependent on my side since tests fail on real devices and multiple emulators.
**Stacktrace**
```
1-08 19:29:05.865 18316 18329 W Binder : Caught a RuntimeException from the binder stub implementation.
11-08 19:29:05.865 18316 18329 W Binder : java.lang.SecurityException: Calling from not trusted UID!
11-08 19:29:05.865 18316 18329 W Binder : at android.app.UiAutomationConnection.throwIfCalledByNotTrustedUidLocked(UiAutomationConnection.java:525)
11-08 19:29:05.865 18316 18329 W Binder : at android.app.UiAutomationConnection.shutdown(UiAutomationConnection.java:429)
11-08 19:29:05.865 18316 18329 W Binder : at android.app.IUiAutomationConnection$Stub.onTransact(IUiAutomationConnection.java:390)
11-08 19:29:05.865 18316 18329 W Binder : at android.os.Binder.execTransactInternal(Binder.java:1159)
11-08 19:29:05.865 18316 18329 W Binder : at android.os.Binder.execTransact(Binder.java:1123)
```
貢獻指南
研究方向
Reproduce the first-test failure with Barista 4.1.0 and 4.2.0, then compare it with 4.0.0, where the tests pass. Start with the Android UiAutomationConnection.shutdown stack trace and verify the behavior on real devices and multiple emulators. Done means identifying the regression and confirming that the test suite runs without the SecurityException.
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- android, kotlin
- 領域
- mobile-dev, testing
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 需要釐清
- 新手友好度
- 30/100