-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using Rigger in kotlin activities/fragments is throwing Runtime exception #24
Comments
@manikantagarikipati Do you turn off |
Yes I have turned it off!. My Activity Annotation:
Also I've added all the AOP Plugins and the dependencies. |
that's weird, have you tried to clean your project ? that could be useful. if not, please show me your gradle version. |
Yeah felt the same, I've cleaned it couple of times/ invalidate caches and all sort of playing around with it but in vain. Here is my gradle version.. And my compile and target android versions:
Also I've faced this issue when trying to flash the apk in device: Let me know if you need any further information info that i can provide.. |
Sorry, i can't reappear this error with your gradle configuration. please give me the full gradle configuration with About the second error, you can try add https://stackoverflow.com/questions/47137483/android-studio-3-0-dexarchivebuilderexception |
getRigger的时候rigger为空 |
@Yhao90 抱歉,我这边无法重现该错误,请贴出你的根目录和module下的 |
I'm having the same problem.
Fragment class:
|
I found the problem,You need to update the library and add support for androidX.I don't know how you've written it but it shouldn't be so hard just letting androidX fragment and Activities be used.Remembering that androidX is nothing but naming convention packages.Not different code. |
java.lang.RuntimeException: Unable to start activity ComponentInfo{MyAppCompatActivity.class}: com.jkb.fragment.rigger.exception.RiggerException: UnKnown error MyAppCompatActivity@16f1f3 is not added into rigger. please check your config or contact author.
The text was updated successfully, but these errors were encountered: