> And NOW, I am forced to include that exotic private READ_GMAIL
> permission to my Manifest.
Ah. My apologies. Not sure what to tell you about that, other than to
perhaps file an issue on b.android.com.
>
> Kevin
>
> On 4 mai, 00:43, Kevin Gaudin wrote:
>> I just declared a default view intent
And NOW, I am forced to include that exotic private READ_GMAIL
permission to my Manifest.
Kevin
On 4 mai, 00:43, Kevin Gaudin wrote:
> I just declared a default view intent-filter for archive mime-types...
> and this is GMail which is calling my Activity, providing a content://
> Uri to the atta
I just declared a default view intent-filter for archive mime-types...
and this is GMail which is calling my Activity, providing a content://
Uri to the attachment.
When I try to open that attachment, I am now asked for a permission...
this is quite odd.
My code is called the same way by any other
> But it's quite surprising to learn about this new permission
> requirement in a crash-report for one specific device. Developing user-
> friendly apps is not possible when the rules change without warning.
The rule is: don't try using the Gmail application this way. Again, the
Gmail application
Thank you for your answer.
I understand that the GMail app is not part of the SDK and that it can
be more secure to inform the user that an app will be able to read
it's mail attachments...
But it's quite surprising to learn about this new permission
requirement in a crash-report for one specific
5 matches
Mail list logo
