From e5c42621095a12e7d22ca5ab871dacd28c9bff41 Mon Sep 17 00:00:00 2001 From: Dianne Hackborn Date: Tue, 19 May 2015 16:04:04 -0700 Subject: Improve reporting to apps of transaction too large failures. If the app tried to do various things with too much data -- starting an activity, starting a service, sending a broadcast -- this would fairly silently fail with little indication of what was going on. Fix this in two ways: - Now when the native code generates a TransactionTooLargeException, it may include an additional message in it telling you how much data was in the parcel being sent, to help you understand why this happening. - In all the framework code paths where we call to the system and may fail, convert these failures into a a runtime exception and rethrow them back to the app so that it will clearly get the above message. Change-Id: I745159b97d3edb6fca86aa09cbc40c1f15a7d128 --- .../src/com/google/android/test/activity/ActivityTestMain.java | 9 +++++++++ 1 file changed, 9 insertions(+) (limited to 'tests') diff --git a/tests/ActivityTests/src/com/google/android/test/activity/ActivityTestMain.java b/tests/ActivityTests/src/com/google/android/test/activity/ActivityTestMain.java index fc66d6d..ddcfd9e 100644 --- a/tests/ActivityTests/src/com/google/android/test/activity/ActivityTestMain.java +++ b/tests/ActivityTests/src/com/google/android/test/activity/ActivityTestMain.java @@ -427,6 +427,15 @@ public class ActivityTestMain extends Activity { return true; } }); + menu.add("Transaction fail").setOnMenuItemClickListener( + new MenuItem.OnMenuItemClickListener() { + @Override public boolean onMenuItemClick(MenuItem item) { + Intent intent = new Intent(Intent.ACTION_MAIN); + intent.putExtra("gulp", new int[1024*1024]); + startActivity(intent); + return true; + } + }); return true; } -- cgit v1.1