Eric Kuxhausen

I can't believe this issue isn't more public. Took me an entire afternoon to isolate this issue in a codebase I'm backporting with ABS

Hmm I'm able to reproduce when compiling master, but not on the last release build pushed to the Play Store. It is possible this crash was introduced when I recently...

User comment: "failed to open" Argument parameters now being printed as of version 83: ``` java.lang.IllegalArgumentException: 25170801,'27445218 java.lang.IllegalArgumentException: 19918511,'1027017114 java.lang.IllegalArgumentException: 3159608,'28272026 java.lang.IllegalArgumentException: 6420974,'361668141 ```

Confirmed still an issue, though the line number changed. LampShade version: 79, 80 Android version: 4.2, 4.4, 5.0, 5.1 Devices; mx4, Xperia Z2 (D6503), Nexus 5 (hammerhead), MeMO Pad HD...

Moods are the only user content that LampShade supports exporting/importing today (as URLs through the standard Android sharing system). Power users have been working around this limitation by using apps...

This may be messy to fix http://stackoverflow.com/questions/1109022/close-hide-the-android-soft-keyboard

Potentially also a duplicate of #69

I propose as best practice titling issues with the crashing exception to make it easier to manage crash reports / prevent duplicates

In the past month, Google Play has collected 17 'unique' crashes, but some of them have already been fixed in newer versions of LampShade and others are duplicates of open...

Many crash reports come through Google Play without enough data to justify a title of anything other than the crashing exception, so at least some bugs will be titled that...