macOS PackageMaker (.mpkg) file download problem

[knb]

Hi,

I have a guy who claimed to "use PackageMaker all the time" to create an installer for my software program for Mac several days ago.

He sent me a zip file via dropbox, I downloaded it to my Window 7 computer,
uploaded it to a Windows 2008 RT server, but when users downloaded it from my server the zip file contains corrupt files... of course not usable.

Previously another individual created a dmg file for me using PackageMaker and I downloaded and uploaded it to the same server, users did not have a problem about the file corruption.

I personally can't test it because I don't have a Mac handy.

What could be going on?

Thanks.

 

[chown33]

It could be anything.

First, be more specific about exactly what's happening. Are you unzipping on the Windows box? Then rezipping? This can lose data.

Second, have you done anything to independently verify the integrity of the files being transferred? One way to do this is to have your uploading friend calculate the MD5 or SHA1 hash of the file before uploading to DropBox, then have him email you that info (or send it to you by any other independent channel). You then download the file, recalculate the hash, and confirm the two values are identical. If they're not, you've found the inaccurate transfer medium.

Third, if you're not unzipping or rezipping, you still need to confirm the integrity of what gets downloaded from your Windows server, and make sure it's identical to what was uploaded.

The simple way of putting this is you need to independently confirm the integrity of the data at every step in the overall transfer.


Calculating MD5 or SHA1 hashes on files can be done in a Terminal command line:

openssl sha1 path_to_file

The output will be the SHA1 hash.

The same command works if you replace sha1 with md5.

If you type the words openssl sha1 in Terminal, followed by a space, then you can drag and drop a file from a Finder window and Terminal will automagically type in the pathname. Then go to the Terminal window and press the return key.


You can probably find apps on the Mac App Store for calculating MD5 or SHA1 hashes, too. I suggest the keyword sha1.

 

[knb]

It could be anything.

First, be more specific about exactly what's happening. Are you unzipping on the Windows box? Then rezipping? This can lose data.

No. I didn't unzipping and rezipping and then upload the file to my server.

Second, have you done anything to independently verify the integrity of the files being transferred? One way to do this is to have your uploading friend calculate the MD5 or SHA1 hash of the file before uploading to DropBox, then have him email you that info (or send it to you by any other independent channel). You then download the file, recalculate the hash, and confirm the two values are identical. If they're not, you've found the inaccurate transfer medium.

Good thought. Thought about asking him to do this, but was eager to get at least one installation testing feedback based on his 'claimed verified' build downloadable from dropbox.

Will do.

Third, if you're not unzipping or rezipping, you still need to confirm the integrity of what gets downloaded from your Windows server, and make sure it's identical to what was uploaded.

The simple way of putting this is you need to independently confirm the integrity of the data at every step in the overall transfer.


Calculating MD5 or SHA1 hashes on files can be done in a Terminal command line:

openssl sha1 path_to_file

The output will be the SHA1 hash.

The same command works if you replace sha1 with md5.

If you type the words openssl sha1 in Terminal, followed by a space, then you can drag and drop a file from a Finder window and Terminal will automagically type in the pathname. Then go to the Terminal window and press the return key.


You can probably find apps on the Mac App Store for calculating MD5 or SHA1 hashes, too. I suggest the keyword sha1.

Thanks for the specific syntax.

Also, I should have mentioned that the first creator of an installer created the installer of 43MB, it was largely working but have serious flaw.

But the second/current creator of the installer, created the installer of 107MB. Not sure why such huge difference in file size.

Probably the first creator was more competent but he went away for vacation left me cold... I had to drop him.

Many thanks.

 

[knb]

Problem

"The installation failed. The installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance"

Two possibilities here:
Either the creator of the installer is malicious or incompetent.

Now the question, is how to find a DECENT and competent PackageMaker for me, lot of time lost as well.

 

[subsonix]

"The installation failed. The installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance"

Contact the guy, as suggestion in the error message tell you.

 

[knb]

Contact the guy, as suggestion in the error message tell you.

Clarification.
The software and the installer is different. I created this software, it worked and it works. I had another guy created an installer because I don't have a Mac handy myself, and that installer worked. This time around, I had another guy who claimed "he used PackageMaker all the time..." to create it, it did not work.
And yes, I've forwarded the installation failure msg to him.

You may ask, why didn't have the first guy do the job? Yes, I did, but he gave an installer, which seemed to work with one tester then he immediately became unavailable (allegedly on vacation), consequent testers reported major problems.

 

[subsonix]

Clarification.
The software and the installer is different. I created this software, it worked and it works. I had another guy created an installer because I don't have a Mac handy myself, and that installer worked. This time around, I had another guy who claimed "he used PackageMaker all the time..." to create it, it did not work.
And yes, I've forwarded the installation failure msg to him.

Great, I think I got that from your first post. It seems he should be in a much better position to fix it than random strangers on Macrumors forums, that was my point.

 

[knb]

Great, I think I got that from your first post. It seems he should be in a much better position to fix it than random strangers on Macrumors forums, that was my point.

Exactly. Prior to hiring him, we had a phone conversation, during which he even suggested to create a native Mac program, thus, I feel he's a programmer as well or at least sort of like that...

And I provided him with an installation shell script, which I wrote and was used by the previous person, it details the installation process step by step, altogether only 5 steps (functional processes) and largely work if not work perfectly, talking of which I don't mind sharing it with you or a few others. I also provided him with notes on file permissions. And from the very beginning, I advised him to run the shell installation script to see if the process would go through...
So, creating such an installer shouldn't be tough. It really puzzles that he would struggle with it. If he does not know shell he should let me know or ask people in the know... (be it ksh or csh...), and this is not heavy scripting but an understanding of it.
Something isn't right...

Thanks.