SFtpFile React Native Reference Documentation

SFtpFile

Current Version: 11.6.1

Chilkat.SFtpFile

Inspect metadata for a file, directory, symlink, or special item in an SFTP listing.

Chilkat.SFtpFile represents one entry returned from an SFTP directory listing. It exposes the entry name, file type, size, ownership, permissions, timestamps, and server-provided attribute flags such as hidden, read-only, archive, immutable, encrypted, compressed, sparse, append-only, system, and synchronization status. It is typically used together with Chilkat.SFtpDir when iterating a remote directory and deciding how each entry should be displayed, filtered, downloaded, skipped, or processed.

Name and type

Read Filename and FileType, or use convenience flags such as IsRegular, IsDirectory, and IsSymLink.

File sizes

Access the entry size as a 32-bit integer, 64-bit integer, or decimal string using Size32, Size64, or SizeStr.

Timestamps

Inspect creation, last-access, and last-modified times as date/time values or RFC822-formatted strings when supported by the server.

Ownership

Read numeric user and group IDs, and when the server supports it, textual owner and group names.

Permissions

Inspect the POSIX-style permissions bit mask for read, write, execute, set-user-ID, set-group-ID, and sticky-bit information.

Extended attributes

Check server-provided flags such as hidden, read-only, archive, immutable, encrypted, compressed, sparse, append-only, system, and sync.

Common pattern: Retrieve a directory listing with Chilkat.SFtp, iterate its Chilkat.SFtpDir entries, and populate a Chilkat.SFtpFile object for each item. Use the file type, timestamps, size, permissions, and attribute flags to decide whether the entry is a regular file, directory, symlink, or special item and how the application should handle it.
Server-version note: Some metadata is only available from newer SFTP protocol versions. For example, textual owner/group information and creation time require SFTP v4 or later, while many extended attribute flags such as read-only, archive, immutable, compressed, encrypted, sparse, append-only, and system require SFTP v6 or later.

Object Creation

// npm install @chilkat/react-native react-native-nitro-modules
// (React Native 0.76+ with the New Architecture; then `pod install` for iOS.  The Chilkat
//  native library is downloaded and verified during the native build -- see the package README.)

import { Chilkat, SFtpFile } from '@chilkat/react-native'

// Once per app start, before any other Chilkat call:
Chilkat.unlockBundle('Anything for 30-day trial')   // shorthand for new Global().unlockBundle(..)

const sFtpFile = new SFtpFile()
// ... the native object is released when `sFtpFile` is garbage collected, or now with sFtpFile.dispose()
new SFtpFile()

Creates the underlying native Chilkat object. SFtpFile is a Nitro Module HybridObject: use it from the JavaScript thread only (it cannot be passed to a Worklet or another runtime). Every member is synchronous and blocks the JavaScript thread until Chilkat returns; a method that can take a while also exists as a ...Async twin returning a Promise, which runs the same call on a native worker thread so the UI keeps rendering. While such a call is pending, every other call on this object throws, except abort() and assigning onPercentDone / onProgressInfo.

dispose(): void

Releases the native object immediately instead of waiting for garbage collection (useful for a large BinData or an open socket). Calling it more than once is harmless; any other use of the object afterwards throws. An object with a pending ...Async call cannot be disposed until the promise settles.

Errors

A method that can fail throws a plain Error: a method whose only outcome is success or failure returns void and throws on failure; a method producing a string or an object returns it and throws where Chilkat would have returned null. The error's message is "Class.method(...): reason", where the reason is the last informative line of the object's lastErrorText, which holds the full Chilkat log of the failed call. A ...Async twin rejects its promise with the same Error instead of throwing. Properties never throw, and methods that answer a question (has..., is..., ...) return a plain boolean.

try {
  sFtpFile.someMethod(...)
} catch (e) {
  console.log((e as Error).message)   // SFtpFile.someMethod(...): <reason>
  console.log(sFtpFile.lastErrorText)   // the full Chilkat log of the failed call
}

// The same call without blocking the JavaScript thread:
try {
  await sFtpFile.someMethodAsync(...)
} catch (e) {
  console.log((e as Error).message)   // SFtpFile.someMethodAsync: <reason>
}

Properties

CreateTimeStr
// read-only
readonly createTimeStr: string

Returns the file creation date and time as an RFC 822-formatted string, such as Fri, 21 Nov 1997 09:55:06 -0600.

Server requirement: Creation-time metadata is available only when the server supports SFTP version 4 or later and provides this attribute.

top
DebugLogFilePath
// read/write
debugLogFilePath: string

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

  • A timeout property set to 0, indicating an infinite timeout.
  • A hang occurring within an event callback in the application code.
  • An internal bug in the Chilkat code causing the hang.

More Information and Examples
top
Filename
// read-only
readonly filename: string

Returns the name of the directory entry. Depending on the entry type, this may be a regular filename, directory name, symbolic-link name, or the name of another special filesystem object.

top
FileType
// read-only
readonly fileType: string

Identifies the type of directory entry. The returned value is one of the following:

Value Meaning
regularA regular file.
directoryA directory.
symLinkA symbolic link.
specialA special file whose more specific type is not reported.
unknownThe type is unknown or was not provided by the server.
socketA socket.
charDeviceA character device.
blockDeviceA block device.
fifoA FIFO (named pipe).

The convenience properties IsRegular, IsDirectory, and IsSymLink may be used for the most common entry types.

top
Gid
// read-only
readonly gid: number

Returns the numeric group ID associated with the file.

top
Group
// read-only
readonly group: string

Returns the textual group name associated with the file.

Server requirement: This attribute is available only when the server supports SFTP version 4 or later and provides owner/group names.

top
IsAppendOnly
// read-only
readonly isAppendOnly: boolean

Returns true if the server marks the file as append-only. New data may be added only at the end of the file; existing data cannot be overwritten through normal file writes.

Server requirement: This attribute is defined for SFTP version 6 or later.

top
IsArchive
// read-only
readonly isArchive: boolean

Returns true if the server marks the file for inclusion in backup or archive operations.

Server requirement: This attribute is defined for SFTP version 6 or later.

top
IsCaseInsensitive
// read-only
readonly isCaseInsensitive: boolean

Applies to directories. Returns true when names within the directory should be compared without regard to letter case.

Server requirement: This attribute is defined for SFTP version 6 or later.

top
IsCompressed
// read-only
readonly isCompressed: boolean

Returns true if the file is stored using transparent filesystem-level compression on the server.

This attribute describes how the server stores the file. It does not change the file bytes transferred through SFTP.

Server requirement: This attribute is defined for SFTP version 6 or later.

top
IsDirectory
// read-only
readonly isDirectory: boolean

Returns true if the directory entry is a directory.

top
IsEncrypted
// read-only
readonly isEncrypted: boolean

Returns true if the file is stored using transparent filesystem-level encryption on the server.

This attribute describes storage at rest. It does not alter the file bytes returned by read operations or accepted by write operations.

Server requirement: This attribute is defined for SFTP version 6 or later.

top
IsHidden
// read-only
readonly isHidden: boolean

Returns true if the server marks the entry as hidden. Hidden entries are normally omitted from user-facing displays unless the user specifically requests them.

top
IsImmutable
// read-only
readonly isImmutable: boolean

Returns true if the server marks the file as immutable. An immutable file cannot normally be deleted, renamed, modified, or used as the target of a new hard link.

Immutability is generally stronger than read-only status, the ordinary permission mask, or an access-control list. On many systems, only a privileged administrator can set or clear this attribute.

Server requirement: This attribute is defined for SFTP version 6 or later.

top
IsReadOnly
// read-only
readonly isReadOnly: boolean

Returns true if the server marks the file as read-only.

Server requirement: This attribute is defined for SFTP version 6 or later.

top
IsRegular
// read-only
readonly isRegular: boolean

Returns true if the directory entry is a regular file rather than a directory, symbolic link, device, socket, FIFO, or other special type.

top
IsSparse
// read-only
readonly isSparse: boolean

Returns true if the server identifies the file as sparse. A sparse file can contain unwritten regions, often called holes, that read as zero bytes without consuming equivalent physical disk space.

For example, writing data at an offset of 10 MB may leave the region between the previous end of file and that offset unallocated on disk.

Some servers store all files sparsely and may always set this flag. Other servers cannot reliably determine whether a file is sparse, so a file may be sparse even when this property is false.

Server requirement: This attribute is defined for SFTP version 6 or later.

top
IsSymLink
// read-only
readonly isSymLink: boolean

Returns true if the directory entry is a symbolic link.

top
IsSync
// read-only
readonly isSync: boolean

Returns true if modifications to the file are committed synchronously to server storage.

Server requirement: This attribute is defined for SFTP version 6 or later.

top
IsSystem
// read-only
readonly isSystem: boolean

Returns true if the server marks the file as part of the operating system.

Server requirement: This attribute is defined for SFTP version 6 or later.

top
LastAccessTimeStr
// read-only
readonly lastAccessTimeStr: string

Returns the file's last-access date and time as an RFC 822-formatted string, such as Fri, 21 Nov 1997 09:55:06 -0600.

top
LastErrorHtml
// read-only
readonly lastErrorHtml: string

Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorText
// read-only
readonly lastErrorText: string

Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastErrorXml
// read-only
readonly lastErrorXml: string

Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

top
LastMethodSuccess
// read/write
lastMethodSuccess: boolean

Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.

top
LastModifiedTimeStr
// read-only
readonly lastModifiedTimeStr: string

Returns the file's last-modified date and time as an RFC 822-formatted string, such as Fri, 21 Nov 1997 09:55:06 -0600.

Use LastModifiedTime when a native date/time value is more convenient.

top
Owner
// read-only
readonly owner: string

Returns the textual owner name associated with the file.

Server requirement: This attribute is available only when the server supports SFTP version 4 or later and provides owner/group names.

top
Permissions
// read-only
readonly permissions: number

Returns the POSIX-style file-permission bit mask. The values correspond to the permission and special-mode bits in the POSIX st_mode field.

Symbol Octal value Meaning
S_IRUSR0400Owner read
S_IWUSR0200Owner write
S_IXUSR0100Owner execute
S_IRGRP0040Group read
S_IWGRP0020Group write
S_IXGRP0010Group execute
S_IROTH0004Others read
S_IWOTH0002Others write
S_IXOTH0001Others execute
S_ISUID4000Set-user-ID
S_ISGID2000Set-group-ID
S_ISVTX1000Sticky bit

Use bitwise AND operations to test individual permission bits.

top
Size32
// read-only
readonly size32: number

Returns the file size in bytes as a 32-bit integer. Returns -1 when the size cannot be represented by a 32-bit integer. Use Size64 or SizeStr for larger values.

top
Size64
// read-only
readonly size64: number

Returns the file size in bytes as a 64-bit integer.

top
SizeStr
// read-only
readonly sizeStr: string

Returns the file size in bytes as a base-10 string. This is the string representation of Size64 and is useful in environments where a 64-bit integer is inconvenient or unavailable.

top
Uid
// read-only
readonly uid: number

Returns the numeric user ID associated with the file.

top
VerboseLogging
// read/write
verboseLogging: boolean

If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

top
Version
// read-only
readonly version: string

Version of the component/library, such as "10.1.0"

More Information and Examples
top

Methods