Subject: Error importing solution / opening .msapp – Object reference error & invalid file

(1) Share

Report

Posted on by MS-18030810-0

Hi Team,

I am facing issues while importing a solution and opening a Canvas app in Power Apps, and I need your support.

Initially, I tried importing a solution ZIP file, but I received the error:
“Object reference not set to an instance of an object”
(Error Code: 559e7c8b-8be1-4b03-a31a-5c4b6a7cb7ab)

I identified that the solution contained flows without proper connection references. So, I removed the Workflows folder and re-zipped the solution. After fixing the ZIP structure, I attempted the import again, but the same error persisted.

As an alternative, I extracted the Canvas app (.msapp) from the solution and tried importing it directly via Power Apps. However, I received another error:
“Error opening file – There was an error opening the file.”

This suggests that the .msapp file might be corrupted or not fully compatible.

This solution was generated using a migration/AI tool (Pega to Power Platform), so I suspect there may be compatibility issues with the generated package.

Could you please help me understand:

Why this error is occurring even after removing flows and fixing the ZIP structure?
Is there a way to repair or validate the .msapp file?
What is the recommended approach to successfully import or recover this app?

I have attached screenshots of the errors for reference.

Thanks in advance for your help!

Categories:

Building Power Apps

I have the same question (0)

All responses (3)

Answers (0)

Sort by

BCBuizer 22,798 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi @MS-18030810-0,

The fact that the solution is created by a third party tool makes me think that is where you should start your troubleshooting journey.

I'd get in touch with the support organization for the tool first and if all is found to be correct, return here with the findings.

If this reply helped you in any way, please give it a Like 💜 and in case it resolved your issue, please mark it as the Verified Answer ✅.

Was this reply helpful? Yes No
Suggested answer

wolenberg_ 1,476 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello @MS-18030810-0,

The import error persists because the solution manifest still references invalid components, even after removing the Workflows folder. The .msapp file is likely corrupted or not schema‑compliant due to the migration tool. The best path forward is to validate and rebuild the solution using Power Platform CLI, ensure connection references are defined, and if the `.mspp won’t open, regenerate it from a clean export rather than trying to repair the corrupted file.

✨ If my response helped clarify the issue, please mark it as ✅ Accepted Answer and give it a ❤️ like — it helps others in the community find solutions faster. Thank you!

Was this reply helpful? Yes No
Suggested answer

11manish 2,635 on at

Like (0)

Report
Copy link

Link copied!
The "Object reference not set to an instance of an object" error is the generic "NullReferenceException" of the Power Platform. When it occurs during a solution import, it typically means the import engine is looking for a specific piece of metadata that it expects to be there based on the solution.xml or customizations.xml, but the file is missing or the internal GUID is null.

You can give a try to below approach :

Since the migration tool produced a "dirty" package, follow this hierarchy of recovery:

Phase A: The "Clean" Import

Extract the original solution ZIP.

Open solution.xml in a text editor.

Remove every <RootComponent> entry that is not a Table or a Canvas App.

Open customizations.xml. Ensure there are no leftover references to Pega-specific plugins or missing web resources.

Re-zip only the modified XMLs and the CanvasApps folder. Try to import this "Skinny Solution."

Phase B: The "New App" Injection
If the solution import fails but you manage to "Repair" the .msapp (using Step 2 above):

Create a new, blank Canvas App in your target environment.

In the Power Apps Studio, go to Open > Browse files.

Select your repaired .msapp. This is often more successful than using the "Import App" tool, as it forces the Studio to re-parse the control tree.

Was this reply helpful? Yes No