-
Notifications
You must be signed in to change notification settings - Fork 26
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
Restored contact to target Android Phone without a Google Account won't be seen by other Applications #224
Comments
Fossify Contacts has two similar options:
You are importing your contacts into the second one. You need to tap on the |
Thank you. I've done what you indicated:
Phone is selected. but when i click on OK =>nothing happens: the App is stuck |
|
Exactly : Then I got into QUIK app => Setting => Sync with Android SMS database Thank you SO MUCH for your help ! |
By the way, how can I delete the contacts wrongly imported into target "Phone storage (not visible by other apps)" so as to improve privacy ? |
Checklist
Affected app version
1.1.0
Affected Android/Custom ROM version
EMUI 11 non rooted/no custom version
Affected device model
Huawei P Smart 2019
How did you install the app?
GitHub releases
Steps to reproduce the bug
The intended target phone would not have an active Google Account
The aim is to use an Android phone without having to share my contacts inside a Google Account
Application displays a warning that imported contacts will be saved onto "Phone":
Bug: why other apps (SMS App: QUIK for example) can't access contacts and thus can't associate SMS numbers with contacts. Although it has been granted access to all necessary permissions: Contacts, SMS, even Calls and Storage
Expected behavior
All Apps with granted permissions should have access to contacts, not just Fossify applications
Actual behavior
Only App Fossify Contacts and Fossify Messages have access to imported contacts
Screenshots/Screen recordings
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: