BUG: Unhandled error FirebaseFunctionsError: The principal (user or service account) lacks IAM permission "cloudtasks.tasks.create" for the resource

[dpietrzyk]

Hi,
I found I think a bug related to "Extension instance ID" length

Right after the installation of the extension, when it succeeds with "Full Index existing documents?" enabled, "Processing" is never-ending.

In "Error Reporting" in GCP I can see

Unhandled error FirebaseFunctionsError: The principal (user or service account) lacks IAM permission "cloudtasks.tasks.create" for the resource "[...]/ext-firestore-algolia-search-ingredients-executeFullIndexOperation" (or the resource may not exist).

at process.processTicksAndRejections ( node:internal/process/task_queues:95 )

Seen in CloudFunction "ext-firestore-algolia-search-ingredients-qmnu-executeFullIndexO"

And when I am checking the "Cloud Tasks" Queues I see that the name of the queue was truncated to "ext-firestore-algolia-search-ingredients-qmnu-executeFullIndexO"

For the "Extension instance ID" I used: firestore-algolia-search-ingredients-qmnu

"Solution"
When I just uninstalled the extension, installed it one more time but with a shorter "Extension instance ID" everything works fine.

[ready4sea]

I also stumbled upon the exact same issue. In my case, the trigger URL and the queue id were both truncated to 63 characters, which looks the same as the OP above. However, the extension was still calling the full URL.

If 63 characters is the maximum, then the extention should not allow entering more than that. Otherwise, it should not truncate the URL.

[amirmohammadshamss]

I also stumbled upon the exact same issue. In my case, the trigger URL and the queue id were both truncated to 63 characters, which looks the same as the OP above. However, the extension was still calling the full URL.

If 63 characters is the maximum, then the extention should not allow entering more than that. Otherwise, it should not truncate the URL.

Thanks this works for me

[azorychta]

I also stumbled upon the exact same issue. In my case, the trigger URL and the queue id were both truncated to 63 characters, which looks the same as the OP above. However, the extension was still calling the full URL.
If 63 characters is the maximum, then the extention should not allow entering more than that. Otherwise, it should not truncate the URL.

Thanks this works for me

Same issue for me.

"Solution" When I just uninstalled the extension, installed it one more time but with a shorter "Extension instance ID" everything works fine.

Same solution too-- uninstall, re-install with a shorter Extension Instance ID.