GrapheneOS Copy permission bug?

Is this a bug? @grapheneos

If I change keyboard, I can change it to “paste only” if I change it back to HeliBoard, it’s back to “allow only” I get why system apps are “allow only” but third-party apps should at least have a pop-up warning before changing it back to “allow only”.

Like this.

This is not a GOS support forum, forward your request to their forum.

It is not a request it’s a question.

Edit: Mb little tired today after reading it again I see why you think it was a request.

No, it isn’t a bug. Active keyboard apps always have access to the clipboard. You’re explicitly granting clipboard access by enabling it as a keyboard. Active keyboards act as clipboard managers and revoking access from those with our feature wouldn’t make sense. Active keyboard apps are one of the main ways of pasting into apps when clipboard read access is revoked from apps.

If something is your keyboard, you already trust it to get your inputs or not?

Okay, I finally got some sleep. I was too tired yesterday to try to explain myself. I hope I can explain it a little better now. :melting_face:

I just found it odd that it would change the permission without saying anything, and I wasn’t sure if it was a bug or not. Usually Android would just refuse to open the app or close the app if you denied it the permission.

I haven’t seen any apps that just allows permissions like this before.

I didn’t care that it needed the permission just why it would allow the permission without saying anything, if a app need a permission for it to work ofc it should have it but normally you would get a pop-up warning before Android change it and if you denied it the permission the app would usually just close or stop working.

I was just thinking it should have a pop-up, something like this, before it would let me use the app.

If you remove the camera permission in the camera app and open the app and deny it camera permission, the app would just stop working. It wouldn’t just allow the permission without saying anything.

Looks like it already has it when you enable the keyboard for the first time :slightly_smiling_face:

This is because this isn’t present in stock android. Therefore, apps expect to be able to read and write into clipboard (there are many legit uses). GOS can’t ask permission because apps don’t ask for it.

By the way, Android apps have dozens or hundrefa of permissions by default that you can’t revoke. Use the kDi app to see them. GrapheneOS just exposes some of them and allow you to disable them, if you know what you are doing.

It was the reason I wasn’t sure if it was a bug or not.

Yeah, I know, but the problem was that you can disable it, and it would just enable itself without notifying the user.

Just to show what I mean.


As long it isn’t a bug, I’m fine with it. It was just a question, I honestly didn’t expect people would be mad about it lol.