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

[FR] Proxy Field is missing inside AndroidNotification Object #2876

Closed
durveshparmar opened this issue Mar 17, 2025 · 3 comments · Fixed by #2874
Closed

[FR] Proxy Field is missing inside AndroidNotification Object #2876

durveshparmar opened this issue Mar 17, 2025 · 3 comments · Fixed by #2874

Comments

@durveshparmar
Copy link

Hello, I have been going through an issue of Notifications are delivered but callbacks are not fired in flutter and after going through so many forums, I have figured out that it is a problem with Firebase SDK and Proxy field inside message Object.

Reference URL:
https://firebase.google.com/docs/reference/fcm/rest/v1/projects.messages#AndroidNotification

proxy enum Setting to control when a notification may be proxied.

I could find proxy field in the above page. but If I try to add the same in my code it gives a following error.

Argument of type '{ notification: { title: any; body: any; }; data: { click_action: string; clickAction: any; type: any; relationType: any; relationID: any; relationType2: any; relationID2: any; }; tokens: any[]; android: { ...; }; }' is not assignable to parameter of type 'MulticastMessage'. The types of 'android.notification' are incompatible between these types. Type '{ proxy: string; }' has no properties in common with type 'AndroidNotification'.ts(2345)

After checking messaging-api.d.ts inside lib folder of
https://www.npmjs.com/package/firebase-admin PACKAGE. I have found out that proxy field is missing.

Due to this I am not able to generate the build for my project and it is necessary to be added in our project as we rely on this solution and it works fine if we use this field.

I request you to please include proxy field sooner. I have found few feature requests for the same but could not figured out that when it could be pushed to production.

Thank you.

@google-oss-bot
Copy link

I found a few problems with this issue:

  • I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
  • This issue does not seem to follow the issue template. Make sure you provide all the required information.

@lahirumaramba
Copy link
Member

Thank you for filing this issue. This is currently being addressed in #2874

@jonathanedey
Copy link
Contributor

#2874 is now merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants