You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When introducing robospock into the my test project, android studio is no longer able to navigate to the actual R file value definitions, as defined in xml, or the layout definitions. i.e. If I have the following project structure
- app
- unit-test (robospock)
then when I'm in say an activity and ctrl-click from an R reference to get to the actual definition, android studio takes me to the r.class file instead of the actual definition. I can only think that somehow, adding the main apps java source sets as source sets in the the 'unit-test' project confuse studio in some way.
Any suggestions as to how to resolve this? I've experimented with adding just the main apps classpath and output dir as a classpath dependency of the test-app and although the tests run, we loose the nicety of source file -> test file navigation via the ide. Any suggestions would be appreciated...
The text was updated successfully, but these errors were encountered:
When introducing robospock into the my test project, android studio is no longer able to navigate to the actual R file value definitions, as defined in xml, or the layout definitions. i.e. If I have the following project structure
then when I'm in say an activity and ctrl-click from an R reference to get to the actual definition, android studio takes me to the r.class file instead of the actual definition. I can only think that somehow, adding the main apps java source sets as source sets in the the 'unit-test' project confuse studio in some way.
Any suggestions as to how to resolve this? I've experimented with adding just the main apps classpath and output dir as a classpath dependency of the test-app and although the tests run, we loose the nicety of source file -> test file navigation via the ide. Any suggestions would be appreciated...
The text was updated successfully, but these errors were encountered: