`IOException atomic move not supported` when using Coil with `com.android.tools:desugar_jdk_libs_nio:2.0.0`
See original GitHub issueI’m using Coil 2.2.2 and also use Android desugaring with com.android.tools:desugar_jdk_libs:2.0.0
and everything works fine.
If I change the desugaring library to com.android.tools:desugar_jdk_libs_nio:2.0.0
, every image load results in an IOException
with the message atomic move not supported
.
Not sure if this is an issue on the desugaring side or on Coil’s side.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
How to guarantee atomic move or exception of a file in Java?
The problem is that the option ATOMIC_MOVE is not considered in all cases, but the location of the source and target path is...
Read more >java.nio.file.AtomicMoveNotSupportedException ... - Tabnine
ATOMIC_MOVE) { throw new AtomicMoveNotSupportedException( source.toString(), target.toString(), "Google Cloud Storage does not support atomic move ...
Read more >Optional atomic move to support differing file systems #16
ATOMIC_MOVE produces an error: java.nio.file.AtomicMoveNotSupportedException: Atomic move between providers is not supported.
Read more >Files | Android Developers
Creates a new directory in the default temporary-file directory, using the given ... Consequently this method may not be atomic with respect to...
Read more >5.2. Use Files class to check, delete, copy or move a file or ...
Performs the move as an atomic file operation. If the file system does not support an atomic move, an exception is thrown. With...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Going to close this out since this is a bug with D8 and will be fixed in the next
desugar_jdk_libs
release.Filed an issue with the D8 team here since it seems like an issue with the desugared code.