Expanding user136964's answer, when you try to send a file from Drive, the URI (i.e path) of the file is passed to the app in this format:

content://com.google.android.apps.docs.storage.legacy/hashed_name

Take note that it's not a direct path to the file (not file://root/folder/file.ext), but a path to content provider. A resource inside content provider cannot be accessed directly, and any apps have to manually handle the given path according to its structure to get the resource (or in this case, the file).

ES File Explorer doesn't handle content:// URI, and thus fails to get the real file.

^{WhatsApp and Terminal Emulator also fail to handle it. On the other hand, Yahoo Mail and Google Inbox handle it properly and attach the real file without any problem}

Expanding user136964's answer, when you try to send a file from Drive, the URI (i.e path) of the file is passed to the app in this format:

content://com.google.android.apps.docs.storage.legacy/hashed_name

Take note that it's not a direct path to the file (not file://root/folder/file.ext), but a path to content provider. A resource inside content provider cannot be accessed directly, and any apps have to manually handle the given path according to its structure to get the resource (or in this case, the file).

ES File Explorer doesn't handle content:// URI, and thus fails to get the real file.

^{WhatsApp and Terminal Emulator also fail to handle it. On the other hand, Yahoo Mail and Google Inbox handle it properly and attach the real file without any problem}