| SAF is not an option because it is HORRIBLY slow[1][2][3][4][5], which makes it an absolute no-go for any decent cloud synchronization app. Excerpt from [1]: > SAF is slow. Every SAF file IO operation takes like 20-30ms because it uses an IPC call. And sometimes you may want to check whether a lot of files exist on the disk and if they do not then create them (or something similar that requires a lot of file operations). It's so slow that even in google example they use hacks to make it faster. Excerpt from [3]: > Just to add a new sample for the performance of SAF vs standard File operations: > […] > 15 seconds with SAF, 6 milliseconds with native ls ! And there's only 128 files LOL ———————— [1] https://github.com/K1rakishou/Fuck-Storage-Access-Framework#... [2] https://www.reddit.com/r/androiddev/comments/ga5u72/saf_is_s... [3] https://issuetracker.google.com/issues/73044953#comment5 [4] https://magicbox.imejl.sk/forums/topic/storage-access-framew... [5] https://issuetracker.google.com/issues/130261278#comment52 |
> We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue (...)
It's all possible excuses all at once: "Thank you for your issue, we are working on it. Also we have no intention to work on it and we are closing it, the problem probably doesn't exist anymore anyways, and if you think it does make sure to open a new issue for us to treat it with the same amount of respect".