[codenameone-discussions] Re: CAMERA permission workaroud

2017-12-04 Thread Shai Almog
Hi, this is effectively because Android is stupid. Permission isn't required because it's asked by the other intent so it has nothing to do with our app. The problem is that if the app does request the permission the way that permission passes through the intent chain is "flaky" for security

[codenameone-discussions] Re: CAMERA permission workaroud

2017-12-04 Thread Ivan
Hi Shai, I'm in troubles with Android 6 permissions again and previous solution does not work for my second application I have two applications in the same eclipse workspace (CN1 v.3.8), libs ver. 196, no android hints at all, build.xml of the same version (3.8) ... setup is the same (except

[codenameone-discussions] Re: CAMERA permission workaroud

2017-10-29 Thread Shai Almog
That's a bug in Android 6 because of the broken way permissions were changed in Android. If you have that hint they get confused and assume you need the permission. -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe

[codenameone-discussions] Re: CAMERA permission workaroud

2017-10-29 Thread Ivan
I had this in build hints and when I removed it, it works also on 6.0.x -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[codenameone-discussions] Re: CAMERA permission workaroud

2017-10-29 Thread Ivan
Hi Shai, thanks for answer but I'm confused little bit now. I tried it on another device with Android 6.0.1 (Xiaomi Redmi A4) and the behavior is the same. I start the photo capturing, I get the question to allow photo capturing, I click yes and then I get above mentioned security exception. I

[codenameone-discussions] Re: CAMERA permission workaroud

2017-10-28 Thread Shai Almog
Hi, this isn't a recent regression as this was never the issue. Camera permission shouldn't be requested as we invoke an intent and that's a request that should be made by the intent provider not by us. I think this might be related to an app you might have installed recently on the device