Issue authorizing Gateway connection after latest update

[WAstarita]

Since the latest update, on all platforms (Win 10 Studio, Chrome viewing / Chrome Editing, Android 7.1) when I run the app it comes up requesting to authorize use of my SQL server connection but the Allow button is disabled.  My development is dead until I can resolve this.  Any ideas?

Edit:

In Chrome, when trying to open in the preview Editor, I used the console to reenable the Allow button and this is the debugger error I get:

Session ID: 9b71d864-b674-970b-cdc9-0a337907047b
errorMessage: Cannot read property 'apiId' of undefined
callStack: TypeError: Cannot read property 'apiId' of undefined
at https://paaeuscdn.azureedge.net/studio/js/Core.Services.js?v=39db1eb30464:7545:116
at Object.notifySuccess [as _notify] (https://paaeuscdn.azureedge.net/studio/openSource/modified/winjs/js/base.js?v=39db1eb30464:2023:59)
at Object.enter (https://paaeuscdn.azureedge.net/studio/openSource/modified/winjs/js/base.js?v=39db1eb30464:1705:30)
at Promise_ctor._run (https://paaeuscdn.azureedge.net/studio/openSource/modified/winjs/js/base.js?v=39db1eb30464:1921:29)
at Promise_ctor._completed (https://paaeuscdn.azureedge.net/studio/openSource/modified/winjs/js/base.js?v=39db1eb30464:1889:18)
at PromiseQueue._shiftJobsAndStartNextJobIfExists (https://paaeuscdn.azureedge.net/studio/js/Core.js?v=39db1eb30464:3576:146)
at PromiseQueue.pushJob (https://paaeuscdn.azureedge.net/studio/js/Core.js?v=39db1eb30464:3574:78)
at https://paaeuscdn.azureedge.net/studio/js/Core.Services.js?v=39db1eb30464:7544:63
at Array.forEach (native)
at PostConnectionUsageManager.postConnectionUsages (https://paaeuscdn.azureedge.net/studio/js/Core.Services.js?v=39db1eb30464:7543:33)

[WAstarita]

It seems to have something to do with the gateway.  When the switch to environments happened, my CDM stayed in my personal environment but the Gateway to my SQL server is not in the default company gateway.  I shared the connection to the SQL server with everyone in the organization but it still doesn't change anything.

[v-yamao-msft]

Hi WAstarita,

To reproduce this issue, please provide information about:
1.Which environment do you use to create the App?
2.Is your App based on SQL server connection?
3.Do you try to recreate the connection to SQL server in your personal environment then create and share the App to see if it works?
4.Which environment do your organization members use to open the App?

PS: SQL server connection would be shared automatically when you share the App. This article about “Share App resources” for a reference:
https://powerapps.microsoft.com/en-us/tutorials/share-app-resources/

Best regards,
Mabel Mao

[Steelman70]

Hello, I have the same issue and we are using Access Web App on Office 365, which is basically SQL server on the cloud so we do not use a gateway.

It was sharing fine before the last update and now other people on my organisation see that the allow button is disabled.

I have shared the app, the connection etc. but nothing seems to help.

I am stuck.

[Steelman70]

PS I created the app in the Default environment, there is actually a little padlock icon in the form where the allow button is disabled

I have also tried in the personal environment and it is the same, padlock for my colleagues:

[Steelman70]

In addition, if you try to share an SQL server connection with the organisation (i.e. all users) you get an error: