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
I noticed that DAVdroid couldn't access the network regardless of Orwall's rules for DAVdroid (even if I rebooted the device and disabled/enabled DAVdroid in Orwall). I then did the following experiment:
iptables -L | grep davdroid
This showed a rule that said owner UID match u0_a67 /* Allow at.bitfire.davdroid to connect on localhost */
ls -n /data/data/at.bitfire.davdroid
This showed that the owner UID was 10043, not 10067.
This mismatch isn't the case for my other apps, which work fine with Orwall. I've reinstalled DAVdroid multiple times since installing Orwall (and I believe it stopped working after one of the reinstalls). However, I'm unable to reproduce this mismatch by reinstalling other apps.
Is Orwall possibly trying to cache the UID of apps, and maybe this cache sometimes desyncs from reality?
I noticed that DAVdroid couldn't access the network regardless of Orwall's rules for DAVdroid (even if I rebooted the device and disabled/enabled DAVdroid in Orwall). I then did the following experiment:
iptables -L | grep davdroidThis showed a rule that said
owner UID match u0_a67 /* Allow at.bitfire.davdroid to connect on localhost */ls -n /data/data/at.bitfire.davdroidThis showed that the owner UID was 10043, not 10067.
This mismatch isn't the case for my other apps, which work fine with Orwall. I've reinstalled DAVdroid multiple times since installing Orwall (and I believe it stopped working after one of the reinstalls). However, I'm unable to reproduce this mismatch by reinstalling other apps.
Is Orwall possibly trying to cache the UID of apps, and maybe this cache sometimes desyncs from reality?