Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enum missing FCMv1, FCM should be removed #47913

Open
sveinung-t opened this issue Jan 21, 2025 · 1 comment
Open

Enum missing FCMv1, FCM should be removed #47913

sveinung-t opened this issue Jan 21, 2025 · 1 comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Notification Hub question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@sveinung-t
Copy link

Type of issue

Outdated article

Description

The table indicates that it ends at 6. However, the full table also contains another entry for FCMv1. The table should be:

Name Value Description
Wns 1 WNS Installation Platform
Apns 2 Apns Installation Platform
Mpns 3 Mpns Installation Platform
Fcm 4 Fcm Installation Platform
Adm 5 Adm Installation Platform
Baidu 6 Baidu Installation Platform
FcmV1 9 FCMv1 Installation Platform

Additionally, FCM should be considered an invalid value since Firebase Cloud Messaging no longer recognizes since July of last year. See also Azure Notification Hubs and Google Firebase Cloud Messaging migration for more information.

Page URL

https://learn.microsoft.com/en-us/dotnet/api/microsoft.azure.notificationhubs.notificationplatform?view=azure-dotnet

Content source URL

https://github.com/Azure/azure-docs-sdk-dotnet/blob/master/xml/Microsoft.Azure.NotificationHubs/NotificationPlatform.xml

Document Version Independent Id

f9e7c2d8-1491-24ba-2bc9-11c75c24149f

Article author

@azure-sdk

Metadata

  • ID: 125e173d-fd44-2a93-6b1e-6969788685ba
  • Service: azure-notification-hubs
@github-actions github-actions bot added customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jan 21, 2025
@jsquire jsquire added Notification Hub Service Attention Workflow: This issue is responsible by Azure service team. Client This issue points to a problem in the data-plane of the library. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team and removed needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. labels Jan 21, 2025
Copy link

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @tjsomasundaram.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team Notification Hub question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

2 participants