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
A Contact with +49 1234 for example was showing as 49 1234 in the App and have not the correct connection with the Phone Contact. I can add this conversation as a new Phone Contact with 49 1234
Overwise the App open a new Conversation as 49 but i written with this Person in the Past and this old conversation have the correct Number with +49, the Contact Name and the connection to the Phone Contact.
Many Thanks!
Greetings
Revan335
Expected behavior
The correct showing, connection with the Persons. Whatever he have +49, 0049, only the number without Country Prefix or another representation like +4912341234, +49 1234 1234, 0049 1234 1234, ...
Actual behavior
Display and/or Assignment Issue.
Screenshots/Screen recordings
No response
Additional information
No response
The text was updated successfully, but these errors were encountered:
Checklist
Affected app version
1.1.4
Affected Android/Custom ROM version
Android 14/15 / iodé 5/6
Affected device model
Shift6mq
How did you install the app?
F-Droid / IzzyOnDroid
Steps to reproduce the bug
Hello,
A Contact with +49 1234 for example was showing as 49 1234 in the App and have not the correct connection with the Phone Contact. I can add this conversation as a new Phone Contact with 49 1234
Overwise the App open a new Conversation as 49 but i written with this Person in the Past and this old conversation have the correct Number with +49, the Contact Name and the connection to the Phone Contact.
Many Thanks!
Greetings
Revan335
Expected behavior
The correct showing, connection with the Persons. Whatever he have +49, 0049, only the number without Country Prefix or another representation like +4912341234, +49 1234 1234, 0049 1234 1234, ...
Actual behavior
Display and/or Assignment Issue.
Screenshots/Screen recordings
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: