Packages ignored when opening folder

Symptom: you opened a folder of packages, one with no app.json directly in it, and a module you expected is missing from the Solution page. In a workspace that depends on such a package, the Diagnostics expander on the Solution page lists Unresolved modules and says “The workspace has unresolved dependencies and one or more runtime packages.”

On the Discovery page, the package's row shows the error “Runtime package format not supported.”

Cause: the package is a runtime package. Runtime packages are encrypted, so Prism for AL cannot read them and leaves them out.

Fix: replace the runtime package with the app's normal package, or with its source folder and app.json, then select the Reload button in the Workspace window. If only a runtime package is available, Prism for AL cannot show that module.

Related

• Discovery page
• Unresolved modules
• Runtime package