ZipStream | stream zipped bundles of remote files

To add to @MarcGravell's answer about differences in GZip encoding, it's worth noting that it looks like you've got an endianness issue with your header bytes, which will be messing up a decoder.

Your header is 4 bytes, which encodes to 5 1/3 base64 characters. The .NET version outputs bAAAAB (the first 4 bytes of which are 6c 00 00 00), whereas the Java version outputs AAAAbB (the first 4 bytes of which are 00 00 00 6c). The fact that the b is moving by around 5 characters among a sea of A's is your first clue (A represents 000000 in base64), but decoding it makes the issue obvious.

.NET's BitConverter uses your machine architecture's endianness, which on x86 is little-endian (check BitConverter.IsLittleEndian). Java's ByteBuffer defaults to big-endian, but is configurable. This explains why one is writing little-endian, and the other big-endian.

You'll want to decide on an endianness, and then align both sides. You can change the ByteBuffer to use little-endian by calling .order(ByteBuffer.LITTLE_ENDIAN). In .NET, you can use BinaryPrimitives.WriteInt32BigEndian / BinaryPrimitives.WriteInt32LittleEndian to write with an explicit endianness if you're using .NET Core 2.1+, or use IPAddress.HostToNetworkOrder to switch endianness if necessary (depending on BitConverter.IsLittleEndian) if you're stuck on something earlier.

It looks like the server you are connecting to applied gzip compression, but failed to include the Content-Encoding response header (which they are meant to include), so the client had no way of knowing that the data was compressed, and didn't decompress it for you automatically. Honestly, you should report this to the server owner as a protocol failure, but for now: you could manually decompress the data using GZipStream. Note that if they fix this, you may need to tweak your code again.

So I found a source of a problem - I'll post it here just for record, in case if anyone would have same problem. Source of the problem was something totally different - I was trying to initiate a download by AJAX request, which of course won't work. I changed my frontend code and instead AJAX I used HTML anchor element with src attribute set on exactly same endpoint and it worked just fine.

Use System.IO.Packaging.ZipPackage can solve the problem, like below code logic :

I wouldn't expect two different Zip algorithms/libraries to yield the same output. For one, in the programmatic way, the file metadata (name, modification date, attributes) are not set, while the command line version will include all that information for unzipping purposes.

Plus libraries update at different cadence than standalones, and you might not have the fixes synchronized to reliably match the outputs.

It means that for a single connection, you need to keep the zlib decompression object open for that whole connection and keep feeding it packets, in order, until the connection is complete. Use the Write method on the decompression object for each packet.

At the same time the connection is complete, the zlib stream should also inform you that the data is complete, since the format is self terminating. Furthermore, there is a check value at the end that will report in an error if any of the data was corrupted.

You are getting 'Unhandled rejection TypeError: dest.write is not a function' bc ourBucket is not a writable stream. It must be an instance of writable stream for you to pipe to it. You should create a bucket file writable stream and use that as ourBucket.

Firestore has its own data persistence (read/write data when offline) and it handles all the hard work so you don't need Hive.

Works on web apps, android and iOS.

See: https://firebase.google.com/docs/firestore/manage-data/enable-offline

Regarding the issue, please refer to the following code. I use new storage SDK Azure.Storage.Blobs.