Android dark side sees new entered contact details

Bug Reports
,
1

REPRODUCIBILITY: always
OS VERSION: 5.0.072
HARDWARE: XA2+
UI LANGUAGE: english
REGRESSION: hmm, switch was again introduced after being absent for many years

DESCRIPTION:

When the switch to allow Android to see contacts from address book is disabled, newly entered contact details can be seen by Android apps.

PRECONDITIONS:

Switch "Make contacts available to Android aaps" in settings is disabled.

STEPS TO REPRODUCE:

  1. Make sure switch is disabled

  2. Create a new contact in (sfos) address book

  3. Take a look at Android apps, and see the new contact

EXPECTED RESULT:

New contact must not be available to Android.

ACTUAL RESULT:

New contact is available to Android.

MODIFICATIONS:

none,

okay, patchmanager installed (nothing activated),
using nemo instead of defaultuser

ADDITIONAL INFORMATION:

After restarting app support (or reboot) it is okay again.
As @ric9k mentioned correctly, of course this happens only as long as App Support is running (after restart this newly added contact is not shared anymore).
2 Likes
3

Where do I find this switch?

4

Settings → Android AppSupport

5

Strange i am on 5.0.0.68 and xiii. I have not this setting section.
The very first contains just infos, the next toggles aas on and off, then there are two buttons for autostart and unofficial apk and last but not least license infos…? No settings at all

6

Do you have the same device as the poster? The Android version can differ depending on the device, even if the SFOS version is the same.

7

It’s not strange at all, these switches were introduced in 5.0.0.72.

3 Likes
8

Thank you makrolon for the clarifying hint! Did not update till now because of the aas start issue, but the new release for all usere is not far anymore.

9

Confirming.
I could reproduce on an XA2 DUAL with SFOS 5.0.0.73.
Good opportunity to start AAS since long and remove some dust on it :–)

I added a first contact before starting AAS and it was not shared.
From what I could observe, the new contact is shared with AAS, when added while AAS is running.

1 Like
10

Oh well spotted. Syncing was blocked but updates snuck through. Fixed for the next release.

8 Likes
11

Great!

This will solve now my “secondary address book” request from TJC , using a third-party contacts app from F-Droid (Fossify Contacts).

1 Like
12

Thanks @peterleinchen for spotting that. Keeping contacts isolated from AAS is extremely important for me.

It’s not strange at all, these switches were introduced in 5.0.0.72

BTW, when they were introduced they defaulted to sharing contacts enabled, and running microG services enabled. Silently. That’s not so good imho, should be opt-in for the user.

1 Like