Print the contents of a Bundle to Logcat?

Question

Is there an easy way to print the contents of a Bundle to Logcat if you can\'t remember the names of all the keys (even being able to print just the key names w

Answer 1

Realize that this isn't answering the question exactly, but I see allot of developers trying to dump the contents to logcat/console because they are not aware that they can set up in Android Studio debugger to display customized object rendering at debug time, when you hit a break point. And in the case of Bundle, you can take the type of code shown in the other answers here, and apply that as a custom renderer, so that you don't need to pipe the dump to logcat and/or the console.

(These instructions are from Android Studio 3.1.3 (June 2018) ...

1. Select the "File" and then the "Settings" menu option/suboption.
2. In the 'Settings' dialog, on the left side, drill-down and select "Build, Execution, Deployment", "Debugger", "Data Views", "Java Type Renderers".
3. Right side of the dialog, where it says "Renderer name" enter a name you wish to identify with the renderer you are creating.
4. Right side of the dialog, where it says "Apply renderer to objects of type", enter 'android.os.Bundle'.
5. Right side of the dialog, under the "When rendering a node" section, select the "Use following expression:" radio button.
6. In the text field below that, type in the following ...

StringBuilder builder = new StringBuilder();
for (String key : ((android.os.Bundle)this).keySet()) {
    Object value = ((android.os.Bundle)this).get(key);
    builder.append("[");
    builder.append(key);
    builder.append("]=[");
    builder.append(value);
    builder.append("](");
    builder.append((value != null) ? value.getClass().getSimpleName() : "null");
    builder.append("), ");
}
return builder.toString();

5. Press 'Apply'/'OK' button.

Now, when you run your app, and you hit a breakpoint that shows a variable that is of type android.os.Bundle, you'll see the output generated from the above code, on the variables section of the debugger window.

I'll also include a screenshot, showing what I described above ...