API Access SharePoint Admin Page Issue
Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
None
What browser(s) / client(s) have you tested
- [ ] 💥 Internet Explorer
- [X] 💥 Microsoft Edge
- [ ] 💥 Google Chrome
- [ ] 💥 FireFox
- [ ] 💥 Safari
- [ ] mobile (iOS/iPadOS)
- [ ] mobile (Android)
- [ ] not applicable
- [ ] other (enter in the "Additional environment details" area below)
Additional environment details
No response
Describe the bug / error
After installing a new version of SPFx package, API page reflects multiple instances of the same APIs (both in approved and pending). Approving API's essentially creates a copy. New package adds another copy to pending. On Entra side of things everything looks fine.
This issue happens on demo tenants, as well as customer tenants.
Steps to reproduce
- Install SPFx package with Graph API's in webApiPermissionRequests
- Approve API's from SharePoint Admin Center
- Install new package
- Look into API access page again
Expected behavior
There should be only one instance of every Graph API on API access page.
Just in case - looking into the oAuth2PermissionGrant response - it does return the following for the approved list - essentially showing scopes twice (as they are on a screenshot for approved). I did approve them twice, so it is kinda messed up now: "scope": "User.Read.All Files.Read.All Sites.ReadWrite.All Directory.Read.All Group.ReadWrite.All Organization.Read.All Sites.Manage.All InformationProtectionPolicy.Read TeamsAppInstallation.ReadForUser TeamsAppInstallation.ReadForUser InformationProtectionPolicy.Read Sites.Manage.All Organization.Read.All Group.ReadWrite.All Directory.Read.All Sites.ReadWrite.All Files.Read.All User.Read.All"
Thanks for reporting this issue. We have made a fix for this which should roll out around October the 2nd.
Hello @sharepointalist , Thank You for your patience. Is the issue resolved now?
I haven't seen this being a problem lately. Let's close this.