The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
But if an app hasn't requested (and hasn't been granted) permission to read storage, does it REALLY mean it can't access storage? I read about some malware that don't request these permissions (so they don't even show up on the Play store in the permissions section) but once downloaded, they 'phone home' to download more executable code that has a malicious payload, which includes access to, say, storage that the original app didn't have. How tight is the sandbox really?
I just wonder if your app might be doing something like this. One thing you can do is install a firewall and see what IPs the app connects to. I've used NoRoot Firewall by Greyshirts (who came up with that name? ) in the past that can do this.
"We have already been through this, I am not going to repeat myself." - fat_boy, in a global warming thread
NoRoot Firewall by Greyshirts (who came up with that name? )
Someone who is married.
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash One Fine Saturday. 24/04/2004
Although in some strange realm that may be something one needs to do, if one were writing their own strlen(...), would it not be better to give it its own name, too? Or maybe create some weird-ass overload if the language permits it?
On the other hand, if it's scope is wide enough, think of the fun you could have with other members of some team when their code goes insane for no discernible reason.
You can add methods right to core classes! You don’t have to call Time.now.advance(days: -1), you can write 1.day.ago! It makes Ruby a joy to read and write. Until…
You hit weird bugs because a patch changed Hash.
You get confused about which code actually ran, so you can’t debug it when it breaks.
And you finally figure out that all your problems were caused six months ago, when you monkey-patched Enumerable to make one line of code five characters shorter.