Filesystem.copy result contains .uri with trailing slash

[maximilianschmid]

Bug Report

7.1.1

💊   Capacitor Doctor  💊 

Latest Dependencies:

  @capacitor/cli: 7.4.0
  @capacitor/core: 7.4.0
  @capacitor/android: 7.4.0
  @capacitor/ios: 7.4.0

Installed Dependencies:

  @capacitor/cli: 7.4.0
  @capacitor/core: 7.4.0
  @capacitor/android: 7.4.0
  @capacitor/ios: 7.4.0

[success] iOS looking great! 👌
[success] Android looking great! 👌

Platform(s)

iOS 18.5

Current Behavior

const { uri } =  await Filesystem.copy({
    from: localUrl,
    to: `${$config.fileOpenerTmpFolder}/${unifiedFile.fileName}`,
    toDirectory: Directory.Cache,
  })

uri contains a file URI with a trailing slash

"file:///var/mobile/Containers/Data/Application/37A8504A-75DF-4273-BDEB-EC034F46F9FB/Library/Caches/file-opener/test.pdf/"

Expected Behavior

uri should contain a file URI without a trailing slash

"file:///var/mobile/Containers/Data/Application/37A8504A-75DF-4273-BDEB-EC034F46F9FB/Library/Caches/file-opener/test.pdf"

[maximilianschmid]

Update - additional info:

writeFileResult = await Filesystem.writeFile({
      path,
      data,
      directory,
      recursive: true,
    })

writeFileResult.uri also has trailing slash which is not wanted.

writeFileResult = await Filesystem.writeFile({
      path,
      data,
      directory,
      recursive: false,
    })

writeFileResult.uri also has no trailing slash which is the wanted result.

[maximilianschmid]

Version 7.0.1 works. Downgrade fixes the issue.

[reinos]

Same issue occurred in our installation:

"@capacitor/core": "^7.4.1",
"@capacitor/filesystem": "^7.1.2",

Example code:

const file = await Filesystem.writeFile({
      path: `our_app_cache_folder/${filename}`,
      directory: Directory.Cache,
      data: base64Data,
    });

The file.uri does have a trailing slash as mentioned in the issue.

I fixed it by not relying on the file response but instead fetching the cache path:

await Filesystem.writeFile({
      path: `our_app_cache_folder/${filename}`,
      directory: Directory.Cache,
      data: base64Data,
    });

    // fetch the path of the cache folder
    const basePath = await Filesystem.getUri({
      path: 'our_app_cache_folder',
      directory: Directory.Cache,
    });

    console.log(`${basePath.uri}${filename}`);

However, this is clearly a bug in the 7.x version.

[olivierschmid]

Same here. Trailing slash is added to uri since 7.1.x version when:

• Filesystem.writeFile
• Filesystem.copy

[OS-pedrogustavobilro]

Hey @maximilianschmid thanks for opening this issue. I remember we had fixed an issue with trailing slash recently, but it seems to have resurfaced or manifested itself differently.

Just to confirm - Even though the URI should not have the trailing slash, you are still able to use it correct? In other words, when you try to e.g. read the file, you won't receive an error?

[olivierschmid]

@OS-pedrogustavobilro Yes - it works (plugin writes / copy the file) - but we had to cut the slash otherwise the app did not work anymore. Problem is only on iOS

[maximilianschmid]

@OS-pedrogustavobilro Yes - it works (plugin writes / copy the file) - but we had to cut the slash otherwise the app did not work anymore. Problem is only on iOS

same here. Removing trailing slash from URI fixes the issue.

[freezzone]

Hey @maximilianschmid thanks for opening this issue. I remember we had fixed an issue with trailing slash recently, but it seems to have resurfaced or manifested itself differently.

Just to confirm - Even though the URI should not have the trailing slash, you are still able to use it correct? In other words, when you try to e.g. read the file, you won't receive an error?

For example appendFile doesn't work for us correctly when used with the trailing slash - it overwrites the existing file instead of appending the content to the existing file.

[maximilianschmid]

Hey @maximilianschmid thanks for opening this issue. I remember we had fixed an issue with trailing slash recently, but it seems to have resurfaced or manifested itself differently.
Just to confirm - Even though the URI should not have the trailing slash, you are still able to use it correct? In other words, when you try to e.g. read the file, you won't receive an error?

For example appendFile doesn't work correctly when used with the trailing slash - it overwrites the existing file instead of appending the content to the existing file.

@freezzone we do not use appendFile so cannot comment on that one.

[freezzone]

Hey @maximilianschmid thanks for opening this issue. I remember we had fixed an issue with trailing slash recently, but it seems to have resurfaced or manifested itself differently.
Just to confirm - Even though the URI should not have the trailing slash, you are still able to use it correct? In other words, when you try to e.g. read the file, you won't receive an error?

For example appendFile doesn't work correctly when used with the trailing slash - it overwrites the existing file instead of appending the content to the existing file.

@freezzone we do not use appendFile so cannot comment on that one.

I meant that appendFile doesn't work in our application, when used together with the trailing slash produced by getUri.

[mszkwsk]

Hey!

I will abuse the opportunity that this issue is still open. It seems that trialing / is not only an issue for Filesystem.copy.

We are building an iOS app with Capacitor. We recently updated to the latest version and that is when we discovered the issue. We have been using Filesystem.writeFile and inside the returned object, value of uri property will also contain the trailing /.

This resulted in error when trying to invoke Filesystem.stats with the URI stored in returned object from Filesystem.writeFile. I know that calling Filesystem.stats right after Filesystem.writeFile might not be the real world scenario, but I used it to narrow down issue to being this plugin related.

const writeResult = await Filesystem.writeFile({
   path: fileName,
   data: fileData,
   directory: Directory.Documents,
});
  
// this will throw an error that the file does not exist.
const stats = await Filesystem.stat({
 path: writeResult.uri,
  directory: Directory.Documents,
})

Now, I have checked version 7.0.1 and the problem is not there. The problem for sure does exist on 7.1.2 and 7.1.3.

[OS-pedrogustavobilro]

PR open at - #20

Until this gets merged and released, feel free to test with this dev version - @capacitor/filesystem@7.1.4-dev.31jul2025