Closed GoogleCodeExporter closed 8 years ago
Grrrr... lots of crazy things can happen with file systems I guess :) We should
probably add lots of exception handling in this area because some manufacturer
out there will probably find a way to break whatever we implement.
Original comment by kurtzm...@gmail.com
on 31 May 2011 at 6:16
See:
http://code.google.com/p/android/issues/detail?id=5807
http://code.google.com/p/android/issues/detail?id=4961
This is a known bug from a cache implementation in Android that was later
removed. The getCanonicalFile method should not throw this exception but it is
so we will catch this specific exception (we are already catching IOExceptions
which are expected).
Original comment by kurtzm...@gmail.com
on 3 Jun 2011 at 8:24
We also return "false" when we get an exception. We should err on the side of
caution and return true if we get an exception so that no further processing is
done on the directory.
Original comment by kurtzm...@gmail.com
on 3 Jun 2011 at 8:28
This issue was closed by revision r939.
Original comment by kurtzm...@gmail.com
on 3 Jun 2011 at 8:29
Original issue reported on code.google.com by
bobzill...@gmail.com
on 28 May 2011 at 6:20Attachments: