IssueTracker

[Comment deleted]

Oh, and I'm seeing this on both the emulator and a Galaxy Nexus. Simply launching an activity that does something like this is enough to reproduce:

ClipboardManager manager = (ClipboardManager) getSystemService(CLIPBOARD_SERVICE);
manager.addPrimaryClipChangedListener(new ClipboardManager.OnPrimaryClipChangedListener() {
    @Override
    public void onPrimaryClipChanged() { }
});

Could you please give full steps to reproduce, including the app to run that is causing it?  The crash here shows it failing when setting the clipboard, which generally works; I need to to be able to see more specifically what this particular app is doing.

Also the API demo "Clipboard/Data Types" does use addPrimaryClipChangedListener() and doesn't have this problem, and the stack crawl originally shown doesn't have anything about addPrimaryClipChangedListener() in it, so there is some information I am missing.

Thanks!

What application are you trying to copy text from after adding a listener? I'm copying text from other apps like Messaging or Search and not the application the listener itself is from.

I have no idea if I'm on the right track, but my personal hypothesis is that this is caused because AppOpsService's uid verification is trying to verify the uid for the *listener's* application but the calling uid (Binder.getCallingUid()) is that of the application the text is being copied from. This leads to the permission check for UPDATE_APP_OPS_STATS which will obviously fail.

The code snippet I posted is basically the full "application" you should be able to reproduce this with. So this should be it:

1. Create a new Android app in $IDE_OF_CHOICE

2. Add a new OnPrimaryClipChangedListener in the onCreate of that application's activity -- it's contents don't matter

3. Install and launch the activity

4. Copy text from any other application

5. Crash.

I'm experiencing similar bug. for example, go to message app, tap and hold a message and copy text. the app will crash (the copy will save in clipboard though)

I have the same problem, I have an app that starts observing clipboard and since I updated to 4.3 that app crashes with similar exception to this from the first post (android.permission.UPDATE_APP_OPS_STATS)
then every other app that tries to copy something crashes with this exception:

W/dalvikvm(5446): threadid=1: thread exiting with uncaught exception (group=0x419c0700)
W/clipboard(431): Exception:
W/clipboard(431): java.lang.IllegalStateException: beginBroadcast() called while already in a broadcast
W/clipboard(431):       at android.os.RemoteCallbackList.beginBroadcast(RemoteCallbackList.java:229)
W/clipboard(431):       at com.android.server.ClipboardService.setPrimaryClip(ClipboardService.java:165)
W/clipboard(431):       at android.content.IClipboard$Stub.onTransact(IClipboard.java:62)
W/clipboard(431):       at com.android.server.ClipboardService.onTransact(ClipboardService.java:123)
W/clipboard(431):       at android.os.Binder.execTransact(Binder.java:388)
W/clipboard(431):       at dalvik.system.NativeStart.run(Native Method)
E/AndroidRuntime(5446): FATAL EXCEPTION: main
E/AndroidRuntime(5446): java.lang.IllegalStateException: beginBroadcast() called while already in a broadcast
E/AndroidRuntime(5446):         at android.os.Parcel.readException(Parcel.java:1439)
E/AndroidRuntime(5446):         at android.os.Parcel.readException(Parcel.java:1385)
E/AndroidRuntime(5446):         at android.content.IClipboard$Stub$Proxy.setPrimaryClip(IClipboard.java:171)
E/AndroidRuntime(5446):         at android.content.ClipboardManager.setPrimaryClip(ClipboardManager.java:125)
E/AndroidRuntime(5446):         at android.content.ClipboardManager.setText(ClipboardManager.java:208)
E/AndroidRuntime(5446):         at com.google.android.apps.authenticator.AuthenticatorActivity.onContextItemSelected(AuthenticatorActivity.java:927)
E/AndroidRuntime(5446):         at com.google.android.apps.authenticator.AuthenticatorActivity.access$200(AuthenticatorActivity.java:73)
E/AndroidRuntime(5446):         at com.google.android.apps.authenticator.AuthenticatorActivity$3.onActionItemClicked(AuthenticatorActivity.java:353)
E/AndroidRuntime(5446):         at android.widget.AbsListView$MultiChoiceModeWrapper.onActionItemClicked(AbsListView.java:6058)
E/AndroidRuntime(5446):         at com.android.internal.policy.impl.PhoneWindow$DecorView$ActionModeCallbackWrapper.onActionItemClicked(PhoneWindow.java:2569)
E/AndroidRuntime(5446):         at com.android.internal.app.ActionBarImpl$ActionModeImpl.onMenuItemSelected(ActionBarImpl.java:962)
E/AndroidRuntime(5446):         at com.android.internal.view.menu.MenuBuilder.dispatchMenuItemSelected(MenuBuilder.java:735)
E/AndroidRuntime(5446):         at com.android.internal.view.menu.MenuItemImpl.invoke(MenuItemImpl.java:152)
E/AndroidRuntime(5446):         at com.android.internal.view.menu.MenuBuilder.performItemAction(MenuBuilder.java:874)
E/AndroidRuntime(5446):         at com.android.internal.view.menu.ActionMenuView.invokeItem(ActionMenuView.java:547)
E/AndroidRuntime(5446):         at com.android.internal.view.menu.ActionMenuItemView.onClick(ActionMenuItemView.java:115)
E/AndroidRuntime(5446):         at android.view.View.performClick(View.java:4240)
E/AndroidRuntime(5446):         at android.view.View$PerformClick.run(View.java:17721)
E/AndroidRuntime(5446):         at android.os.Handler.handleCallback(Handler.java:730)
E/AndroidRuntime(5446):         at android.os.Handler.dispatchMessage(Handler.java:92)
E/AndroidRuntime(5446):         at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime(5446):         at android.app.ActivityThread.main(ActivityThread.java:5103)
E/AndroidRuntime(5446):         at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(5446):         at java.lang.reflect.Method.invoke(Method.java:525)
E/AndroidRuntime(5446):         at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737)
E/AndroidRuntime(5446):         at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime(5446):         at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager(431):   Force finishing activity com.google.android.apps.authenticator2/com.google.android.apps.authenticator.AuthenticatorActivity

or similar. Once I disabled clipboard monitoring app and rebooted Nexus 7 the copying worked for sometime.

[Comment deleted]

Yes, It's happening to my NEXUS 4 also. Once you launch any app monitoring clipboard then copying in any app crashes the app.

i've noticed that even if app crashes, copying still works and I can paste copied data. So I've changed code in my app to:

public static void setClipData(Context context, String text) {
        try {
                ClipboardManager clipboard = (ClipboardManager) context.getSystemService(Context.CLIPBOARD_SERVICE);
                ClipData clip = ClipData.newPlainText("", text);
                clipboard.setPrimaryClip(clip);
                Toast.makeText(context.getApplicationContext(), R.string.url_copied, Toast.LENGTH_SHORT).show();
        } catch (Exception e) {
                Toast.makeText(context.getApplicationContext(), R.string.url_copying_error, Toast.LENGTH_LONG).show();
                e.printStackTrace();
        }
}

But copying from contextual action bar still crashes and observing clipboard doesn't work at all. I think this is because of http://www.androidpolice.com/2013/07/25/app-ops-android-4-3s-hidden-app-permission-manager-control-permissions-for-individual-apps/ :)

Could someone *please* post complete steps to reproduce.  This means either:

(1) Attaching a complete code project that can be built and run to cause the problem to happen, or
(2) A pointer to an app on the play store to install with steps to reproduce in that app.

Thanks.

Diana Install https://play.google.com/store/apps/details?id=org.rojekti.clipper set it to have it monitoring in the notifaction bar then try copying anything from anywhere ;)

As I mentioned here[1], it happens on pretty much any app, Google's included, in example:

1. Open YouTube (I have version 4.5.17).
2. Open a video (any video).
3. Overflow menu > Copy URL

Same with GMail:

1. Open GMail (I have version 4.5.2-714156).
2. Open a conversation
3. Long press on text to action bar mode to appear
4. Tap on copy action


1. https://plus.google.com/103638111379552295023/posts/hZMgjN2qSUU

Diane,

I've attached a sample application. Like I mentioned before, it's just a blank activity that attaches a listener to the clipboard service.

Once you've built, installed and run this application and its activity, simply open any other application and copy something. For example, open Google Search, type anything in the search bar, copy it and a crash will occur.

The important part here is that the copying must occur in _another application_ separate from the listener. This causes the uid mismatch in AppOpsService's verifyIncomingUid and throws an exception.

Alternatively, install the Clipper application linked in #13, complete the tutorial so that it registers a listener, and copy from any other application. A crash will occur.

[Comment deleted]

S/MIME is currently supported by iOS 5+, Windows Mobile (6), Blackberry (with Enterprise-Deployment BES, individual user support is planned).

Microsoft announced to deliver S/MIME support into Windows Phone Mobile (8) http://www.infoq.com/news/2013/07/wp-8-vpn-smime 

Here is a list of corporations and institutions in Germanay that operate a PKI and/or use S/MIME within there internal and external (usually b2b) communication: https://gist.github.com/rmoriz/5945400#file-smime-md

It would be a huge step forward if Android could support this. I think general S/MIME support and reach in MUAs was never as good as today and we may have a historical chance to finally bring end-to-end-encryption to the masses! Thank you!

Basically it happens with any app monitoring clipboard. 100% reproducible and very much easy to repro.

1) install https://play.google.com/store/apps/details?id=net.daum.android.dictionary
2) launch the app
3) launch or switch to other app(Chrome, Gmail, ''') which has texts can be copied to clipboard
4) copy text then the app crashes.

Thanks for the help in reproducing!  We now have a fix.

I am also having this issue on the n
New Nexus 7 (2013)

Can confirm that my Nexus 7 2013 has this bug. Every time I copy the app being copied from crashes. Google or non-violent, makes no difference.

I am also having this issue on my Nexus 4 after the 4.3 update. I use the clipboard very often, the only way I find to solve the issue is to do a factory reset (Settings -> Backup & Reset -> Factory data reset)

Folks, there is no need to comment further. :)  This bug has been marked as fixed, as noted.

Not fixed on my Nexus 7 2013. Where is the note?

The bug may be fixed on some internal development version of Android, but in reality there are tens of thousands of affected devices out there right now. I am starting to get bad ratings over this bug and the clipboard is rendered unusable for many people.

When can we expect device updates to correct the issue? Are we talking about days, weeks or months? Will other device manufacturers ship the same broken code with their own updates?

Still experiencing this bug.

Bug still happening on my nexus 10.  

I have the same problem. Apps (Chrome, GMail, Phone) crashes after copying text. But after crash the text still in clipboard, and I can paste it. Nexus 4.

Still happening on my Nexus 7

Could someone shut down comments on this, please? :)
It's been marked as fixed, just not released yet.

@#30 nat.abbo...@gmail.com
and @ all googlers

shut down comments? why? Imho thousands of comments and complaints should pile here.

Breaking Copy and Paste is breaking one of the most basic properties of any computer system. It worked before, it worked when i bought the phone/tablet, and I want it back! ASAP

hack...@android.com said there is a fix. What is the problem to release the fix? Why is the OTA, that not all users have received yet, updated asap? Why not a second OTA (and that must be a really small one) to all 4.3 users? At the time of writing only NEXUS users are affected.
Do all the (e.g.) Samsung S4 users get the same bug when they receive the 4.3 update as veeti.paananen asked in post #25, or is it fixed there?

You broke it, you fix it, AND YOU SHALL DEPLOY IT ASAP!

But you don't care, right? Average time with google is 1.1 years I read this week. Fixing bugs is not in favour of your careers. Better working on new fancy features that the management ist focussing on. No older code gurus that live with the code and can maintain them.

tl;dr : Don`t call a bug fixed, before the fix is deployed

P.S.: Please excuse my bad english, I am not an native speaker and I not amused at this very moment

I'm not sure you understand how code works, or what this site is.

This is a developer issue tracker, for developers, not users who don't actually know what goes on behind the scenes.

You aren't helping anything or anyone by complaining, you're just spamming. Google reports that the issue is fixed, it just needs to be pushed to devices. Presumably, they're testing internally first, to ensure the fix is safe for a larger staged rollout.

They are deploying it ASAP. You know what that means, I assume? "As Soon As Possible." That doesn't mean immediately, it means once it is *possible* for them to safely deploy it.

tl;dr: stop spamming, you aren't helpful.

>I'm not sure you understand how code works, or what this site is.

I coded 6502 assembly on the Commodore C64 when you were still in the goolies (a word I learned right now) of your father.

>This is a developer issue tracker, for developers, not users who don't actually know >what goes on behind the scenes.

Hey insider, tell me, what goes on behind the scenes? Perhaps you can tell me why the new Motorola does not debut with 4.3 but 4.2 instead. Fights amongst googlers I heared?

>You aren't helping anything or anyone by complaining, you're just spamming. Google >reports that the issue is fixed, it just needs to be pushed to devices. Presumably, >they're testing internally first, to ensure the fix is safe for a larger staged >rollout.

Question: When should I report that I have a fix? When I think that I have a fix or when I tested that fix, so that it it worth to be called a fix?

>They are deploying it ASAP. You know what that means, I assume? "As Soon As >Possible." That doesn't mean immediately, it means once it is *possible* for them to >safely deploy it.

Yeah, I know the definition of ASAP, I also know snafu and fubar, both come in to my mind when I think of android development in the past year (-> and YES, this is spamming, but i fed the troll)
 
>tl;dr: stop spamming, you aren't helpful.

perhaps not helpful fixing this bug, but highlighting the bad situation android development faces right now. There are several (imho mission critical) bugs open for YEARS. But no one cares, new features, new features, thas's what they call for.

> Presumably, they're testing internally first, to ensure the fix is safe for a larger staged rollout.

Well, if that is the case, then how come you rolled out the 4.3 without fixing this bug? Clipboard management is such a basic part of the OS. It makes one wonder about the quality of the so called "internal testing".

BTW, aren't we, the so called "non-developers", supposed to report bugs here? Then don't we have a say on issues when we face one?

And please don't proclaim "Fixed", just saying "Fixed" gives a wrong idea. You could have rather said "Noted/Confirmed, will be fixed in future release", or something to that effect.

My 2p.

Just received an email about this very issue with one of my apps and 4.3. Yep definitely crashes. Hope Google rolls out a fix soon.

I have the same problem with Clipboard Monitoring on BlueDict.
Android 4.3

How lame is that!

also having this problem

I understand this issue has been marked as fixed but even after the recent update to Build JWR66Y I'm still having the clipboard bug, from what I've read online this minor update to 4.3 was supposed to fix the bug.  Not the case so far :(

My Galaxy Nexus got updated to the new build this morning. Its just been a few times that I have tested it, and apparantely this issue seems to be resolved. If other users could share their experience, it could help others.

FYI, I am using "ClipNote" app for Clipboard monitoring. I haven't tested with any other Clipboard monitoring app.

I've just installed the newest update to android 4.3, which reportedly contained the fix, but there is no change to the crash, and the copy-paste features still fail to function!

Why is the fix only on the 4.3_r2.2 branch and not on the 4.3_r1.1 branch? This seems to mean that the fix is only going out to the 2013 Nexus 7. Please push out this update to all Nexus devices.

As mentioned in my previous post, I am using Galaxy Nexus and there are no crashes on copying from any app (tested with GoSMS, WhatsApp, Gmail) after the update to JWR66Y, with "ClipNote" running in the background. But it seems that other users are experiencing crashes still.

Attaching 2 screenshots. First one shows the "About phone" screen and the second one shows the clippings that I copied without any crashes since last few days and the recent ones today.

I have a Nexus 4, Build JWR66Y I too am having the clipboard bug.

Oli

Got update. Still crash.

I think the fix is waiting for Apple approval:)))

Updated Nexus 7. Still clashes on copy.

Sent from my Android Nexus 7

Jim Flanagan
Cell:  773 396-4638
Beaver Island                    Chicago
219.448.2109                    773.463.5494
37700 Font View Ct.          4439 N.  California
Beaver Island, MI.              Chicago, IL.

I have a similar issue when sending a notification on a user's Galaxy Nexus running 4.3. Not sure how to reproduce this, I only see the crash with no user info. Here is he crash log:

java.lang.SecurityException: uid 10157 does not have android.permission.UPDATE_APP_OPS_STATS.
        at android.os.Parcel.readException(Parcel.java:1431)
        at android.os.Parcel.readException(Parcel.java:1385)
        at android.app.INotificationManager$Stub$Proxy.enqueueNotificationWithTag(INotificationManager.java:380)
        at android.app.NotificationManager.notify(NotificationManager.java:136)
        at android.app.NotificationManager.notify(NotificationManager.java:109)
        at com.levelup.touiteur.BackgroundTouitLoader$1.run(BackgroundTouitLoader.java:274)
        at android.os.Handler.handleCallback(Handler.java:730)
        at android.os.Handler.dispatchMessage(Handler.java:92)
        at android.os.Looper.loop(Looper.java:137)
        at android.app.ActivityThread.main(ActivityThread.java:5306)
        at java.lang.reflect.Method.invokeNative(Native Method)
        at java.lang.reflect.Method.invoke(Method.java:525)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:743)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:559)
        at dalvik.system.NativeStart.main(Native Method)

Updated to the most recent build.

My Nexus 4 can now copy from apps without crashing.
My Nexus 7 (1st gen) still crashes when copying.

Trying to track down the app that it triggering the crashing so I can uninstall it for the time being until the "fix" is fixed.

I can confirm, that

NotificationManager notificationManager = (NotificationManager)
...
context.getSystemService(Context.NOTIFICATION_SERVICE);
notificationManager.notify();

let GT-I9300, GT-I9505 crash with

.lang.SecurityException: uid 10140 does not have android.permission.UPDATE_APP_OPS_STATS

Nexus 4, Build JWR66Y. I can confirm that the problem persists basically with any app from which you want to copy and paste, let it be a google app or a third party app.

This type of bugs are unacceptable, start paying attention to details.

Me too: JWR66Y on Nexus 4, still crashes on copy.

Had this issue on my Play version of HTC ONE for 3 weeks now.  Last night I took a leap of faith and updated my Nexus 7 from a 4.3 to a newer 4.3 JWR66Y and also broken what was perfectly fine.

This is not a minor obscure function.  Its been marked fixed for over a month now and as of last night the bad update that WILL break your copy function is still being pushed OTA.  

Please be sensitive of the timing of this issue.  Nexus 7 2 already has issues, and the big Apple event is just next week.  This doesn't exactly bond well....

Hey google, you know why i bought an android phone in the first place?  Copy and paste.  I kid you not.  Please bump the priority on pushing this out and stop saying it's fixed until it's in our hands - until it's 'out' your job isn't done.  Thanks

Can anyone @ google confirm whether or not we'll see this fix before 4.4 KitKat?  Is that the cause of the delay in deployment?

I strongly hope the fix is released as a part of Android 4.3, not in KitKat
as soon as possible because:

* This issue is too serious. We don't want our app to be crashed by other
apps.
* We need to wait KitKat upgrade which will not be provided from carriers,
or provided after a year from the launch of KitKat
 2013/09/05 6:57 <android@googlecode.com>:

I can verify this with Nexus 4 and lastest Android update. First I thought that my qrcode scanner app is broken. But I was not: Because it copied the scanned text automatically to the clipboard the scanner app crashed after every scan. Other app with barcode or qrcode scanner like the Amazon app don't crash because they do not copy to clipboard.

Same issue on my Nexus 7, Android 4.3. The simple way fix it without ROOT:
1. find out what app have clipboard listening requirements, uninstall it.
2. reboot your device,that's all.

This clipboard issue appear on my device after i installed a app called Select Translator to it.

How exactly is one meant to determine what app has a clipboard listener installed?

"How exactly is one meant to determine what app has a clipboard listener installed?"

For non-techies like me that would be very useful to know. It might be that I can temporarily live without whatever app or widget is triggering this. Any advice on hunting down the culprit without wiping everything?