Error after building power app on android

[mattiaottoborgo]

Hello,

I'm trying to export on android a power app. After the login, I get an error 2400.

When I come back to sign in with my work account, i got the following description:

[ServerError] There was a server error. Error: AdalCode: [MAL_STATUS_API_CONTRACT_VIOLATION] and Message: {Description=Embedded browser flow resulted in 'invalid_client' with description '(pii)', stop_time=2023-03-09T09:08:25.000Z, Message=The operation attempted is invalid., authority_type=Unknown, read_credential_last_error=missing required parameter, ui_event_count=1, client_id=84e5d10d-be66-4f58-bd38-d4f8c985c2ee, prt_enabled=false, original_authority=https://login.microsoftonline.com/common, request_duration=12427, api_status_code=StatusInternal::ApiContractViolation, was_request_throttled=false, api_error_code=0, is_successful=false, additional_query_parameters_count=0, api_error_context=Embedded browser flow resulted in 'invalid_client' with description '(pii)', request_new_prt=false, SystemErrorCode=0, all_error_tags=49dvr, api_error_tag=49dvr, authorization_type=Interactive, start_time=2023-03-09T09:08:12.000Z, Type=OneAuth, api_name=SignInInteractively, correlation_id=f54c9d23-dbe5-4426-b28a-a5644235d31b, request_eligible_for_broker=false, ErrorCode=2400, Tag=49dvr, Domain=com.microsoft.oneauth, msal_version=1.0.0+c5c73a58}12:20 PM

[mattiaottoborgo]

.

[LeeSummers]

I'm facing the same issue, we've got a wrapped power app that triggers flows and on the trigger it will fire an authentication from an upon sign in we ger an error "Something went wrong" 4200.

The Power App then displayed the same error message as described by @mattiaottoborgo 

I'm not sure of a way forward at this point.

[LeeSummers]

I've raised this with Microsoft support to see if they can help out with this one

[mattiaottoborgo]

@LeeSummers did you get any answer from Microsoft support?

[robinke1]

Did anyone make any progress with this, help would be appreciated as I too have the same 2400 error

No help on the web and I am very frustrated after a long line of Power apps issues getting to this point.

Would appreciate any pointers

Thanks

[goncalomelo8]

I have the same problem. Did anyone manage to find out a solution for this?

Cheers

[robinke1]

No look at all with this, someone must be able to help. I have put my project on hold currently. The whole power apps thing has been dissapointing.

Some one must have an answer, please help us out here

[goncalomelo8]

For anyone still having this issue, I managed to solve it on my side.

My app is for iOS devices and the app registration was created automatically during the wrap app process and this is the problem.

When the process creates the app registration for you there are two things it does wrong:

1. It sets it as Single tenant when it should be Multitenant. 
   1. To fix this, open the app registration on the Azure Portal and, on the Authentication tab, under Supported account types, switch to Multitenant.
2. It looks like it is giving the Azure API Connections "Runtime.All" permission, when in fact it isn't.
   1. To fix this, open the app registration on the Azure Portal and, on the API Permissions tab, remove the Azure API Connections permission.
   2. Click on "Add a permission" and search for Azure API Connections on the APIs my organization uses, you will most likely not find it, and this is why it's failing, it seems like the process is creating only some kind of template/mask and not actually giving the app the permissions it needs.
   3. Open the Azure Cloud Shell and run these two commands, replacing what's between <> with your Tenant ID:
      1. Connect-AzureAD -TenantId <your tenant ID>
      2. New-AzureADServicePrincipal -AppId fe053c5f-3692-4f14-aef2-ee34fc081cae -DisplayName "Azure API Connections"
   4. Now repeat step b and you should be able to find the permission and add it.

Let me know if this solved your issue.

Cheers.

[robinke1]

Thank You for responding.

You were spot on with your analysis and detail on fixing the problem. I am now past that error point and have a working APP on my android device.

In my case the app permission were there to install after I had deleted the API connection, but suspect this is because I may have run the script in Azure previously in trying the fix the problem. The key is deleting the API connection first

I hope that is of use to others and again thanks for the response on the initial 2400 error