Answered

The app didn't start correctly.

(0) Share

Report

Posted on by tristanrobinson

We've migrated an app from a development to a test environment. Upon loading the app in edit mode, everything works as expected. However when we load the app via play we receive an error.

The error we receive is "the app didnt start correctly, check that you are online and try refreshing your browser". When we check the browser console we see an error which says {"error":{"code":"InvalidApiVersion","message":"The API version '' is not valid for provider 'Microsoft.PowerApps' The supported list of API versions are: '2015-02-01, 2015-03-01, 2015-08-01, 2016-01-01, 2016-02-01, 2016-04-01, 2016-05-01, 2016-07-01, 2016-11-01, 2017-02-01, 2017-04-01, 2017-05-01, 2017-06-01, 2017-07-01, 2017-08-01, 2018-10-01, 2019-05-01, 2020-02-01, 2020-06-01, 2020-07-01, 2021-02-01'."}}

Any ideas where to get started with this one?

Categories:

Building Power Apps

All responses (8)

Answers (1)

Sort by

AJ_Z 3,711 Super User 2024 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Are you using chrome browser if not i recommend apps be run in it and ensure the browser is an up to date version. Are you using any custom Connections?
tristanrobinson 35 on at

Like
a
(0)

Report
Copy link

Link copied!

Yup using chrome, and all up to date, tested across multiple machines. No custom connections.
Upon some further digging, it might be caused by Dataverse as its complaining it cannot connect yet the app does not use Dataverse. Might be an environment thing?
AJ_Z 3,711 Super User 2024 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Microsoft Support have suggested rolling back the authoring version in the past for this issue. See below:

As a workaround change the Authoring Version of your PowerApps to the previous version this is usually the one below recommended or if you are not already on the recommended that could be linked to your issue you should try change it to it.. On your side, please go to "PowerApps Canvas app Create" guide panel, then switch to "Account" setting-> "Change Authoring Version" option-> "Authoring Version" to previous version:

let me know how that goes and yeh it may be environment based but i dont think so if there are not ay connections for it being used.
tristanrobinson 35 on at

Like
a
(0)

Report
Copy link

Link copied!

Thanks for the response. We gave that a go too as we found that as a response on an old thread but it didn't seem to make a difference. I am currently connecting with MS so will update the thread when we get to the bottom.
AJ_Z 3,711 Super User 2024 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Okay awesome i am very interested to know the cause of the issue if the find out 🙂
tristanrobinson 35 on at

Like
a
(0)

Report
Copy link

Link copied!

So it looks like the issue is related to the fact one environment is connected to a Dataverse and the new one is not. As far as I'm aware there is no way to delete Dataverse from an environment other than going through Microsoft and even then they were very reluctant to do as asked for some reason.

We also managed to resolve this by using the save as feature within the app, saving locally as a .msapp file and then creating a new blank canvas, opening the local file, removing all the connections and data sources and then re-adding them in again. Bit long winded but I think we are ok now. Hopefully this might help someone else in future.
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!
I think it's related to connections that you Power App is using directly (in the app) or indirectly (in a connected flow). I had some duplicate connections so I removed some from the "Data" --> "Connections" tab. This is where my problem started off course (should have known it was not clever to do that 😅). For me the problem was a Power Automate flow which was connected to the Power App and was turned off.

Without saving the Power App locally I managed to fix the problem in the already existing Power App by doing the following:
Open the Power App in edit mode and delete the connected Power Automate flow
Save, publish and close the Power App
Try to play the Power App and see if it works (for me this worked so I knew the problem was with the turned off flow)
Turn on the Power Automate flow
Open the Power App in edit mode again and add the existing turned on flow to the Power App
Save, publish and close the Power App
This solved my problem. The same can be done with all your other connections in the Power App so you can see which connection broke you app. If you are not interested in that you can do the above steps with all you connections at the same time.

Let me know if this was helpful to you! Good luck and happy building 👍
Verified answer

tristanrobinson 35 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi, just to close out this topic. The issue was indeed to do with a Dataverse connected to the environment that we didn't use or didn't need. Unfortunately once a Dataverse is created for an environment, you cannot undo this directly or indirectly (without jumping through lots of support calls). The recommendation from MS is to create a new (Dev) environment without a Dataverse and import it from the copy of the new environment (Test) which you were originally trying to import to. Then once you have it in the new (Dev) environment you can move it back into the new (Test) environment without issue. It seemed to work for us as it disconnected the code from the old Dataverse after moving the app through the environments.