Windows, SDK 2.0.0 and 2.0.1, reported by both myself and joyrider3774:
A band-aid (sledgehammer) that used to work (it's been a while since I worked with the framework) to shut this sort of stuff up would be to add this to the top/entry of the method with the issue:
: wxLogNull logNo; // suppress wxLog error messages within this scope... :
... that, or figure out what it takes to satisfy the assert condition
Let us know what it turned out to be... inquiring minds want to know!
This is a known issue and will be fixed in the next release, thanks for the report!