8000 KSTypeArgument.type should not have been null crash during KSP processing with star projections · Issue #2426 · google/ksp · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

KSTypeArgument.type should not have been null crash during KSP processing with star projections #2426

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.

Sign up for GitHub

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

Jump to bottom
Closed
fauzangifari opened this issue Apr 24, 2025 · 2 comments
Closed

KSTypeArgument.type should not have been null crash during KSP processing with star projections #2426

fauzangifari opened this issue Apr 24, 2025 · 2 comments

Comments

@fauzangifari
Copy link

When running the KSP task for a Kotlin module, I encountered a crash with the message:
KSTypeArgument.type should not have been null, please file a bug. STAR null

This happened during the :favorite_feature:kspDebugKotlin task.

Environment:

  • Kotlin version: 2.0.21
  • KSP version: 2.1.20 -2.0.0
@ting-yuan
Copy link
Collaborator

Can you share more details, like a small test project?

On the other hand, it looks like the error message was from Dagger / Hilt. It may worth try updating the version of Dagger / Hilt.

@fauzangifari
Copy link
Author

I’ve found the solution the issue was caused by applying the Hilt plugin in a Dynamic Feature Module, which is not supported. I removed the plugin and just used implementation and kapt for the dependencies.

Thanks a lot for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ting-yuan @fauzangifari
0