Have you been able to reproduce this issue yourself? Is there any more context on how to reproduce this (steps), or do you just have the reports from Google Play?
Ajay: I do not have an LG device. I have given you all the information I have – even a Play Store bug console screenshot!
Have you looked at your Android code in question in the Corona runtime? What happens when you test this app on a LG device?
Hi Corona273,
I am receiving same issue with same logs as u received from playStore. I have attached screenshot and logs below.
What i am doing is copying text to clipboard using pasteboard plugin… which i think is creating crashes between corona and android layer… whats ur thoughts in this…
And plz help me if you find any solution in this…
Thanx in advance.
Sajid Zeb
These are the logs:
java.lang.NullPointerException
at
plugin.pasteboard.ClipboardListener$ApiLevel11$1.run(ClipboardListener.java:64)
at
android.os.Handler.handleCallback(Handler.java:733)
at
android.os.Handler.dispatchMessage(Handler.java:95)
at
android.os.Looper.loop(Looper.java:136)
at
android.app.ActivityThread.main(ActivityThread.java:5103)
at
java.lang.reflect.Method.invokeNative(Native Method)
at
java.lang.reflect.Method.invoke(Method.java:515)
at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:606)
at
dalvik.system.NativeStart.main(Native Method)
Sajid: This is a Corona SDK runtime bug. Corona staff need to fix it. There is nothing we can do. It is in their hands.
same here:
my log from the playstore:
java.lang.NullPointerException
at plugin.pasteboard.ClipboardListener$ApiLevel11$1.run(ClipboardListener.java:64)
at android.os.Handler.handleCallback(Handler.java:733)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:136)
at android.app.ActivityThread.main(ActivityThread.java:5118)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:515)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:794)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:610)
at dalvik.system.NativeStart.main(Native Method)
i have an LG G3 phone and my app crashes on startup on my phone, on my friend’s phone this does not happen.
please help im getting tons of requests to fix this error
So we have three different Corona SDK developers reporting the identical ClipboardListener.java crash providing plenty of documentation and logs, but no confirmation of a fix date from Corona staff after over a week.
Ajay: Can you tell us when this will be fixed in a daily build? Unfortunately I don’t see it in today’s 2015.2733. 
Has anyone filed a bug report? We do not track bugs in the forums.
Rob
Rob: I can think of plenty of examples over the last few years when Corona staff have tracked (and fixed) bugs in the forums without a formal bug report being filed.
But far be it from me not to follow proper procedures!
It is case 43402.
Your right. The build server problems this week was fixed (or is being fixed) with out a bug report. The whole community not being able to build is a high level bug and we report them, they tend to get fixed quickly. Sometime we ask the Engineers if there is a work around to a problem in the forums and the issue is obvious and something that needs fixed now. But more often than not, the bugs require research or are edge cases that we simply can’t go “Oh, that’s it”. If it was that simple we would have fixed it already. So if its not a bug that will be fixed immediately because it has wide spread impact and it’s going to take time to do, the only way we can track it, assign it to engineers, make sure we have all the relevant information is to use a bug tracker.
Thanks, Rob. I didn’t mean to be snarky, and I think my message could have been read that way. For a while I was posting bugs here and they were magically getting fixed without me having to file a bug report, so I think I got a bit lazy!
In any case I hope this can be fixed soon. It is very bad when the Corona SDK runtime crashes on popular Android devices.
Hi everyone,
We’ve just pushed out an update to the Pasteboard plugin that resolves a device-independent issue that can cause the crash detailed in the Google Play reports you’ve all sent.
From our experimentation with an LG G3 device, we believe that this issue has only been reported on LG devices because they add some data to the Android clipboard in a way no other devices do.
Long story short, we’ve fixed what we believe the fundamental issue was given the sparse data. However, getting some more data points on the behavior from you guys would help us confirm this.
@bsadambs: Since you have a LG G3 device, can you confirm that this resolves the behavior you’re experiencing?
The fix is in our Pasteboard plugin, so if you perform a new device build of your project on Android, you should just get the fix.
Lastly, the Pasteboard plugin code is open-source and available here. Here’s the relevant commit for those that are curious about what changes were made.
Thanks, folks. I have submitted the new version to the play store using today’s daily build. Now to see if we still get crashes!
seems to be working on my LG G3.
Will post to play store