Before, the app assumes the package is valid if there is a README.txt file in it. But, for instance, if the whole account folder were deleted, the app would still thinking it is a valid package and don't show the error: "Your package seems to be corrupted. Click or drop your package file here to retry".
Also, it would end by throwing an error like: "TypeError: Cannot read property 'id' of null"
What was done
Now, in order to handle a package as valid, the app tests if all the required files are there.
That makes random errors much more difficult to happen, and shows "Your package seems to be corrupted. Click or drop your package file here to retry".
What was happening
Before, the app assumes the package is valid if there is a
README.txtfile in it. But, for instance, if the wholeaccountfolder were deleted, the app would still thinking it is a valid package and don't show the error: "Your package seems to be corrupted. Click or drop your package file here to retry".Also, it would end by throwing an error like: "TypeError: Cannot read property 'id' of null"
What was done
Now, in order to handle a package as valid, the app tests if all the required files are there.
That makes random errors much more difficult to happen, and shows "Your package seems to be corrupted. Click or drop your package file here to retry".
By the way, it should fix #22-like issues.