I'm starting up a new thread on this problem as I previously raised it in a discussion that had already been marked as answered.
I am trying to publish a project using the Preflight function. The progress bar gets to about 60% complete. It then stalls and after about 10 mins it goes red with the following error:
'Preflight failed because of a network error. Select the preflight button to try again.'
Is this a server issue or could it be related to one of the article files (they are packaged web apps) that I'm including in the project? Is there any way of updating using another tool that gives more detailed error messages - e.g. a console app?
I have tried to strip the project back to include just a single PDF but I get the same result.
I'm under some pressure to get a solution to this problem and would appreciate any assistance.
Bob, do you have an update on this problem? As I say, I am under pressure to find a resolution.
We have created a second project and it exhibits the same issue. I created a very basic HTML-JS web app as a test and the Preflight initially worked when this was the only content included in the build. However, preflight then failed when I attempted to add the real web app and subsequent efforts with the basic web app have failed as well.
The major problem is that the system is not telling me what the issue might be. Is there any way to submit a preflight request using a different mechanism, which provides more verbose error information?
I don't think that it's a problem with the PDF. The PDF is just one of many attempts at preflight'ing an article. I've been trying to publish a web app packaged as a .article file with the same result. This was all working for me a few days ago and then yesterday, it stopped.
I've created a new app in the console but I can't seem to find a way of associating a collection with the new app. I'm not an admin on the project. Perhaps that's the problem.
You might try publishing the article instead of using preflight (use a different project if you have a live app in the current project). I'm not sure if this is a problem with the preflight server or a problem with the PDF-based article.