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

"Permission denied" when creating LOI as data collector #1351

Closed
gino-m opened this issue Dec 13, 2023 · 2 comments · Fixed by #1352
Closed

"Permission denied" when creating LOI as data collector #1351

gino-m opened this issue Dec 13, 2023 · 2 comments · Fixed by #1352
Assignees
Labels
type: bug Something isn't working

Comments

@gino-m
Copy link
Collaborator

gino-m commented Dec 13, 2023

Write failed at surveys/terrabio/lois/WrcZ2g33g057xMeeatWL: Status{code=PERMISSION_DENIED, description=Missing or insufficient permissions., cause=null}

Blocking google/ground-android#2108

@gino-m gino-m added type: bug Something isn't working priority: p0 labels Dec 13, 2023
@gino-m gino-m transferred this issue from google/ground-android Dec 13, 2023
@gino-m gino-m self-assigned this Dec 13, 2023
@gino-m gino-m added this to the Field testing milestone Dec 13, 2023
@gino-m gino-m transferred this issue from google/ground-platform Dec 13, 2023
@gino-m
Copy link
Collaborator Author

gino-m commented Dec 13, 2023

The Firestore rules are correct, the issue is likely that the data collector's email is not being written with the LOI in data.created.user.email.

@gino-m
Copy link
Collaborator Author

gino-m commented Dec 13, 2023

When disabling rules, the LOI is added the the expected audit info:

image

@gino-m gino-m transferred this issue from google/ground-android Dec 14, 2023
@github-project-automation github-project-automation bot moved this from Todo to Done in Ground Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant