AADSTS650057 Error in Wrapped Power Apps Canvas App (iOS)

(0) Share

Report

Posted on by PPDEV

142

Hi Experts,

I’d appreciate your insights on an issue I’m encountering with my wrapped Power Apps canvas app, which is currently distributed via the Apple App Store.

Error Details:

Correlation Id: d56f081d-cd25-4282-b597-b7f1c6e4d28f
Timestamp: 2025-08-05T02:49:26.000Z
DPTI: F598DC65-5727-4585-A12D-21D8B2A21A68
Message: AADSTS650057
Description: (pii), Domain: MSALErrorDomain. Error thrown in sourceArea: Broker
Tag: 4vlpo
Code: -42003

App Connectors Used:

Office 365 Users
Outlook
SharePoint
Multiple Dataverse tables

Power Automate Flow:

HTTP action
SharePoint: Create folder + Generate sharing link (using SharePoint connection references)

Issue Summary:

The app logs me in successfully, but then loops back to the Authenticator app before showing the error.

If I tap "Cancel," it redirects me to the app, and everything functions normally afterward.

Based on my research, this appears related to resource access, but all connections are verified and seem correctly configured.

I’m stuck at this point and would truly appreciate any guidance or suggestions you can provide. Thank you in advance!

Categories:

Building Power Apps

Image (22).jpg

Screenshot 2025-0...

I have the same question (0)

All responses (4)

Answers (2)

stampcoin 5,058 Super User 2025 Season 2 on at

Like (0)

Report

@PPDEV Hi,

Have you tested it with other IOS devices?

Was this reply helpful? Yes No
PPDEV 142 on at

Like (0)

Report

Hi @stampcoin, yes, and same error.

Was this reply helpful? Yes No
Verified answer

stampcoin 5,058 Super User 2025 Season 2 on at

Like (0)

Report

@PPDEV Hi,

Have you checked the log in Entra Admin ?

You have Timestamp+Correlation Id, so try to check the Sign-in logs if anything special in the log.

It might give you some lead.

Was this reply helpful? Yes No
Verified answer

PPDEV 142 on at

Like (1)

Report
Hi @stampcoin, thank you for your help on this. I was able to identify the root cause of the issue, and I’d like to share the solution here for everyone’s reference in case you encounter the same problem with your wrapped application.

It turns out that app registration now requires more specific API permissions related to Power Platform. Here’s what I did to resolve it:

1) Check if the Power Platform API is already listed in your app’s API permissions. If it’s not, register a new service principal using PowerShell:

Install-Module AzureAD

Connect-AzureAD

New-AzureADServicePrincipal -AppId 8578e004-a5c6-46e7-913e-12f58912df43 -DisplayName "Power Platform API"

2) Add the necessary delegated permissions for the Power Platform API (include any other permissions required by your app), such as:

Environments.Read

PowerApps.Read

3) Grant admin consent to apply the permissions.

Thanks again!

Was this reply helpful? Yes No