ZipCrc React Native Reference Documentation
ZipCrc
Current Version: 11.6.1
Chilkat.ZipCrc
Use
Use
Use
Use
Call
Use Calculate ZIP-compatible CRC32 values for files, bytes, strings, and streamed data.
Chilkat.ZipCrc calculates the 32-bit CRC value used in ZIP file
headers. It can compute CRC32 values for in-memory byte arrays,
BinData, StringBuilder content, strings using a
specified character encoding, and entire files. It also supports streaming
CRC calculation, allowing applications to process large or incremental data
in chunks without holding the full input in memory.
CRC32 for byte data
CalculateCrc to calculate a ZIP-style CRC32 value for
an in-memory byte array.
BinData support
CrcBd when the input bytes are already stored in a
Chilkat.BinData object.
String CRCs
CrcString or CrcSb to calculate CRC32 for
text using a specific charset such as utf-8,
utf-16, or windows-1252.
File CRCs
FileCrc to calculate the CRC32 of a file while streaming
the file contents to keep memory usage small and constant.
Streaming calculation
BeginStream, add chunks with MoreData, and
finish with EndStream when data arrives incrementally.
Hex formatting
ToHex to convert a 32-bit CRC integer into a readable
hexadecimal string.
FileCrc for files, CalculateCrc or
CrcBd for binary data already in memory, and
CrcString or CrcSb for text where the byte
representation depends on a charset. For large or chunked input, initialize
the CRC with BeginStream, feed each block with
MoreData, and call EndStream to obtain the final
CRC32 value.
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, ZipCrc } 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 zipCrc = new ZipCrc()
// ... the native object is released when `zipCrc` is garbage collected, or now with zipCrc.dispose()Creates the underlying native Chilkat object. ZipCrc 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.
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 {
zipCrc.someMethod(...)
} catch (e) {
console.log((e as Error).message) // ZipCrc.someMethod(...): <reason>
console.log(zipCrc.lastErrorText) // the full Chilkat log of the failed call
}
// The same call without blocking the JavaScript thread:
try {
await zipCrc.someMethodAsync(...)
} catch (e) {
console.log((e as Error).message) // ZipCrc.someMethodAsync: <reason>
}Properties
DebugLogFilePath
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.
LastErrorHtml
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.
topLastErrorText
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.
LastErrorXml
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.
topLastMethodSuccess
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.
VerboseLogging
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.
Version
readonly version: string
Methods
BeginStream
Provides a way to calculate a CRC by streaming the data a chunk at a time. An application would start by calling BeginStream. Then it would add data by calling MoreData for each additional chunk. After the last chunk has been processed, the EndStream method is called to return the CRC.
topCrcBd
Calculates a CRC32 for the bytes contained in bd.
CrcSb
Calculates a CRC32 for the string contained in sb. The charset is the byte representation to be used for the sb when calculating the CRC32. It can be utf-8, utf-16, windows-1252, iso-8859-1, or any of the character encodings (charsets) listed at the link below.
CrcString
Calculates a CRC32 for a string. The charset is the byte representation to be used for the str when calculating the CRC32. It can be utf-8, utf-16, windows-1252, iso-8859-1, or any of the character encodings (charsets) listed at the link below.
EndStream
Finalizes and returns the Zip CRC value calculated by calling BeginStream followed by multiple calls to MoreData.
topFileCrc
Calculates the CRC32 of a file. The data contained in the file is streamed for the calculation to keep the memory footprint small and constant. Returns the CRC32 of the file.
FileCrcAsync
Asynchronous form of FileCrc: the same call on a native worker thread, so the JavaScript thread (and the UI) stays responsive. Takes the same arguments and resolves with the same result. While the returned Promise is pending, every other call on this object throws (the object is busy), except abort(), which cancels the call, and assigning the onPercentDone / onProgressInfo callbacks, which report its progress.
Note: the onPercentDone and onProgressInfo callbacks run on the JavaScript thread while the promise is pending, so they can update the UI directly. A rejection's message is "Class.methodAsync: reason"; the full log is in lastErrorText.
Returns a Promise that resolves with the synchronous method's result (undefined for a void method) and rejects with an Error where the synchronous method would throw.
ToHex
Converts a 32-bit integer to a hex string.
Throws an Error on failure (where the description says null is returned, the method throws instead).
Events
While a method runs, ZipCrc reports progress through two optional callback properties. Assign a function to receive the event, or undefined to stop receiving it. The callbacks are delivered on the JavaScript thread, so they are useful with the ...Async methods: during a synchronous call the JavaScript thread is busy inside Chilkat, and the events can only arrive after it returns.
const zipCrc = new ZipCrc()
zipCrc.onPercentDone = (pct) => setProgress(pct) // pct is 0..100
zipCrc.onProgressInfo = (name, value) => console.log(`${name}: ${value}`)
zipCrc.heartbeatMs = 250 // let abort() take effect within a quarter second
const pending = zipCrc.someMethodAsync(...)
cancelButton.onPress = () => zipCrc.abort() // the promise then rejects
await pendingPercentDone fires when an operation's completion percentage is known; ProgressInfo delivers named progress values (what is reported depends on the class and method). There is no AbortCheck callback: to cancel a pending ...Async call, call abort() on the object. Chilkat notices the request at its next progress check, which happens at least every heartbeatMs milliseconds on the classes that have that property (0, the default, disables the heartbeat, so set it for a responsive cancel), and the promise rejects with Chilkat's abort error. abort() is harmless when nothing is pending.
PercentDone
onPercentDone?: (pctDone: number) => void
This provides the percentage completion for any method involving network communications or time-consuming processing, assuming the progress can be measured as a percentage. This event is triggered only when it's possible and logical to express the operation's progress as a percentage. The pctDone argument will range from 1 to 100. For methods that finish quickly, the number of PercentDone callbacks may vary, but the final callback will have pctDone equal to 100. For longer operations, callbacks will not exceed one per percentage point (e.g., 1, 2, 3, ..., 98, 99, 100).
The PercentDone callback also acts as an AbortCheck event. For fast methods where PercentDone fires, an AbortCheck event may not trigger since the PercentDone callback already provides an opportunity to abort. For longer operations, where time between PercentDone callbacks is extended, AbortCheck callbacks enable more responsive operation termination.
To abort the operation, set the abort output argument to true. This will cause the method to terminate and return a failure status or corresponding failure value.
Example:
zipCrc.onPercentDone = (pct) => {
// pct ranges from 0 to 100.
setProgress(pct) // runs on the JavaScript thread: React state may be updated directly
}
await zipCrc.someMethodAsync(...)
// To stop an operation from within the callback, call zipCrc.abort()ProgressInfo
onProgressInfo?: (name: string, value: string) => void
This event callback provides tag name/value pairs that detail what occurs during a method call. To discover existing tag names, create code to handle the event, emit the pairs, and review them. Most tag names are self-explanatory.
Note: Some Chilkat methods don't fire any ProgressInfo events.
Example:
zipCrc.onProgressInfo = (name, value) => console.log(`${name}: ${value}`)
await zipCrc.someMethodAsync(...)