[go: nahoru, domu]

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

extension error #82

Closed
leblancmeneses opened this issue Nov 17, 2021 · 2 comments
Closed

extension error #82

leblancmeneses opened this issue Nov 17, 2021 · 2 comments

Comments

@leblancmeneses
Copy link

We upgraded to:

Search with Algolia
algolia/firestore-algolia-search@0.5.9

We are seeing this error:

ext-firestore-algolia-search-executeIndexOperation
Error when performing Algolia index { FetchError: invalid json response body at https://accounts.google.com/ServiceLogin?service=ah&passive=true&continue=https://uc.appengine.google.com/_ah/conflogin%3Fcontinue%3Dhttps://xxxxxx/extAlgoliaSearchCustomers reason: Unexpected token < in JSON at position 1 at /workspace/node_modules/node-fetch/lib/index.js:272:32 at process._tickCallback (internal/process/next_tick.js:68:7) message: 'invalid json response body at https://accounts.google.com/ServiceLogin?service=ah&passive=true&continue=https://uc.appengine.google.com/_ah/conflogin%3Fcontinue%3Dhttps://xxxxxxx/extAlgoliaSearchCustomers reason: Unexpected token < in JSON at position 1', type: 'invalid-json' }

@smomin
Copy link
Collaborator
smomin commented Nov 17, 2021

Hello @leblancmeneses,

We have tested this on our Firebase Database and we did not find any issues. Can you provide more details? Also, based on errors, it seems like Service User issue. You might want to also open a ticket with Firebase team. Thanks.

Sajid

@smomin
Copy link
Collaborator
smomin commented Dec 6, 2021

Closing the ticket due to no response.

@smomin smomin closed this as completed Dec 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants