We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
See https://sentry.io/organizations/openfoodfacts/issues/3749073432/events/2638e00077e54c64abf983aaedb71838/?project=1415205&referrer=previous-event
'null' is sometimes sent as username in during /insights/annotate call.
/insights/annotate
The text was updated successfully, but these errors were encountered:
@raphael0202 Actually there are expected cases when the user is null, branded as "anonymousAnnotation" (in question_page.dart):
question_page.dart
if (OpenFoodAPIConfiguration.globalUser == null && insightId != null) { _anonymousAnnotationList.putIfAbsent(insightId, () => insightAnnotation); } await LoadingDialog.run<Status>( context: context, title: appLocalizations.saving_answer, future: OpenFoodAPIClient.postInsightAnnotation( insightId, insightAnnotation, deviceId: OpenFoodAPIConfiguration.uuid, user: OpenFoodAPIConfiguration.globalUser, ), );
There has been some refactoring here, so it's not easy to follow the history: which user should we use for those anonymous annotations?
Sorry, something went wrong.
No authentication headers should be sent for anonymous annotations. The documentation is not up to date on that matter, sorry for that!
fix: openfoodfacts#625 - no user credentials in header if null
9e0cabe
Impacted file: * `HttpHelper.dart`
fix: #625 - no user credentials in header if null (#626)
8566fcf
monsieurtanuki
Successfully merging a pull request may close this issue.
See https://sentry.io/organizations/openfoodfacts/issues/3749073432/events/2638e00077e54c64abf983aaedb71838/?project=1415205&referrer=previous-event
'null' is sometimes sent as username in during
/insights/annotate
call.The text was updated successfully, but these errors were encountered: