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

NotFoundError 404: DELETE /rest/tutanota/calendarevent #8262

Closed
bedhub opened this issue Jan 13, 2025 · 1 comment · Fixed by #8286
Closed

NotFoundError 404: DELETE /rest/tutanota/calendarevent #8262

bedhub opened this issue Jan 13, 2025 · 1 comment · Fixed by #8286
Labels
android issues that concern the android client but not all clients bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues ios issues that concern the ios client but not all clients state:tested We tested it and are about to release it topic: calendar
Milestone

Comments

@bedhub
Copy link
Contributor

bedhub commented Jan 13, 2025

Describe the bug
After log in and during the synchronization process i receive an unexpected error for a DELETE request to an calendar event.

I checked the error reporting and there are a several reports each day.

By looking closer at my case i noticed that the event the we try to delete is part of an external calendar subscription.

To Reproduce
Steps to reproduce the behavior:

  1. Subscribe to calendar via URL and have at least one event inside it.
  2. Have two clients with offline data that have this event in the offline database (e.g. mobile app and desktop client)
  3. Log out of both clients.
  4. Delete the event from the external calendar
  5. Login with client A (mobile app) and synchronize the external calendar so the events gets removed from the tuta server
  6. Login with client B (desktop client) => see unexpected error.

Notes
To easier reproduce this case it is recommended to modify the MailLocator in a way that the synchronization of external calendars is executed always after login ( force=true).

async handleExternalSync() {
		const calendarModel = await locator.calendarModel()

		if (isApp() || isDesktop()) {
			calendarModel.syncExternalC

Expected behavior
Synchronization happens without error

Error Report

Error message:
404: | DELETE /rest/tutanota/calendarevent/ODpM5ZF--B-9/MTcyNzYzODcxMDMyOA
Stacktrace:
dv@asset://app/common-min-BA8onQK2.js:1:13964
@asset://app/calendar-worker.js:23:17958
App version:
259.241217.1
Client type:
Ios
Additional info:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko)
@bedhub bedhub added bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues android issues that concern the android client but not all clients ios issues that concern the ios client but not all clients topic: calendar labels Jan 13, 2025
@bedhub bedhub changed the title NotFoundError 404: DELETE /rest/tutanota/calendarevent/OFrz9fL--V-9/MTczNjE5MzA4NDk3Mg NotFoundError 404: DELETE /rest/tutanota/calendarevent Jan 13, 2025
@vascYT
Copy link

vascYT commented Jan 14, 2025

Thanks for reporting this, I also experience this issue 👍

@murilopereirame murilopereirame self-assigned this Jan 16, 2025
@murilopereirame murilopereirame added this to the Calendar Release milestone Jan 16, 2025
@murilopereirame murilopereirame removed their assignment Jan 16, 2025
@wrdhub wrdhub self-assigned this Jan 16, 2025
@wrdhub wrdhub added the state:tested We tested it and are about to release it label Jan 16, 2025
@wrdhub wrdhub removed their assignment Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
android issues that concern the android client but not all clients bug broken functionality, usability problems, unexpected errors desktop Desktop client related issues ios issues that concern the ios client but not all clients state:tested We tested it and are about to release it topic: calendar
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants