<ContentAlreadySetError> cc.: <@UQHPVEAJV> Can you...
# compose
j
ContentAlreadySetError cc.: @Jelle Fresen [G] Can you elaborate a little bit on that? Why is that always bad? We have a test that perfectly worked pre 1.2.0-rc01 and now breaks with this exception. (more details in the thread) Whats the alternative?
We take our MainActivity and set the content again with another user state (to be logged in etc). Currently we need an android compose rule because of getString (could be replaced with
Copy code
InstrumentationRegistry.getInstrumentation().targetContext
) and some other stuff, otherwise I considered using a regular compose rule.