Autofill Framework is one of the things that should have resolved lots of issues regarding password managers or other apps that strive in simplifying the process of filling in the data for the user (https://www.xda-developers.com/android-os-autofill-framework-will-finally-resolve-a-long-standing-lag-issue-with-password-managers/). There were even threats by Google itself that apps who are not going to use Autofill Framework instead of Accessibility Service to fill in the data, are going to be kicked out from the Play Store (https://www.xda-developers.com/google-threatening-removal-accessibility-services-play-store/) . About the latter, I think Google went too far given that Autofill Framework being developed for almost two years still has massive issues, such as being able to kill any other Android app.
This framework is being adopted, but so far Autofill Framework does not cover pretty basic use cases. And there is not just not covering, but through Autofill Framework you can crash other apps. I have even created a ticket for that: https://issuetracker.google.com/u/0/issues/125158212 . In my GitHub repository, you can get the code which demonstrates how to use Autofill Framework to crash other Android apps: https://github.com/vaidotasstrazdas/autofill-crash-demo .
The idea is simple – simulation of dataset being no longer available which might happen due to lots of circumstances. For instance, user logs out, and another user logs in which does not have any data that previous user had. As you can see, use case is really valid, often occuring, but such use case crashes the app you want to autofill. Hopefully, Google will fix this bug, or provide another way to make sure this issue is resolved.