Skip to content

Commit ec3b264

Browse files
committed
Adding notes on accessing autogenerated teams package for SPFx solutions
1 parent 80b2aa6 commit ec3b264

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

docs/spfx/deployment-spfx-teams-solutions.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,17 @@ When SharePoint creates the app manifest, it will use values from the SPFx solut
4949
5050
If a SPFx solution contains multiple web parts designated for use in Microsoft Teams, SharePoint Online will repeat the above process for each of them.
5151

52+
> [!NOTE]
53+
> If you are curious on the generated package structure, you can use use the following REST API to download the package for specific solutions:
54+
>
55+
> `_api/web/tenantappcatalog/downloadteamssolution(id)/$value`
56+
>
57+
> id is the numeric identifier of the solution in the app catalog library.
58+
>
59+
> You can request this API in the context of your app catalog, for example with URL of `https://[yourtenant]].sharepoint.com/sites/appcatalog/_api/web/tenantappcatalog/downloadteamssolution(123)/$value`
60+
> API call will start download process of the generated manifest package.
61+
62+
5263
## Developer-provided Microsoft Teams app manifest & package
5364

5465
When you need more control over the Microsoft Teams app manifest or app package, you can create your own package. In this case, when an administrator selects the **Sync to Teams** button, SharePoint Online will look for the following file in the **\*.sppkg** file: **./teams/TeamsSPFxApp.zip**.

0 commit comments

Comments
 (0)