Read the manifest before blaming the platform

Most import failures are described by the file that describes the package.

A package is a compressed archive with a description file at its root. That file lists what is inside, how the pieces relate, and which one starts. When an import fails, that file is where the answer usually is, and reading it directly takes less time than raising a support ticket. It is ordinary structured text and it can be opened in any editor.

The recurring faults are mundane. A referenced file that is not in the archive, usually because the authoring tool published to a folder and somebody compressed the folder rather than its contents, putting everything one level too deep. A path with a backslash in it, which works on the machine it was built on and nowhere else. A character encoding problem in a title that contains an accented letter. None of these is subtle once you are looking at the file.

The second most common class involves the declared version. A package declares which edition of the standard it conforms to, and a delivery system configured for a different edition may reject it or, worse, accept it and behave oddly. When a package works in one system and not another, comparing declared versions is a faster first move than comparing feature lists.

It is worth building the habit of opening the archive before uploading it. Thirty seconds spent confirming that the description file sits at the root, and that the file it names as the entry point exists at the path given, prevents the majority of failed imports and all of the accompanying correspondence.

Two further habits repay the effort. Keep one known-good package that you have verified yourself, and use it whenever a platform behaves oddly, because it separates a problem with the content from a problem with the system in a single test. And when a package fails, record what the failure looked like alongside what it turned out to be, since these faults recur across years and the same three causes account for most of them. That record is worth more than any troubleshooting guide, because it is specific to the tools you actually use.