Documentation improvement, dangers of having an "old/wrong" fingerprint about magiskhidepropsconf HOT 5 CLOSED

That's a good idea. The docs can always be improved...

I'll look at that later, no need for an RP (unless you really want to, but I can't promise I'll use it).

from magiskhidepropsconf.

No problem, if I have free time this weekend (maybe not so likely?) and you haven't done it, I'll draft one.

Also, no worries if you don't use it -- that is why I posted it as an issue and offered to do it! 😆

Thanks for this repo btw

from magiskhidepropsconf.

Ok...

I added some warnings and info on what might happen if you change props and use different/old device fingerprints.

https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#warning-1
https://github.com/Magisk-Modules-Repo/MagiskHide-Props-Config/blob/master/README.md#can-i-use-any-fingerprint
https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/README.md#the-play-store-is-broken

I'm considering it a first draft, but hardly anyone reads the docs anyway...

If you've got anything to add I'm all ears.

from magiskhidepropsconf.

Generally speaking, I believe this is all good.

Also, I'm not 100% certain exactly how the filtering is done, as it's done server side for Google Play. The fingerprint is potentially a factor - but may not be the leading factor. As google states themselves, one "should not part the fingerprint themselves".

I think your changes to the README are good - I just wanted to state the above incase someone stumbles into this issue, etc.

from magiskhidepropsconf.

Yeah... It's because of that kind of uncertainty that I usually try to keep the docs a bit vague on subjects like this (might, possibly, could, etc).

Thanks for the inspiration and the kick in the behind.

from magiskhidepropsconf.