azure-docs
azure-docs copied to clipboard
MicrosoftDocs
Instructions for Server Key
Instructions currently stop at step 8 which instructs the users to copy and save the server key. However, server key can only be retrieved if Cloud Messaging API (Legacy) is enabled, as per instructions for Legacy SDK. This change takes the instructions from the Legacy SDK and injects them here as well.
@samirbanjanovic : Thanks for your contribution! The author(s) have been notified to review your proposed change.
![prmerger-automator[bot] avatar](https://avatars.githubusercontent.com/u/22479449?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit a28798c:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/notification-hubs/android-sdk.md | :warning:Warning | Details |
articles/notification-hubs/android-sdk.md
-
Line 93, Column 5: [Warning: file-not-found - See documentation]
Invalid file link: './media/notification-hubs-enable-firebase-cloud-messaging/notification-hubs-enable-firebase-cloud-messaging-legacy-api.png'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
@samirbanjanovic : Thanks for your contribution! The author(s) have been notified to review your proposed change.
@samirbanjanovic : Thanks for your contribution! The author(s) have been notified to review your proposed change.
Learn Build status updates of commit 3129c5d:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/notification-hubs/android-sdk.md | :warning:Warning | Details | |
| media/notification-hubs-enable-firebase-cloud-messaging-legacy-api.png | :white_check_mark:Succeeded |
articles/notification-hubs/android-sdk.md
-
Line 93, Column 5: [Warning: file-not-found - See documentation]
Invalid file link: './media/notification-hubs-enable-firebase-cloud-messaging/notification-hubs-enable-firebase-cloud-messaging-legacy-api.png'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
@samirbanjanovic : Thanks for your contribution! The author(s) have been notified to review your proposed change.
Learn Build status updates of commit d9c83ac:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/notification-hubs/android-sdk.md | :warning:Warning | Details | |
| media/notification-hubs-enable-firebase-cloud-messaging-legacy-api.png | :white_check_mark:Succeeded |
articles/notification-hubs/android-sdk.md
-
Line 93, Column 5: [Warning: file-not-found - See documentation]
Invalid file link: './media/notification-hubs-enable-firebase-cloud-messaging-legacy-api.png'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
@samirbanjanovic : Thanks for your contribution! The author(s) have been notified to review your proposed change.
@samirbanjanovic : Thanks for your contribution! The author(s) have been notified to review your proposed change.
Learn Build status updates of commit ae469cd:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/notification-hubs/android-sdk.md | :warning:Warning | Details |
articles/notification-hubs/android-sdk.md
-
Line 93, Column 5: [Warning: file-not-found - See documentation]
Invalid file link: './media/notification-hubs-enable-firebase-cloud-messaging-legacy-api.png'.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Learn Build status updates of commit 57366b7:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/notification-hubs/android-sdk.md | :white_check_mark:Succeeded | ||
| articles/notification-hubs/media/android-sdk/notification-hubs-enable-firebase-cloud-messaging-legacy-api.png | :white_check_mark:Succeeded |
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
PRMerger Results
| Issue | Description |
|---|---|
| Added File(s) | This PR contains added files. New files require human review. |
| Image File | This PR added or updated an image file(s). |
@sethmanheim,
Can you review the proposed changes? If you approve, can you move these changes to the public repo so we can make sure the added image "works".
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
Thank you for the contribution -- this was addressed and fixed in our private repo and should be live after 3 PM PST today. #please-close
