Fix for scenario when contact with some number with/without country code
was deleted, and new contact with same number but without/with country
code is added and then new contact have same prefix as deleted one.
Now new contact will have number exacly like provided.
* Switched to DB initialization at compile time
* Organized and cleaned up db files directories(not finished completely)
* Fixed DB related unit tests
* Minor improvements to CMake
* Small fixes for GCC12 build
This mechanism is similar to the current backup implementation,
but is stripped of irrelevant data that is not required by the
MC to perform data synchronization.
Adding or removing country code from existing contacts number is
changing now number record itself, exactly when changed number
is placed in DB, instead to create new number record, to avoid
miss match during matching numbers.
Backup had some issues when filesystem was not clearly closed.
After that, sqlite was not commiting the transaction while
doing VACUUM INTO query, which caused fail on the next
query. Fixed by commiting the transaction when there's
any ongoing one during backup.
Fixed issue that apeared when user switched to contact
edition via Contact details -> Contact Options just after
adding new contact. Contact record without correct ID
was passed through windows, which caused to open
Add new contact window instead of Edit.
Improve structure of the module sys. Problems within this module
prevents from linking others.
Signed-off-by: Marcin Smoczyński <smoczynski.marcin@gmail.com>
Split module-utils into smaller components for better dependency
management. Fix many dependencies throughout the project.
Signed-off-by: Marcin Smoczyński <smoczynski.marcin@gmail.com>
Fixed too short timeout for sending sms
Fixed flow for switching to thred window to asynchornous one
Fixed some minor issues connected to new sms error handling
Add send message test (long sms, special characters)
[EGD-5322] Add send message test (long sms, special characters)
Add send message test (long sms, special characters)
Original behaviour (from dial window) was that user-provided number
was send to db with partial match query. This could cause more than
one result, with no further selection rule. Solution to this
particular behavior was to switch to full number match query.
Additionally problem with unrecognizable prefixes in user-provided
numbers was solved.
of temporary contact. Newly added contact is no longer considered
as a duplicate of a temporary one.
It simply replaces the temporary contact, if its number matches.
[EGD-3572] Application has an instance of Settings - removed from derived apps
[EGD-3572] Application is the owner of Settings handling for its windows/widgets
[EGD-3572] Settings header moved to service-db public section
