Closed andrewsardone closed 9 years ago
It's far from a solution, but my current hack is to key off of a static flag for whether or not we've loaded the module :shame:
Oh.
I throw this exception to prevent people from initializing Iconify in every activity instead of just once in the application. I didn't think about tests instantiating multiple applications. I'll change this behavior in the next release, adding twice the same font would do.. well, nothing.
Fixed in 2.0.9 released just now.
This is more of a question / out-loud-thinking to see if anyone has come across this issue, or if anyone sees any obvious mistakes I have made.
I have a simple
android.app.Application
subclass which registers myIconify
modules within theonCreate()
implementation (per the README instructions). Everything works and runs fine in a normal context, but all of my JUnit tests (ran with Robolectric) are throwing exceptions:Has anyone come across this? Any ideas on how to fix the issue? Apologies for the lack of details; just not sure where to go next. Thanks!