You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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").
Checklist
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
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.
The text was updated successfully, but these errors were encountered: