BUG: Export & Import Canvas App Issues - Entities.json no longer created - MS PowerApps tools won't work with exported app

[Anonymous]

TLDR Summary - 

• When exporting a canvas application - PowerApps appears to no longer create an Entities.json file.  This is regardless of whether I use the "Export package (preview)" to save a ZIP of the project (and opening the MSAPP within) - regardless of whether I tell it to Update or export as a New app, or if I use the "Save As->This computer" option within Studio to directly save the MSAPP file.  (only files in the root of the MSAPP are Header.json and Properties.json - and a few subdirectories)
  
  
• MS PowerApps tools on GitHub do not work with these exported files, as they expect Entities.json to be in the MSAPP.  ie:  tools at https://github.com/microsoft/powerapps-tools
  
  Screenshot of the error message from "PowerApps Review Tool" is shown below:
  
  
• Importing recently exported apps often (almost always) fails with no useful information whether imported by File->Open in Studio (MSAPP file directly) or via "Import package (preview)".  VERY simple apps I have seen work earlier today, but anything with more than a few controls and that have custom components seems to fail every time.  Unsure if this is related to the Entitites.json issue, but could be. 
  
  NOTE: just now tried this while typing this up, and one of my more complex apps did import from Studio with File->Open, when earlier it would not. However, some others still will not. 
  
  
• Importing an MSAPP (or Zip) that has had ANY file modified (to resolve a separate issue I'll post about) fails with an error with no details - whether opening from Studio or from the Import screen.  Below is a screenshot:
  
  

  Note that this is using methods described in the forums and blogs on how to do this (ie: such as editing themes) that worked in the past.  

All of these issues were encountered by trying to resolve another bug whether PowerApps got an app into a state where it would NOT load outside of the dev environment.  After hours of debugging and comparing a working version and the none working (that had additional code I needed and would have taken a while to merge back into the working one), discovered there were some small issues that PowerApps created in the 1.json file for the App control (3 minor parameters). 

Attempts at the above were to resolve that, but I kept running into problems.  Note that the problems above with export and import exist with other (simpler) apps.  

PowerApps Studio 3.19062.18

Happens with Google Chrome (latest 64 bit), latest (as of yesterday) stable Chromium 64 bit build (with no extensions, etc, default settings), and MS Edge.

[v-yuxima-msft]

Hi @Anonymous 

How do you export and import your App?

Do you test with other environments and is there also the same issue?

I test on my side export and save on loacal and then import and there is no the issue.

So could you please change one environmnet to test?

More information:

https://powerapps.microsoft.com/sv-se/blog/powerapps-packaging/

working-with-environments

Best Regards.

Yumia

[Anonymous]

I've tried exporting by BOTH doing Save As (This computer - to a local file) from within Studio - which directly exports the MSAPP, as well as clicking on the ... from the app list screen and selecting "Export package (preview)" which instead exports the whole thing to a ZIP file (ie: manifest.json, as well as directories for included PowerApps, MSFlow, etc, with the MSAPP further below).

And then trying to import the MSAPP directly with Load (Browse Files) to load from the local computer, as well as from the app list screen with "Import package (preview)" to load the ZIP file.

As mentioned in the other thread created by @JamesA (https://powerusers.microsoft.com/t5/Administering-PowerApps/Injecting-updated-JSON-into-msapp-withou...) after I posted this one (seems we both saw these issues at the same time, so most likely this is a recent thing - I know this did work properly 2 months ago).