Ec app deploy and publish

Docs Build status updates of commit f3e7c7d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-detail-page-checklist.md
:bulb:Suggestion

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/frequently-failed-cases.md
:bulb:Suggestion

Details

msteams-platform/concepts/deploy-and-publish/apps-upload-for-team-and-user.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/application-certification.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/office-store-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/office-store-approval.md
:white_check_mark:Succeeded

msteams-platform/TOC.yml

Line 0: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/publish-app/overview.md).
Line 0: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/publish-app/appsource-submission-walkthrough.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/foo.md).
Line 0: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-content-policy.md).

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/overview.md

Line 9: [Warning] Invalid file link:(~/).
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.
Line 9: [Suggestion] Link 'https://docs.microsoft.com/en-us/microsoft-365-app-certification/teams/teams-apps' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md

Line 11: [Warning] Invalid link: 'help and configuration page'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md doesn't contain a bookmark named 'Help-and-configuration-page'.
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md

Line 11: [Warning] Invalid link: 'Submitting your Microsoft Teams app in the Seller Dashboard'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md doesn't contain a bookmark named 'Submitting-your-Microsoft-Teams-app-in-the-Seller-Dashboard'.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md

Line 11: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/msteams-platform%5Cconcepts%5Cdeploy-and-publish%5Coverview.md).
Line 12: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/msteams-platform%5Cconcepts%5Cdeploy-and-publish%5Cappsource-publishing-guidance%5Cprepare-app%5Capp-functionality-requirement.md).
Line 14: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/frequently-failed-cases.md)).
Line 15: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/msteams-platform%5Cconcepts%5Cdeploy-and-publish%5Cappsource-publishing-guidance%5Cprepare-app%5Coffice-store-checklist.md).
Line 18: [Warning] Invalid link: 'Test Notes for validation'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md doesn't contain a bookmark named 'Test-Notes-for-validation/approval'.
Line 20: [Warning] Invalid file link:(~/appsource-submission-walkthrough.md).
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.
Line 16: [Suggestion] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/debug' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md

Line 18: [Warning] Invalid link: 'Register as a developer'. The file concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md doesn't contain a bookmark named 'Register-as-a-developer'.
Line 19: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Coverview.md).
Line 20: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Cfrequently-failed-cases.md).
Line 21: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Cappsource-submission-walkthrough.md).
Line 22: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app%5Coverview.md).

msteams-platform/concepts/deploy-and-publish/overview.md

Line 10: [Warning] Invalid link: 'Upload your app directly for yourself or a team'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Upload-your-app-directly-for-yourself-or-a-team'.
Line 11: [Warning] Invalid link: 'Publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.
Line 12: [Warning] Invalid link: 'Publish your app through AppSource'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-AppSource'.
Line 17: [Warning] Invalid link: 'publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-detail-page-checklist.md

Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/frequently-failed-cases.md

Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit e7d88cd:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-detail-page-checklist.md
:bulb:Suggestion

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/frequently-failed-cases.md
:bulb:Suggestion

Details

msteams-platform/concepts/deploy-and-publish/apps-upload-for-team-and-user.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/application-certification.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/office-store-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/office-store-approval.md
:white_check_mark:Succeeded

msteams-platform/TOC.yml

Line 0: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/publish-app/appsource-submission-walkthrough.md).

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/overview.md

Line 9: [Warning] Invalid file link:(~/).
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.
Line 9: [Suggestion] Link 'https://docs.microsoft.com/en-us/microsoft-365-app-certification/teams/teams-apps' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md

Line 11: [Warning] Invalid link: 'help and configuration page'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md doesn't contain a bookmark named 'Help-and-configuration-page'.
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md

Line 11: [Warning] Invalid link: 'Submitting your Microsoft Teams app in the Seller Dashboard'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md doesn't contain a bookmark named 'Submitting-your-Microsoft-Teams-app-in-the-Seller-Dashboard'.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md

Line 11: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/msteams-platform%5Cconcepts%5Cdeploy-and-publish%5Coverview.md).
Line 12: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/msteams-platform%5Cconcepts%5Cdeploy-and-publish%5Cappsource-publishing-guidance%5Cprepare-app%5Capp-functionality-requirement.md).
Line 14: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/frequently-failed-cases.md)).
Line 15: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/msteams-platform%5Cconcepts%5Cdeploy-and-publish%5Cappsource-publishing-guidance%5Cprepare-app%5Coffice-store-checklist.md).
Line 18: [Warning] Invalid link: 'Test Notes for validation'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md doesn't contain a bookmark named 'Test-Notes-for-validation/approval'.
Line 20: [Warning] Invalid file link:(~/appsource-submission-walkthrough.md).
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.
Line 16: [Suggestion] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/debug' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md

Line 18: [Warning] Invalid link: 'Register as a developer'. The file concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md doesn't contain a bookmark named 'Register-as-a-developer'.
Line 19: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Coverview.md).
Line 20: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Cfrequently-failed-cases.md).
Line 21: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Cappsource-submission-walkthrough.md).
Line 22: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app%5Coverview.md).

msteams-platform/concepts/deploy-and-publish/overview.md

Line 10: [Warning] Invalid link: 'Upload your app directly for yourself or a team'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Upload-your-app-directly-for-yourself-or-a-team'.
Line 11: [Warning] Invalid link: 'Publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.
Line 12: [Warning] Invalid link: 'Publish your app through AppSource'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-AppSource'.
Line 17: [Warning] Invalid link: 'publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-detail-page-checklist.md

Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/frequently-failed-cases.md

Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 67cffbf:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-detail-page-checklist.md
:bulb:Suggestion

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/frequently-failed-cases.md
:bulb:Suggestion

Details

msteams-platform/concepts/deploy-and-publish/apps-upload-for-team-and-user.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/application-certification.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/office-store-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/office-store-approval.md
:white_check_mark:Succeeded

msteams-platform/TOC.yml

Line 0: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/publish-app/appsource-submission-walkthrough.md).

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/overview.md

Line 9: [Warning] Invalid file link:(~/).
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.
Line 9: [Suggestion] Link 'https://docs.microsoft.com/en-us/microsoft-365-app-certification/teams/teams-apps' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md

Line 11: [Warning] Invalid link: 'help and configuration page'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md doesn't contain a bookmark named 'Help-and-configuration-page'.
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md

Line 11: [Warning] Invalid link: 'Submitting your Microsoft Teams app in the Seller Dashboard'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md doesn't contain a bookmark named 'Submitting-your-Microsoft-Teams-app-in-the-Seller-Dashboard'.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md

Line 11: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/msteams-platform%5Cconcepts%5Cdeploy-and-publish%5Coverview.md).
Line 12: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/msteams-platform%5Cconcepts%5Cdeploy-and-publish%5Cappsource-publishing-guidance%5Cprepare-app%5Capp-functionality-requirement.md).
Line 14: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/frequently-failed-cases.md)).
Line 15: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/msteams-platform%5Cconcepts%5Cdeploy-and-publish%5Cappsource-publishing-guidance%5Cprepare-app%5Coffice-store-checklist.md).
Line 18: [Warning] Invalid link: 'Test Notes for validation'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md doesn't contain a bookmark named 'Test-Notes-for-validation/approval'.
Line 20: [Warning] Invalid file link:(~/appsource-submission-walkthrough.md).
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.
Line 16: [Suggestion] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/debug' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md

Line 18: [Warning] Invalid link: 'Register as a developer'. The file concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md doesn't contain a bookmark named 'Register-as-a-developer'.
Line 19: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Coverview.md).
Line 20: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Cfrequently-failed-cases.md).
Line 21: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Cappsource-submission-walkthrough.md).
Line 22: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app%5Coverview.md).

msteams-platform/concepts/deploy-and-publish/overview.md

Line 10: [Warning] Invalid link: 'Upload your app directly for yourself or a team'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Upload-your-app-directly-for-yourself-or-a-team'.
Line 11: [Warning] Invalid link: 'Publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.
Line 12: [Warning] Invalid link: 'Publish your app through AppSource'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-AppSource'.
Line 17: [Warning] Invalid link: 'publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-detail-page-checklist.md

Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/frequently-failed-cases.md

Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 072ece4:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-detail-page-checklist.md
:bulb:Suggestion

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/frequently-failed-cases.md
:bulb:Suggestion

Details

msteams-platform/concepts/deploy-and-publish/apps-upload-for-team-and-user.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/application-certification.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/office-store-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/office-store-approval.md
:white_check_mark:Succeeded

msteams-platform/TOC.yml

Line 0: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/publish-app/appsource-submission-walkthrough.md).

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/overview.md

Line 9: [Warning] Invalid file link:(~/).
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.
Line 9: [Suggestion] Link 'https://docs.microsoft.com/en-us/microsoft-365-app-certification/teams/teams-apps' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md

Line 11: [Warning] Invalid link: 'help and configuration page'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md doesn't contain a bookmark named 'Help-and-configuration-page'.
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md

Line 11: [Warning] Invalid link: 'Submitting your Microsoft Teams app in the Seller Dashboard'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md doesn't contain a bookmark named 'Submitting-your-Microsoft-Teams-app-in-the-Seller-Dashboard'.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md

Line 11: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/msteams-platform%5Cconcepts%5Cdeploy-and-publish%5Coverview.md).
Line 12: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/msteams-platform%5Cconcepts%5Cdeploy-and-publish%5Cappsource-publishing-guidance%5Cprepare-app%5Capp-functionality-requirement.md).
Line 14: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/frequently-failed-cases.md)).
Line 15: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/msteams-platform%5Cconcepts%5Cdeploy-and-publish%5Cappsource-publishing-guidance%5Cprepare-app%5Coffice-store-checklist.md).
Line 18: [Warning] Invalid link: 'Test Notes for validation'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md doesn't contain a bookmark named 'Test-Notes-for-validation/approval'.
Line 20: [Warning] Invalid file link:(~/appsource-submission-walkthrough.md).
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.
Line 16: [Suggestion] Link 'https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/debug' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites. NOTE: This Suggestion will become a Warning on 12/20/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md

Line 18: [Warning] Invalid link: 'Register as a developer'. The file concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md doesn't contain a bookmark named 'Register-as-a-developer'.
Line 19: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Coverview.md).
Line 20: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Cfrequently-failed-cases.md).
Line 21: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Cappsource-submission-walkthrough.md).
Line 22: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app%5Coverview.md).

msteams-platform/concepts/deploy-and-publish/overview.md

Line 10: [Warning] Invalid link: 'Upload your app directly for yourself or a team'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Upload-your-app-directly-for-yourself-or-a-team'.
Line 11: [Warning] Invalid link: 'Publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.
Line 12: [Warning] Invalid link: 'Publish your app through AppSource'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-AppSource'.
Line 17: [Warning] Invalid link: 'publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-detail-page-checklist.md

Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/frequently-failed-cases.md

Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 4e6f43e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-detail-page-checklist.md
:bulb:Suggestion

Details

msteams-platform/concepts/deploy-and-publish/apps-upload-for-team-and-user.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/application-certification.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app/overview.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/frequently-failed-cases.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/office-store-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/office-store-approval.md
:white_check_mark:Succeeded

msteams-platform/TOC.yml

Line 0: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/publish-app/appsource-submission-walkthrough.md).

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md

Line 11: [Warning] Invalid link: 'help and configuration page'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-functionality-requirement.md doesn't contain a bookmark named 'Help-and-configuration-page'.
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md

Line 11: [Warning] Invalid link: 'Submitting your Microsoft Teams app in the Seller Dashboard'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/appsource-submission-walkthrough.md doesn't contain a bookmark named 'Submitting-your-Microsoft-Teams-app-in-the-Seller-Dashboard'.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md

Line 19: [Warning] Invalid link: 'Test Notes for validation'. The file concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/overview.md doesn't contain a bookmark named 'Test-Notes-for-validation/approval'.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md

Line 18: [Warning] Invalid link: 'Register as a developer'. The file concepts/deploy-and-publish/appsource-publishing-guidance/publish-on-appsource.md doesn't contain a bookmark named 'Register-as-a-developer'.
Line 19: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Coverview.md).
Line 20: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Cfrequently-failed-cases.md).
Line 21: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app%5Cappsource-submission-walkthrough.md).
Line 22: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource-publishing-guidance/post-publish-app%5Coverview.md).

msteams-platform/concepts/deploy-and-publish/overview.md

Line 10: [Warning] Invalid link: 'Upload your app directly for yourself or a team'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Upload-your-app-directly-for-yourself-or-a-team'.
Line 11: [Warning] Invalid link: 'Publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.
Line 12: [Warning] Invalid link: 'Publish your app through AppSource'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-AppSource'.
Line 16: [Warning] Invalid link: 'publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.

msteams-platform/concepts/deploy-and-publish/appsource-publishing-guidance/prepare-app/app-detail-page-checklist.md

Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 7d0b439:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 7d0b439:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/appsource-submission-walkthrough.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/apps-upload-for-team-and-user.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/application-certification.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/overview.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/office-store-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/office-store-approval.md
:white_check_mark:Succeeded

msteams-platform/TOC.yml

Line 0: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/publish-app/appsource-submission-walkthrough.md).

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md

Line 11: [Warning] Invalid link: 'help and configuration page'. The file concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md doesn't contain a bookmark named 'Help-and-configuration-page'.
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/appsource-submission-walkthrough.md

Line 11: [Warning] Invalid link: 'Submitting your Microsoft Teams app in the Seller Dashboard'. The file concepts/deploy-and-publish/appsource/prepare/appsource-submission-walkthrough.md doesn't contain a bookmark named 'Submitting-your-Microsoft-Teams-app-in-the-Seller-Dashboard'.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md

Line 18: [Warning] Invalid link: 'Test notes for validation'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Test-notes-for-validation/approval'.
Line 19: [Warning] Invalid link: 'privacy policy, terms of use and support URLs'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Privacy-policy-terms-of-use-and-support-urls'.

msteams-platform/concepts/deploy-and-publish/appsource/publish.md

Line 18: [Warning] Invalid link: 'Register as a developer'. The file concepts/deploy-and-publish/appsource/publish.md doesn't contain a bookmark named 'Register-as-a-developer'.
Line 19: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Coverview.md).
Line 20: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Cfrequently-failed-cases.md).
Line 21: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Cappsource-submission-walkthrough.md).
Line 22: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/post-publish%5Coverview.md).

msteams-platform/concepts/deploy-and-publish/overview.md

Line 10: [Warning] Invalid link: 'Upload your app directly for yourself or a team'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Upload-your-app-directly-for-yourself-or-a-team'.
Line 11: [Warning] Invalid link: 'Publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.
Line 12: [Warning] Invalid link: 'Publish your app through AppSource'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-AppSource'.
Line 16: [Warning] Invalid link: 'publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 982d684:
:clock10: Pending: waiting for processors (8 builds ahead of you)
:warning: Docs Build is busy, currently there are 8 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 982d684:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/apps-upload-for-team-and-user.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/application-certification.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/overview.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/office-store-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/office-store-approval.md
:white_check_mark:Succeeded

msteams-platform/TOC.yml

Line 0: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/publish-app/appsource-submission-walkthrough.md).

msteams-platform/concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md

Line 11: [Warning] Invalid link: 'Submitting your Microsoft Teams app in the Seller Dashboard'. The file concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md doesn't contain a bookmark named 'Submitting-your-Microsoft-Teams-app-in-the-Seller-Dashboard'.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md

Line 11: [Warning] Invalid link: 'help and configuration page'. The file concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md doesn't contain a bookmark named 'Help-and-configuration-page'.
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md

Line 14: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare/TODO.md).
Line 17: [Warning] Invalid link: 'test notes for validation'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Test-notes-for-validation/approval'.
Line 18: [Warning] Invalid link: 'privacy policy, terms of use and support URLs'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Privacy-policy-terms-of-use-and-support-urls'.

msteams-platform/concepts/deploy-and-publish/appsource/publish.md

Line 18: [Warning] Invalid link: 'Register as a developer'. The file concepts/deploy-and-publish/appsource/publish.md doesn't contain a bookmark named 'Register-as-a-developer'.
Line 19: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Coverview.md).
Line 20: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Cfrequently-failed-cases.md).
Line 21: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Cappsource-submission-walkthrough.md).
Line 22: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/post-publish%5Coverview.md).
Line 27: [Warning] Invalid link: 'Register as a Microsoft app developer'. The file concepts/deploy-and-publish/appsource/publish.md doesn't contain a bookmark named 'register-as-a-Microsoft-app-developer'.

msteams-platform/concepts/deploy-and-publish/overview.md

Line 10: [Warning] Invalid link: 'Upload your app directly for yourself or a team'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Upload-your-app-directly-for-yourself-or-a-team'.
Line 11: [Warning] Invalid link: 'Publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.
Line 12: [Warning] Invalid link: 'Publish your app through AppSource'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-AppSource'.
Line 16: [Warning] Invalid link: 'publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit e9561fd:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit e9561fd:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/apps-upload-for-team-and-user.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/application-certification.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/overview.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/office-store-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/office-store-approval.md
:white_check_mark:Succeeded

msteams-platform/TOC.yml

Line 0: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/publish-app/appsource-submission-walkthrough.md).

msteams-platform/concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md

Line 11: [Warning] Invalid link: 'Submitting your Microsoft Teams app in the Seller Dashboard'. The file concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md doesn't contain a bookmark named 'Submitting-your-Microsoft-Teams-app-in-the-Seller-Dashboard'.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md

Line 11: [Warning] Invalid link: 'help and configuration page'. The file concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md doesn't contain a bookmark named 'Help-and-configuration-page'.
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md

Line 14: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare/TODO.md).
Line 17: [Warning] Invalid link: 'test notes for validation'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Test-notes-for-validation/approval'.
Line 18: [Warning] Invalid link: 'privacy policy, terms of use and support URLs'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Privacy-policy-terms-of-use-and-support-urls'.

msteams-platform/concepts/deploy-and-publish/appsource/publish.md

Line 18: [Warning] Invalid link: 'Register as a developer'. The file concepts/deploy-and-publish/appsource/publish.md doesn't contain a bookmark named 'Register-as-a-developer'.
Line 19: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Coverview.md).
Line 20: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Cfrequently-failed-cases.md).
Line 21: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Cappsource-submission-walkthrough.md).
Line 22: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/post-publish%5Coverview.md).
Line 27: [Warning] Invalid link: 'Register as a Microsoft app developer'. The file concepts/deploy-and-publish/appsource/publish.md doesn't contain a bookmark named 'register-as-a-Microsoft-app-developer'.

msteams-platform/concepts/deploy-and-publish/overview.md

Line 10: [Warning] Invalid link: 'Upload your app directly for yourself or a team'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Upload-your-app-directly-for-yourself-or-a-team'.
Line 11: [Warning] Invalid link: 'Publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.
Line 12: [Warning] Invalid link: 'Publish your app through AppSource'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-AppSource'.
Line 16: [Warning] Invalid link: 'publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit d6e6205:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit d6e6205:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/overview.md
:warning:Warning

Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/apps-upload-for-team-and-user.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/application-certification.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/overview.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/office-store-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/office-store-approval.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md

Line 11: [Warning] Invalid link: 'Submitting your Microsoft Teams app in the Seller Dashboard'. The file concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md doesn't contain a bookmark named 'Submitting-your-Microsoft-Teams-app-in-the-Seller-Dashboard'.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md

Line 11: [Warning] Invalid link: 'help and configuration page'. The file concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md doesn't contain a bookmark named 'Help-and-configuration-page'.
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md

Line 14: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare/TODO.md).
Line 17: [Warning] Invalid link: 'test notes for validation'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Test-notes-for-validation/approval'.
Line 18: [Warning] Invalid link: 'privacy policy, terms of use and support URLs'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Privacy-policy-terms-of-use-and-support-urls'.

msteams-platform/concepts/deploy-and-publish/appsource/publish.md

Line 18: [Warning] Invalid link: 'Register as a developer'. The file concepts/deploy-and-publish/appsource/publish.md doesn't contain a bookmark named 'Register-as-a-developer'.
Line 19: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Coverview.md).
Line 20: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Cfrequently-failed-cases.md).
Line 21: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Cappsource-submission-walkthrough.md).
Line 22: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/post-publish%5Coverview.md).
Line 27: [Warning] Invalid link: 'Register as a Microsoft app developer'. The file concepts/deploy-and-publish/appsource/publish.md doesn't contain a bookmark named 'register-as-a-Microsoft-app-developer'.

msteams-platform/concepts/deploy-and-publish/overview.md

Line 10: [Warning] Invalid link: 'Upload your app directly for yourself or a team'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Upload-your-app-directly-for-yourself-or-a-team'.
Line 11: [Warning] Invalid link: 'Publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.
Line 12: [Warning] Invalid link: 'Publish your app through AppSource'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-AppSource'.
Line 16: [Warning] Invalid link: 'publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit ea1ed78:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit ea1ed78:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/office-store-checklist.md
:bulb:Suggestion

Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/apps-upload-for-team-and-user.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/application-certification.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/overview.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/office-store-approval.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md

Line 11: [Warning] Invalid link: 'Submitting your Microsoft Teams app in the Seller Dashboard'. The file concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md doesn't contain a bookmark named 'Submitting-your-Microsoft-Teams-app-in-the-Seller-Dashboard'.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md

Line 11: [Warning] Invalid link: 'help and configuration page'. The file concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md doesn't contain a bookmark named 'Help-and-configuration-page'.
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md

Line 14: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare/TODO.md).
Line 17: [Warning] Invalid link: 'test notes for validation'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Test-notes-for-validation/approval'.
Line 18: [Warning] Invalid link: 'privacy policy, terms of use and support URLs'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Privacy-policy-terms-of-use-and-support-urls'.

msteams-platform/concepts/deploy-and-publish/appsource/publish.md

Line 18: [Warning] Invalid link: 'Register as a developer'. The file concepts/deploy-and-publish/appsource/publish.md doesn't contain a bookmark named 'Register-as-a-developer'.
Line 19: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Coverview.md).
Line 20: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Cfrequently-failed-cases.md).
Line 22: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/post-publish%5Coverview.md).
Line 27: [Warning] Invalid link: 'Register as a Microsoft app developer'. The file concepts/deploy-and-publish/appsource/publish.md doesn't contain a bookmark named 'register-as-a-Microsoft-app-developer'.

msteams-platform/concepts/deploy-and-publish/overview.md

Line 12: [Warning] Invalid link: 'Publish your app through AppSource'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'publish-to-AppSource'.
Line 16: [Warning] Invalid link: 'publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/office-store-checklist.md

Line 23: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit de8609c:
:clock10: Pending: waiting for processors (7 builds ahead of you)
:warning: Docs Build is busy, currently there are 7 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit de8609c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/office-store-checklist.md
:bulb:Suggestion

Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/apps-upload-for-team-and-user.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/application-certification.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/overview.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/office-store-approval.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md

Line 11: [Warning] Invalid link: 'Submitting your Microsoft Teams app in the Seller Dashboard'. The file concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md doesn't contain a bookmark named 'Submitting-your-Microsoft-Teams-app-in-the-Seller-Dashboard'.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md

Line 11: [Warning] Invalid link: 'help and configuration page'. The file concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md doesn't contain a bookmark named 'Help-and-configuration-page'.
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md

Line 14: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare/TODO.md).
Line 17: [Warning] Invalid link: 'test notes for validation'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Test-notes-for-validation/approval'.
Line 18: [Warning] Invalid link: 'privacy policy, terms of use and support URLs'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Privacy-policy-terms-of-use-and-support-urls'.

msteams-platform/concepts/deploy-and-publish/appsource/publish.md

Line 18: [Warning] Invalid link: 'Register as a developer'. The file concepts/deploy-and-publish/appsource/publish.md doesn't contain a bookmark named 'Register-as-a-developer'.
Line 19: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Coverview.md).
Line 20: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Cfrequently-failed-cases.md).
Line 22: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/post-publish%5Coverview.md).
Line 27: [Warning] Invalid link: 'Register as a Microsoft app developer'. The file concepts/deploy-and-publish/appsource/publish.md doesn't contain a bookmark named 'register-as-a-Microsoft-app-developer'.

msteams-platform/concepts/deploy-and-publish/overview.md

Line 12: [Warning] Invalid link: 'Publish your app through AppSource'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'publish-to-AppSource'.
Line 18: [Warning] Invalid link: 'Publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/office-store-checklist.md

Line 23: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit cf12064:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit cf12064:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/publish.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/overview.md
:warning:Warning

Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/office-store-checklist.md
:bulb:Suggestion

Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/apps-upload-for-team-and-user.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/application-certification.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/post-publish/overview.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/detail-page-checklist.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/prepare/frequently-failed-cases.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/office-store-approval.md
:white_check_mark:Succeeded

msteams-platform/concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md

Line 11: [Warning] Invalid link: 'Submitting your Microsoft Teams app in the Seller Dashboard'. The file concepts/deploy-and-publish/appsource/appsource-submission-walkthrough.md doesn't contain a bookmark named 'Submitting-your-Microsoft-Teams-app-in-the-Seller-Dashboard'.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md

Line 11: [Warning] Invalid link: 'help and configuration page'. The file concepts/deploy-and-publish/appsource/prepare/app-functionality-requirement.md doesn't contain a bookmark named 'Help-and-configuration-page'.
Line 7: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/overview.md

Line 14: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare/TODO.md).
Line 17: [Warning] Invalid link: 'test notes for validation'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Test-notes-for-validation/approval'.
Line 18: [Warning] Invalid link: 'privacy policy, terms of use and support URLs'. The file concepts/deploy-and-publish/appsource/prepare/overview.md doesn't contain a bookmark named 'Privacy-policy-terms-of-use-and-support-urls'.

msteams-platform/concepts/deploy-and-publish/appsource/publish.md

Line 17: [Warning] Invalid file link:(~/concepts/design/understand-use-cases).
Line 18: [Warning] Invalid link: 'Register as a developer'. The file concepts/deploy-and-publish/appsource/publish.md doesn't contain a bookmark named 'Register-as-a-developer'.
Line 19: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Coverview.md).
Line 20: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/prepare%5Cfrequently-failed-cases.md).
Line 22: [Warning] Invalid file link:(~/concepts/deploy-and-publish/appsource/post-publish%5Coverview.md).
Line 27: [Warning] Invalid link: 'Register as a Microsoft app developer'. The file concepts/deploy-and-publish/appsource/publish.md doesn't contain a bookmark named 'register-as-a-Microsoft-app-developer'.

msteams-platform/concepts/deploy-and-publish/overview.md

Line 12: [Warning] Invalid link: 'Publish your app through AppSource'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'publish-to-AppSource'.
Line 18: [Warning] Invalid link: 'Publish to you organization app catalog'. The file concepts/deploy-and-publish/overview.md doesn't contain a bookmark named 'Publish-to-your-organization-app-catalog'.

msteams-platform/concepts/deploy-and-publish/appsource/prepare/office-store-checklist.md

Line 23: [Suggestion] Multiple H1s are not allowed. You can only have one top-level heading. NOTE: This Suggestion will become a Warning on 11/25/2019.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


KAFKA-17169: Add an EndpointsTest suite that test all of the public methods

Add tests to test all the public methods for class raft/Endpoints.java

Thanks for the feedback @OmniaGM , I have updated code to address most issues in comments. Regarding hashcode() & toString() methods, I feel like there is a need to make sure they work as we expected. Happy to remove them if I am on the wrong direction.

Hi @jsancio @OmniaGM , could you please have a look at the updated pr when free? Thanks.

Thanks for the feedback @OmniaGM , updated to address the latest comments as well.

Hi @OmniaGM @jsancio  please take another look when free, thanks.

Thanks for the review @OmniaGM and the PR @masonyc . I take a look tomorrow.

Thanks @jsancio @OmniaGM for looking into it. Please let me know if I need to update anything.

Thanks, @masonyc . This looks good! And thanks to @OmniaGM for reviewing the first versions. LGTM.


Maximized windows didn't fill the screen when Taskbar use small icons

Issue Type: Bug
When windows task bar uses small icons, the maximized vscode windows doesn't fill the screen, there an extra line between the taskbar and window. You can see the black line from my wallpaper in this capture.

Other apps have no problem (Foxit Reader)

The problem doesn't relate to windows theme, vscode extension or screen resolution.
When windows taskbar use large icons, vscode window perfectly fit.
My screen is DellE2416H.


Is there a way to prepare multiple statements into one statement object ?

I am somehow trying to simulate stored procedures by precompiling all the sqls of stored procedures before they are used.
However better-sqlite3 (as well as node-sqlite and node-sqlite3) allow only one sql statement per statement object, or it would be like this:
RangeError: The supplied SQL string contains more than one statement

(actually the rest 2 libs are even worse, they do not allow named parameters).
It means I need to compile the statements line by line into an array, and take case of transactions, since I am not sure how better-sqlite3 handles a single begin; or end; statement.
Any better way to handle multiple statements ?
p.s. at least not db.exec. It does not allow parameters.

I know sqlite3_prepare_v2 do one statement a time.
However, maybe the statement object can hold an array for all the compiled statements ? This is better than holding multiple statement objects in js code.

better-sqlite3 provides a .transaction() function for grouping multiple statements into a transaction. You still need to compile the statements individually, however.
const db = require('better-sqlite3')('my-database.db');

const statements = [
  'DELETE FROM table WHERE id = @id',
  'INSERT INTO table VALUES (@foo, @bar)',
  'UPDATE table SET foo = @foo, bar = @bar',
].map(sql => db.prepare(sql));

const myTransaction = db.transaction((data) => {
  for (const stmt of statements) {
    stmt.run(data);
  }
});

// Execute transaction
myTransaction({ id: 1, foo: 2, bar: 3 });

You could easily create a helper function to make this more automatic:
function compileTransaction(sqlArray) {
  const statements = sqlArray.map(sql => db.prepare(sql));
  return db.transaction((data = {}) => {
    let result;
    for (const stmt of statements) {
      if (stmt.reader) result = stmt.get(data);
      else stmt.run(data);
    }
    return result;
  });
}

xd

@JoshuaWise - Sorry for the ping on a very very old issue. I'm working to basically build this exact same thing, but I'm having problems with it completing properly. Below is a simplified version of what I'm doing. I have a step to flatten the string to remove the \n characters, which seemed to be causing an issue here.
Any ideas on what I'm failing to do/
const run = (queryString: string | string[]): DatabaseResponse => {
  const db = accessDatabase();
  if (Array.isArray(queryString)) {
    const flattenedArray = queryString.map((row) => row.replace(/\n+/gi, '').replace(/\s+/gi, ' '));
    const statements = flattenedArray.map((sql) => db.prepare(sql));
    return db.transaction((data = {}) => {
      for (const stmt of statements) {
        stmt.run(data);
      }
    });
  }

 const stmt = db.prepare(queryString);
 return stmt.run();
};

function checkOrMakeTables() {
  const existingTables = query("SELECT name FROM sqlite_master WHERE type='table';") as { name: Tables }[];

  const tableCreateArray: string[] = [];

  const tableNames = existingTables.map((table) => table.name);
  if (!tableNames.includes('config')) {
    tableCreateArray.push(`
        CREATE TABLE config (
            name TEXT,
            value TEXT,
            profileId TEXT,
            CONSTRAINT profileId
              FOREIGN KEY(profileId)
              REFERENCES profiles(id)
              ON DELETE CASCADE
            )`);
  }
  if (!tableNames.includes('templates')) {
    tableCreateArray.push(`
    CREATE TABLE templates (
        id TEXT PRIMARY KEY UNIQUE,
        name TEXT,
        description TEXT,
        match_fields TEXT,
        single_name_column BOOLEAN,
        amount_in_cents BOOLEAN,
        imported_fields TEXT
        )`);
  }

  if (!tableNames.includes('matches')) {
    tableCreateArray.push(`
    CREATE TABLE matches (
        id TEXT PRIMARY KEY UNIQUE,
        match_type TEXT,
        match_data TEXT,
        database_id TEXT,
        template_id TEXT,
        sync_id TEXT,
        possible_matches TEXT,
        CONSTRAINT sync_id
          FOREIGN KEY(sync_id)
          REFERENCES syncs(id)
          ON DELETE CASCADE
        )`);
  }

  run(tableCreateArray);

// can fix this with
// tableCreateArray.forEach((table) => run(table))

  const tableCheck = query("SELECT name FROM sqlite_master WHERE type='table';") as { name: Tables }[];
  // returned as []
}

Okay, Well, I figured it out and I feel foolish. I didn't realize something needed to actually trigger the db.transaction to run... I had previously been doing async/awaits on all my stuff, and recently discovered you actively discourage that so I'm removing them. The solution is painfully simple, in case anyone else makes it here and wants to replicate.
I stuck everything inside the transaction related to it. Let me know if this is a bad idea in your opinion.
      const runTransaction = db.transaction((queries: string[]) => {
        const flattenedArray = queries.map((row) => row.replace(/\n+/gi, '').replace(/\s+/gi, ' '));
        const statements = flattenedArray.map((sql) => db.prepare(sql));
        statements.forEach((stmt) => {
          stmt.run();
        });
      });

      runTransaction(queryString);


access link prompt not working when deployed on remote server

Access link prompt not working when deployed on remote server
Expected Behavior
It was supposed to authorize when i open the link which i get in the logs on the browser
Actual Behavior
but it was giving me 404 error after authorizing.
Specifications

Java version (java 1.8)
OS (Mac/Linux/Windows)
Maven

Did you open the link with a browser with the correct G Suite access? If you access the file from an account that isn't shared with, you'll see the error 404.
Can you try opening the link with an incognito browser tab?


chore: release main

:robot: I have created a release beep boop
secret: 1.1.0
1.1.0 (2024-06-04)
Features

secret: expose internal methods as a library (#325) (c6edf88)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/aversini/node-cli/releases/tag/secret-v1.1.0 :sunflower:


update namespace gradle 8

I believe we should also remove the package name from: https://github.com/gabrimatic/restart_app/blob/7ab3a332629e86caca5a96b81b0503c2c0aca308/android/src/main/AndroidManifest.xml#L2
In addition to updating the, using this change would result in:
Execution failed for task ':restart_app:compileDebugKotlin'.
> 'compileDebugJavaWithJavac' task (current target is 1.8) and 'compileDebugKotlin' task (current target is 17) jvm target compatibility should be set to the same Java version.
  Consider using JVM toolchain: https://kotl.in/gradle/jvm/toolchain

See https://github.com/gabrimatic/restart_app/issues/27 for more information on how to handle the change.


Add app team leads to devops codeowneers

Add application team leads, Victor and Arnej, into devops code owners group, so they do not need to involve DevSecOps in every minute change.

@arnejduranovic  @victor-chaparro  You should now be able to approve PRs that require DevOps approval - please let me know if you run into any issues.


rfc: change FluentBadge's dismiss icon margin

💬 RFC
in the application i am making with my client's team we are using a font that is smaller than the default font used in fluentUI & has its alignment higher than normal fonts... (its euh... not a fun font!)
Overal this works normal and as expected as we compensate for the smaller font by adjusting all the css variables related of line-height & font-size.
However, in the FluentBadge's content ive noticed the dismiss icon has standard margin of 2px top and 2px left.
The Left pixels is fine, but the top pixels make the badge look off as seen in the screenshot.

After some investigations ive noticed that the text in the dom has only 14 pixels height, compared to the 16 in the storybook. this makes the margin of the icon off.
Therefor, Ive changed this margin to margin: calc(calc(var(--type-ramp-minus-1-line-height) - 12px) / 2) 0px 0px 2px so its kinda positioned in the centre of the line height. it looks as following :

it looks better, but because of the kind of fix, im not feeling particular good with it.
Im also sorry i can not share the font, as it is a font paid for by my client.
🔦 Context
we are using the Autocomplete to select items, but the dismiss icon on the icons looks off when using smaller fonts. we could overwrite it, but would prefer not to do so. we could also leave the line-height as is, but this ends up taking useless space in the UI, as the font is smaller.
💻 Examples
Ive tried to reproduce it using the default font, but was unable to do so sadly... the only example i can give is above screenshots with the data that the line-height was 14px (16px in storybook) and the text is up higher than default.

Hi,
I'm not sure what your ask is here.
If you are achieving what you need with changing the marging yourself, then I'd say go for it! As it is only an issue in your situation with a particular font, I don't think there is a lot of chance we are going to make changes on or side,


RFC - Catalog source  2.0

Updated version of Google Document.
Motivation
Performance
To avoid java.lang.OutOfMemoryError errors, the interface should prevent users from having to store documents into a list which will later be pushed. With that approach, users with significant large amount of documents could easily encounter memory issues.
Instead, the SDK would work in the following manner:

Instantiate the appropriate service
Feed documents to the service
Flush buffered documents

Full examples in src/main/java/com/coveo/pushapiclient/Sandbox.java.

This push mechanism would remain the same regardless of the upload mechanism (Update and Stream modes). The user would simply have to instantiate the appropriate service based on the use case (Full catalog rebuild, catalog incremental update).
FullCatalogUploadService service = source.startfullCatalogUpload("source_id");

Having a dedicated service to each push mode will prevent users from running operations not allowed by the selected mode. E.g. Partial updates and document deletions while in Stream mode.
Automatic batching
The UpdateBatch class used to stack documents before being pushed to a Push source could potentially cause  confusion on the user side. E.g. this approach requires the user to craft documents batches and ensure they respect API size limit.
Instead, users can only instantiate a PushService to which they could feed documents without worrying about batch size.
Proposition
In this PR you will find a Sandbox.java file containing a bunch of examples of how a user might use the SDK.
This file is for demonstration only.
Implementation Details
Here are the classes that will be publicly exposed.
CatalogSource
The main entry point to manipulate Catalog source.
PartialUpdateDocument
This class can be instantiated to build a partial document operation.
DocumentUpdateService
This class will expose methods to perform Full document updates and partial document operation.
FullCatalogUploadService
This class will expose methods to perform Full Catalog Rebuild (a.k.a. Initial catalog upload).

lgtm, looks a lot like the JS sdk

There is a difference between the JS SDK
JavaScript SDK push logic

Get all documents in memory
Pass document list when calling SDK method

Pros:
Straightforward
Cons:
Requires all documents to be in memory before pushing
Java SDK push logic

Push documents
Repeat step one as many time as needed
Close (flush) stream


第一次修改

What is the purpose of the change
XXXXX
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

What is your purpose of this pull request?

Please update PR to make sure purpose of the change is clear.
You can reopen this PR when it's ready


Fix invalid char for report name

Tests pass

Okay will do

Done.
I'll leave it to the next dev support person to get this merged and released.

Thanks


Only test against latest Puppet 5 and 6

Coverage decreased (-0.8%) to 98.374% when pulling 2cb3d8a5b2a074bb59fb20619ab397797cd991cd on ghoneycutt:modernize_testing_platforms into c438df7980d49aa7214521a3ac448505d0215b2b on mcanevet:master.


[Bug] The Not operator handles Boolean constants and Boolean operation results inconsistently.

Search before asking

[X] I searched in the issues and found nothing similar.

Version
1.3.2
Describe the bug and provide the minimal reproduce step
DROP DATABASE root.db0
CREATE DATABASE root.db0

INSERT INTO root.db0(t1) VALUES (1)
INSERT INTO root.db0(timestamp, t1) VALUES (13453556, 2)
INSERT INTO root.db0(timestamp, t1) VALUES<PHONE_NUMBER>, 3)

# query 1
SELECT t1 FROM root.db0 WHERE !FALSE

# query 2
SELECT t1 FROM root.db0 WHERE !(1 != 1)

What did you expect to see?
Query 1 and Query 2 should yield the same result, as 1 != 1 is equivalent to FALSE.
What did you see instead?
Query 1 can retrieve all the data, but Query 2 reports the error Msg: org.apache.iotdb.jdbc.IoTDBSQLException: 301: This predicate contains a not! Did you forget to run this predicate through PredicateRemoveNotRewriter?.
Anything else?
Dear IoTDB team, I believe this is a logical bug, as 1 != 1 is equivalent to FALSE, yet the results of the two operations are inconsistent.  If it is a bug, please mark this issue as "bug". Thank you!
Are you willing to submit a PR?

[x] I'm willing to submit a PR!

It's not a bug, in current version, we don't support constant expression in where or select clause.


Update: New windows size mode

Added improvement to resizing the border so that it was at 90% of the screen size
Fixed Italian localization: Changed 'Lingue' to 'Language' to maintain universal terminology and improve user experience.

@Yidadaa , pls review the locales in Chinese because i dont know if it is correct and let me know if there are any additional modifications needed. Looking forward to your feedback.

Great work!
I've been wanting to do this for a long time, and it would be even better if I could make some adjustments based on the existing code.

Delete the tightBorder option.
Add a windowStyle configuration item to config as an enum value, with options of FixedWidth, AdjustedWidth, and FullScreen.
When selecting different option values, the SubTitle displays the corresponding instructions.

Looking forward to the merge of this PR!!!


Unable to install for Ubuntu 24.04

Describe the bug
With Ubuntu 24.04 being released, I first checked to see if noble was available in https://packages.microsoft.com/repos/azure-cli/dists/.
Since it is not available yet, I tried to use the install script instead curl -L https://aka.ms/InstallAzureCli | bash.
Using the defaults for everything in the script (not specifying any strange paths for install directory or bin directory), I receive an error.
Related command
curl -L https://aka.ms/InstallAzureCli | bash

Errors
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100  1405  100  1405    0     0   1981      0 --:--:-- --:--:-- --:--:--  228k
Downloading Azure CLI install script from https://azurecliprod.blob.core.windows.net/install.py to /tmp/azure_cli_install_tmp_DELCpg.
######################################################################## 100.0%
/tmp/azure_cli_install_tmp_DELCpg: OK
Running install script.
-- Verifying Python version.
-- Python version 3.12.3 okay.
-- Verifying native dependencies.
-- Unable to verify native dependencies. dist=ubuntu, version=24.04. Continuing...

===> In what directory would you like to place the install? (leave blank to use '/home/wdixon/lib/azure-cli'):
-- Creating directory '/home/wdixon/lib/azure-cli'.
-- We will install at '/home/wdixon/lib/azure-cli'.

===> In what directory would you like to place the 'az' executable? (leave blank to use '/home/wdixon/bin'):
-- Creating directory '/home/wdixon/bin'.
-- The executable will be in '/home/wdixon/bin'.
-- Downloading virtualenv package from https://pypi.python.org/packages/source/v/virtualenv/virtualenv-16.7.11.tar.gz.
-- Downloaded virtualenv package to /tmp/tmp1d0rj52p/virtualenv-16.7.11.tar.gz.
-- Checksum of /tmp/tmp1d0rj52p/virtualenv-16.7.11.tar.gz OK.
-- Extracting '/tmp/tmp1d0rj52p/virtualenv-16.7.11.tar.gz' to '/tmp/tmp1d0rj52p'.
-- Executing: ['/usr/bin/python3', 'virtualenv.py', '--python', '/usr/bin/python3', '/home/wdixon/lib/azure-cli']
Already using interpreter /usr/bin/python3
Using base prefix '/usr'
New python executable in /home/wdixon/lib/azure-cli/bin/python3
Also creating executable in /home/wdixon/lib/azure-cli/bin/python
ERROR: The executable /home/wdixon/lib/azure-cli/bin/python3 is not functioning
ERROR: It thinks sys.prefix is '/usr' (should be '/home/wdixon/lib/azure-cli')
ERROR: virtualenv is not compatible with this system or executable
Traceback (most recent call last):
  File "/tmp/azure_cli_install_tmp_DELCpg", line 415, in <module>
    main()
  File "/tmp/azure_cli_install_tmp_DELCpg", line 399, in main
    create_virtualenv(tmp_dir, install_dir)
  File "/tmp/azure_cli_install_tmp_DELCpg", line 144, in create_virtualenv
    exec_command(cmd, cwd=working_dir)
  File "/tmp/azure_cli_install_tmp_DELCpg", line 105, in exec_command
    subprocess.check_call(command_list, cwd=cwd, env=env)
  File "/usr/lib/python3.12/subprocess.py", line 413, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3', 'virtualenv.py', '--python', '/usr/bin/python3', '/home/wdixon/lib/azure-cli']' returned non-zero exit status 100.

Issue script & Debug output
N/A
Expected behavior
I would expect to either setup the PPA or use the Install script to successfully get a working version of the Azure CLI.
Environment Summary
$ python3 --version
Python 3.12.3

$ which python3
/usr/bin/python3

$ cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

Additional context
No response

Thank you for opening this issue, we will look into it.

While the bot did find a solution to my problem for now. With Ubuntu 24.04 being LTS and publicly released (no longer in preview), would love to see an official .deb package in the PPA (https://packages.microsoft.com/repos/azure-cli/dists/) with noble being supported.

@rakibmirza I wrote the following work around to get it installed. It assumes it is ran as root.
azureEnv="/usr/local/share/azure-cli-env"
python3 -m venv "$azureEnv"
"$azureEnv/bin/python" -m pip install --upgrade pip
"$azureEnv/bin/python" -m pip install --upgrade setuptools
"$azureEnv/bin/python" -m pip install azure-cli
ln -s "$azureEnv/bin/az" /usr/local/bin/az

The install script is deprecated.
We'll release a package for 24.04

@bebound Do we have an ETA on this? If not do we have any workaround?

It will be released on May 21.

@PriyankaRudramaina

@bebound Do we have an ETA on this? If not do we have any workaround?

See this comment for a workaround I am currently using.
https://github.com/Azure/azure-cli/issues/28872#issuecomment-2093817749


Add more space or use selection highlight for resource types

The position of the radio button for resource type is not ideal: hard to know which button maps to which icon. Either give them more space or Ideally have the icon be the radio button.

Nice. Does it stand out enough? It's hard to tell from the picture. Would a slight halo or shadow be possible?

that does look nice.  How hard would it be to create a button? thinking about something that Justin said about a grid where the "inverse" is shown when selected (dark background square with white icon)


Can't cast columns

In the PostgRest documentation, it says to cast a column in query do something like...
GET /people?select=full_name,salary::text HTTP/1.1
It seems like this isn't a possibility in this wrapper, unless I am missing something.

Can you provide an example of when this happens and the outpur you get and what you expected to get?

Through the Python supabase client (which I believe leverages this package), I would do something like...
client.table("my_table").select("*").eq("col1::date", "2021-12-31")
I would expect this to cast column "col1" from its current dtype to a date type and then check the equality condition. The error message I get reflects that it looks for column "my_table"."col1::date" instead of "my_table"."col1"::date if that makes sense.

Right, I get what you mean. Although I think you might be missunderstanding a bit how the client works.
For instance, postgrest-py, as client doesn't get all the records and then filters the data in python, but it actually requests the data filtered to the postgres db, therefore if the column is of type date, your example would work with no casting. I would understand the example if your column was of type text and you wanted to filter it as a date.
I also see this postgREST feature would work really well if you wanted to get a column of a type into a certain JSON compatible type. For instance, I have an int column I want to use in my app as text, therefore I could request the certain column casted as text instead of converting this column to text in all records.
What do you think?
Thanks!

This issue is over 2 years old with no replies. Closing this out.


Release 1.23.0

What
Release 1.23.0
Features

[x] Implement renderer library

How to review
Check nothing has slipped into the release that shouldn't be there
Who can review
Anyone but me

PR is out for the changes, as previously noted. I don't feel that these are hotfix worthy but if the other is approved prior to this one and dev is stable for a day then I will add them to the release.


DBeaver - Office support returns an error while saving data

Description
When exporting the data, I get this error

My hypothesis, in the new version of the extension, when saving to excel, sheet name is assigned the beginning of the SQL query that breaks the export if there are special characters. Example below

Export  SELECT '111/11' will broke also a process of export
I would generally disable this change and let Excel create default sheet names as it has in past versions(Sheet 1,2,3 and etc)
DBeaver Version
Community <IP_ADDRESS>411171748
Operating System
Windows 10 Pro
Database and driver
Database: Snowlake
Driver:

Steps to reproduce

Connect to any base
run sql query SELECT '111/11'
try to export(will get the error)

Without special characters will work

Connect to any base
run sql query SELECT '11111'
try to export(will success)

Additional context
No response

@bossanova1986 @YoungEnch
For myself found a temporary crutch, just add 30 allowed characters before any query then the sheet in Excel will use these characters as the name of the sheet. For myself, I made a snippet that inserts 30 minuses before each query. In this case 30 first allowed characters will be used for the sheet name and the data will be exported normally. An example below
--------------------------------
SELECT '111/11'

But basically, I do not understand why the developers began to fill the name of the sheet with the first characters of the request it has never been a problem when exporting, the default name of the sheet from excel all satisfied, who needs it manually renamed.

Thank you for bug report.


all: publish src for sourcemaps

Sourcemaps point to ../[../]*.tsx files. We don't publish those to npm. So, tooling is lacking until we do.
But we explicitly have src in our .npmignore's.  Why was that? Is there a reason to avoid pushing src to npm?

Smaller pkg sizes?
Do some research into industry practice.

Resolved by package.json files addition in the ESM changes.