Currently, the behavior appears to be platform-specific. On Android, the shared PDF retains the original filename correctly, whereas on iOS the file is displayed as “attachment.pdf” when shared through the native iOS share sheet. This is commonly related to iOS share sheet behavior and how the file metadata is handled by the sharing plugin.

As per standard iOS limitations, many sharing plugins do not have full control over the filename shown in the share sheet. In most cases, iOS derives the filename from the temporary file or attachment metadata, which can result in generic names like “attachment.pdf”. Therefore, this is generally considered a limitation of the iOS sharing mechanism rather than Android behavior.

Most plugins do not provide a direct option to explicitly force the filename on iOS during sharing. A common workaround is to first save the PDF locally with the required filename in the device storage/temp directory and then share that exact file path instead of sharing raw binary/base64 content. In some cases, using a different sharing plugin or native iOS customization may also help preserve the original filename.