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

Temporary unknown error after moving a contact #108

Closed
7 tasks done
WebworkrNet opened this issue Apr 13, 2024 · 3 comments
Closed
7 tasks done

Temporary unknown error after moving a contact #108

WebworkrNet opened this issue Apr 13, 2024 · 3 comments
Labels
duplicate This issue or pull request already exists

Comments

@WebworkrNet
Copy link

WebworkrNet commented Apr 13, 2024

Checklist

  • I can reproduce the bug with the latest version given here.
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

Affected app version

1.0.1

Affected Android/Custom ROM version

Android 14 / One UI 6.0

Affected device model

Samsung Galaxy A13 5G (SM-A136B)

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

  1. Open a contact.
  2. Change the account to which the contact is assigned (move contact).

Expected behavior

Moving takes place without any problems.

Actual behavior

Occasionally, but quite frequently, the move operation is acknowledged with an unknown error. As a user, however, I was often unable to detect any errors during various spot checks. The process was presumably carried out correctly. In rare cases, the move operation was not carried out. In any case: The search result list may also be deleted (contacts previously filtered via search term).

Screenshots/Screen recordings

No response

Additional information

I reported the error by email to the former maintainer back in November 2022. Apart from a query about the system environment, no further work has presumably been done on it.

@WebworkrNet WebworkrNet added bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels Apr 13, 2024
@Aga-C
Copy link
Member

Aga-C commented Apr 13, 2024

It's a duplicate of #101.

@Aga-C Aga-C closed this as not planned Won't fix, can't repro, duplicate, stale Apr 13, 2024
@Aga-C Aga-C added duplicate This issue or pull request already exists and removed bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels Apr 13, 2024
@WebworkrNet
Copy link
Author

@Aga-C Thanks for closing.

I just noticed it myself and was about to close the bug myself. Presumably the GitHub search only finds complete terms and not fragments like "mov" (for "move", "moving").

@WebworkrNet
Copy link
Author

One good thing about the unintentional double ticket: the original Issue 101 has been enriched with additional information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants