search

SharePoint / sp-dev-docs

SharePoint & Viva Connections Developer Documentation
https://docs.microsoft.com/en-us/sharepoint/dev/
Creative Commons Attribution 4.0 International
1.24k stars 1.01k forks source link

Not getting API Requests from my SPFX Solution after deploying it to Tenant level app catalog #7074

Closed sivanu137 closed 3 years ago

sivanu137 commented 3 years ago

What type of issue is this?

Question

What SharePoint development model, framework, SDK or API is this about?

💥 SharePoint Framework

Target SharePoint environment

SharePoint Online

What browser(s) / client(s) have you tested

Additional environment details

Issue description

Hi, in my SPFX react framework solution I have some web API permissions added, but the problem is after deploying the solution in tenant level app catalog, nothing is there under pending request in API Management.

image

and my solution is also deployed without any error.

tempsnip

What may be the issue here?? Help me to solve this issue

Thankyou

ghost commented 3 years ago

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

andrewconnell commented 3 years ago

Have you tried uninstalling & deleting it from the app catalog and trying again? It does appear something screwed up.

You could alternatively grant the permission using POSH/M365 CLI.

ghost commented 3 years ago

This issue has been automatically marked as stale because it has marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within the next 7 days of this comment. Please see our wiki for more information: Issue List Labels: Needs Author Feedback & Issue List: No response from the original issue author

NicolajHedeager commented 3 years ago

We are seeing a similar behaviour when we are trying to add new permission requests to an existing SPFx package. The new permissions doesn’t show up under pending requests in API management. We have tried updating the package version but with no success.

Running SPFx 1.12.1 and Node 14.15.5

sivanu137 commented 3 years ago

@andrewconnell Thanks for the response, I tried the same, but no use, the issue remains the same. But I got some workaround to grant the Same permissions via Azure.

I'm very much excited to learn what is the root cause? why my API request from SPFX Package is not showing up under Pending request.

Steps: Add Graph API through UI:

From the Azure portal, display the Azure Active Directory (AAD), then select the App Registration menu and select All Applications, then click on SharePoint Online Client Extensibility Web Application Principal. It's the AAD Application that holds the connection to the API (Microsoft and others) from SharePoint (SPFx or every other development) using the Implicit Flow.

Once here, click on Add permission, then select Microsoft Graph and add the [ExternalItem.Read.All] Graph API delegated permission (you can type the name of the permission in the available search box to get it easily).

image

Once added, grant it by clicking on Grant admin consent for Contoso.

If you go to the API access page (https://contoso-admin.sharepoint.com/_layouts/15/online/AdminHome.aspx#/webApiPermissionManagement), you can see new Permission added under Approved Request.

Reference: https://michaelmaillot.github.io/tips/20210302-spfx-api-permissions/

sivanu137 commented 3 years ago

@NicolajHedeager For time being you can follow the above-mentioned steps to overcome the problem, let's figure out the root cause of this if possible.

NicolajHedeager commented 3 years ago

@sivanu137 That approach has also been my workaround for now, but thanks for steps anyway 😄

sivanu137 commented 3 years ago

@NicolajHedeager , Need your help, Since you were Running SPFx 1.12.1 and Node 14.15.5, can you share with me the yo and gulp versions too? Because I want to upgrade my SPFX Development Environment. If possible share with me the version details.

Currently, I'm running

node -v --> Node - 10.22.0

gulp -v --> CLI version: 2.3.0 Local version: 3.9.1

npm ls -g --depth=0 +-- @microsoft/generator-sharepoint@1.11.0 +-- gulp@4.0.2 `-- yo@3.1.1

NicolajHedeager commented 3 years ago

@sivanu137 Gulp 4.0.2

Yeoman is just scaffolding so it shouldn't matter. I'm updating an existing solution.

MortenGuldbaek commented 3 years ago

We are still seeing this issue in our environments and it's hindering us in releasing new features to our product. Using PS/M365CLI is not an option for us in our deployment scenario.

I'm commenting here to hopefully get some attention to this issue.

Do you have any details @andrewconnell ?

Thanks in advance.

patmill commented 3 years ago

Sorry for the delay - can you help us drill down a bit into this? 1 - Can you share a screenshot of the API access page? Is there any chance that the request has already been previously approved? Are there any errors displayed? 2 - If you look at the network trace in the dev dashboard, or the console, do you see any errors / failed requests / etc?

ghost commented 3 years ago

This issue has been automatically marked as stale because it has marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within the next 7 days of this comment. Please see our wiki for more information: Issue List Labels: Needs Author Feedback & Issue List: No response from the original issue author

ghost commented 3 years ago

Closing issue due to no response from the original author. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: No response from the original issue author