Hi! I am having an issue with accessibility, since...
# compose-android
e
Hi! I am having an issue with accessibility, since 1.9.0 version. I know that there are braking changes on graphicsLayer, but even if I remove all direct applications of graphicsLayer, entire app is just broken. Accessibility is not working. Not sure where to even dig for a way out 😄
k
This needs more info on how your app hierarchy is structured. Is it all one big canvas with direct drawing? Is it using any higher level Compose blocks like box, row or column? Is it using any higher level Material components like buttons, checkboxes, etc?
e
I am not sure where to even start… this is quite complex app, with loads of custom elements, plenty of animations and what not.
App with around 100 different views, quite sophisticated navigation structures… you name it, it is there. I have bent my brain around this issue, and the problem of pinpointing possible culprit. Accessibility tree is broken and that is it. I thought maybe some “typical” places are already know.
k
Start fresh with a skeleton app, but same dependencies to rule out the more basic things
s
You can also modify your Compose dependency to
1.9.0-alpha01
,
alpha02
, etc until you find which update introduced your breaking changes. Then you can read the release notes for that particular release and view the associated diffs.
Copy code
<https://developer.android.com/jetpack/androidx/releases/compose-runtime#version_19_2>
You've got a handful of published subversions to test, would be pretty quick to do a binary search
e
1.9.0 introduced this, well known braking changes. But that is not the point.
By knowing the version I will not fix this issue. That is not a bug in the library, but new reality
s
Understanding the library and its changes can help you fix your app 🙏
e
I do understand the changes quite well. There are 1001 places where these changes can break stuff.