Strange, execution-breaking assertions

What steps will reproduce the problem?
1. Install on device that doesn't ignore assert statements
2. Try to create or open any database

Please provide any additional information below.

com.keepassdroid.utils.Util.java has two methods, getEditText() and 
setEditText() which have strange contradicting assertion statements. Each will 
first assert that an input parameter is explicitly not null, then provide 
conditional behavior based on nullness.

While this is ignored on most devices in published distributions, it means 
certain and constant failure on any device that has assertions enabled. Every 
time I reboot my phone, or debug any of my own code, I have to run a 

adb -d shell setprop assert 0

to be able to run KeePassDroid. I love your app, so this makes me sad. :(

Are these asserts for some reason intentional for your own debugging process, 
or can they be removed?

Original issue reported on code.google.com by garyspre...@gmail.com on 8 Oct 2013 at 10:35

Attachments:

utilAsserts.patch

dckc / keepassdroid

Strange, execution-breaking assertions #606