@eyedeekay
&zzz
+RN_
+T3s|4
+cumlord
+dr|z3d
+hagen
+not_bob
+orignal
+postman
+qend-irc2p
+snex
+wodencafe
Arch
Birdy
BubbRubb1
Danny
FreefallHeavens
Irc2PGuest12685
Irc2PGuest17873
Irc2PGuest20240
Irc2PGuest21096
Irc2PGuest41816
Irc2PGuest61421
Irc2PGuest62063
Irc2PGuest62705
Irc2PGuest6367
Irc2PGuest83366
Onn4l7h
Onn4|7h
Over1
Sisyphus
Sleepy
SlippyJoe_
Teeed
aargh2
acetone_
anontor
b3t4f4c3___
dr4wd3
duanin2
gellegery
makoto
nilbog
noidea
nyaa2pguy
onon_
poriori_
profetikla
r00tobo
shiver_1
solidx66_
thetia
u5657_
user1
vivid_reader56
w8rabbit
x74a6
eyedeekay
User reports from Matrix are suggesting that the /data/data/ vs /data/user/0/ issue is happening on some devices that use the freestanding `.apk` builds and Android 11.
eyedeekay
I'm not quite sure why, it doesn't seem to be happening to any of my devices when using the `.apk` builds, including after factory reset, but logs are logs
eyedeekay
As such I'll be uploading 1.7.1 releases of the `.apk` builds tonight/this morning. It contains the same fix as the one which was required on all `.aab` builds.