Jay Chou

不支持 org.gradle.unsafe.configuration-cache=true

3

* Exception is: org.gradle.configurationcache.ConfigurationCacheProblemsException: Configuration cache problems found in this build. 1 problem was found storing the configuration cache. - Plugin 'xml-class-guard': read system property 'user.dir' See https://docs.gradle.org/7.2/userguide/configuration_cache.html#config_cache:requirements:undeclared_sys_prop_read 官网建议是 To...

子module依赖的远程aar并没有被打包进来

7

子module依赖的远程aar并没有被打包进来，已经在主library中embd该子module，结果还是一样

每个module都要加apply plugin: 'com.kezong.fat-aar'吗？

2

每个有依赖其他module的moudle，都要在build.gradle加apply plugin: 'com.kezong.fat-aar'吗？

异常类型：Cannot invoke "org.gradle.api.Project.getBuildDir()" because "this.project" is null matrix版本：2.0.8 gradle版本：AGP 7.4.2, gradle 7.6.3 问题描述：修改代码后再次编译，大概率报 Cannot invoke "org.gradle.api.Project.getBuildDir()" because "this.project" is null 堆栈/日志： ``` Execution failed for task ':app:transformClassesWithMatrixTraceTransformForDebug'. > Cannot invoke...

升级到 v2.1.0 版本后，监控返回的帧率明显变低了

2

异常类型：监控返回的帧率明显变低了 手机型号：无关 手机系统版本：无关 matrix版本：2.10.0 问题描述： 同样的场景（和代码，仅 matrix 版本不同），FPS 从 60 下降到 40 以下，而且数据上报统计显示整个大盘的 FPS 都降低了（说明与设备或系统版本无关） 而通过其他性能采集工具（如火山）发现，实际 FPS 并没有降低，怀疑是 v2.1.0 版本的 bug，希望作者抽空帮忙看看，谢谢！ 通过 onReportIssue 回调接口 v2.0.8 版本打印如下issue=tag[Trace_FPS]type[0];key[null];content[{"machine":"MIDDLE","cpu_app":0,"mem":3753299968,"mem_free":1159304,"scene":"xxx.xxx.xxx","dropLevel":{"DROPPED_FROZEN":0,"DROPPED_HIGH":0,"DROPPED_MIDDLE":0,"DROPPED_NORMAL":1,"DROPPED_BEST":742},"dropSum":{"DROPPED_FROZEN":0,"DROPPED_HIGH":0,"DROPPED_MIDDLE":0,"DROPPED_NORMAL":3,"DROPPED_BEST":4},"fps":60,"tag":"Trace_FPS","process":"xxx.xxx.xxx","time":1685088286163}] v2.1.0 版本打印如下 issue=tag[Trace_FPS]type[0];key[null];content[{"machine":"MIDDLE","cpu_app":0,"mem":3753299968,"mem_free":1220116,"scene":"xxx.xxx.xxx","dropLevel":{"DROPPED_BEST":593,"DROPPED_NORMAL":3,"DROPPED_MIDDLE":0,"DROPPED_HIGH":0,"DROPPED_FROZEN":0},"dropSum":{"DROPPED_BEST":258,"DROPPED_NORMAL":11,"DROPPED_MIDDLE":0,"DROPPED_HIGH":0,"DROPPED_FROZEN":0},"fps":39.21251678466797,"UNKNOWN_DELAY_DURATION":1377531,"INPUT_HANDLING_DURATION":2399,"ANIMATION_DURATION":905243,"LAYOUT_MEASURE_DURATION":307483,"DRAW_DURATION":991190,"SYNC_DURATION":729489,"COMMAND_ISSUE_DURATION":11868509,"SWAP_BUFFERS_DURATION":1382197,"TOTAL_DURATION":25069426,"GPU_DURATION":6250504,"DROP_COUNT":1,"REFRESH_RATE":60,"tag":"Trace_FPS","process":"xxx.xxx.xxx","time":1685088456120}]

参考： https://github.com/bytedance/AlphaPlayer/issues/23 https://vites.app/article/dev/763e0905.html

Memory leak may happen

2

If we reference viewBinding again in onDestroyView, this will trigger ViewBindingProperty#getValue, which will inflate another view if cache is null. example here: ``` class PersonListFragment : Fragment(R.layout.fragment_person_list) { // Without...