Requested entity was not found

[oluwaseunladeinde]

Send messages

• Trying to send a message to an android device with its registration token.
• I get a 404 all the time
  • requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://fcm.googleapis.com/v1/projects/project-id/messages:send
• firebase_admin.messaging.ApiCallError: Requested entity was not found.

Need help urgently

• Operating System version: Windows 10
• Firebase SDK version: firebase-admin-python
• Library version: Python 3
• Firebase Product: messaging

A Cue

Steps to reproduce:

Get the token from a registered android device and tried sending message to the same device but kept getting a 404 entity requested not found. I am confused at what entity it is referring to. . I was wondering if I had to save the device token on my firebase db?

[hiranya911]

The SDK is not detecting your project ID. How did you initialize the SDK? Share the code please.

[oluwaseunladeinde]

from firebase_admin import credentials, initialize_app, delete_app, auth, db, get_app,
messaging

cred = credentials.Certificate('filename.json')
default_app = initialize_app(cred)
message = messaging.Message(data={'note': '2864974004'}, token='',)
response = messaging.send(message)

@hiranya911 I suspect that is the case. But the filename.json was generated from my serviceaccount from the Google API Console. SO I am not sure how the Project ID is not recognized.

[hiranya911]

Did you edit the following error message in any way before posting? I see the string project-id in the URL, which is not correct:

requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://fcm.googleapis.com/v1/projects/project-id/messages:send

If this is indeed the error you receive, then that's the issue.

[oluwaseunladeinde]

I actually did. It was my attempt to mask my project id. Not sure if it was safe to make that public.
@hiranya911

[hiranya911]

Ok, in that case my initial guess was wrong. The SDK does indeed correctly pick up the project ID. Try downloading a service account from Firebase console, and give this another try. I'm thinking this has something to do with how your service account json was obtained.

[oluwaseunladeinde]

Hi @hiranya911 I get an entirely new error with a new service account generated from the Firebase Console twice. I have enabled Firebase Cloud Messaging API but nothing works.

** raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://fcm.googleapis.com/v1/projects/project-id/messages:send

** raise ApiCallError(code, msg, error) firebase_admin.messaging.ApiCallError: The caller does not have permission

Do you have a sample codebase that works that I can use as a guide. At this point, its difficult to tell whether it is my code or there are some pieces in the setup I have missed. The Python code on the documentation has not helped much.

Thanks in advance.

[hiranya911]

The issue doesn't reproduce to me. And since this is the only report we have received on this issue, it's most likely a problem with your environment and project set up. Try capturing the full response payload sent by the back-end server. You can access this via the detail property of the ApiCallError.

err.detail.response.json()

[joshimbriani]

I had the same error as your initial one and it turned out that my device ID changed and I was still using the old ID. If anyone sees that error in the future it might be worth double checking that you have the correct device token.

[hiranya911]

I'm closing this as there aren't enough details to investigate this further. Please let us know if somebody finds something new related to this.

[Syednazirhussain]

I also faced the same issue if device no longer exists it show me the error like that i actually send bulk notification having device ids inside an array and loop through it when any device id no longer exist it break my code i want to handle and continue to next device id
{
"message": "Client error: POST https://fcm.googleapis.com/v1/projects/internationalfriendspusher/messages:send resulted in a 404 Not Found response:\n{\n "error": {\n "code": 404,\n "message": "Requested entity was not found.",\n "status": "NOT_FOUND",\n "detail (truncated...)\n",
"exception": "Kreait\Firebase\Exception\Messaging\NotFound",
"file": "/var/www/vhosts/lvps87-230-85-233.dedicated.hosteurope.de/pusherang/MainApp/vendor/kreait/firebase-php/src/Firebase/Exception/MessagingException.php",
"line": 76
}

[vsukhin]

Got an interesting case, we recieved "Requested entity was not found." error for some old device ids, but notification was still delivered to the device

[zardilior]

Got same error when sending notifications

[Shahor]

I can confirm I get the same error as well when delivering notifications and most of them are being delivered.

(I am using the nodejs library though, but I'm posting here as the issue is related and this might just be a server side thing)

[zardilior]

I had this error when sending notifications to devices that did not contain the app any longer