Hello brilliant developers :grinning: Could someon...

# android

[Mohammadreza Khahani]

Hello brilliant developers 😀
Could someone help me by answering my simple question on Stackoverflow? 🙏

[Jonny]

That works fine for me without using "invoke". No complaints about unused parameter.

[Mohammadreza Khahani]

@Jonny Thanks for your response. 🙏

Could you confirm there is no such warning after doing code analysis by Android Studio because there are no compiler complaints about it but you can see the warning by doing Inspect Code.

[Jonny]

When I run code analysis I get that warning as well. I have a bunch of callbacks in my composable method and two of them have the same warning. They are the only callbacks with arguments. So I believe there's an issue with code inspection when there are callbacks with arguments.

[Mohammadreza Khahani]

You're right. It only occurs for callbacks with arguments. 💪

Do you have any idea how to satisfy the code inspection without using the invoke calls?

[Jonny]

Nope.

[Mohammadreza Khahani]

Thanks for your valuable time to help me. 🙏

[Jonny]

Create an issue at google and they'll probably solve it eventually.

[Jonny]

No problem. 😄

[Mohammadreza Khahani]

Thanks for your great idea to report the issue. 🙏
Someone came up with an answer to my question referring to an issue related to the problem on the Google issue tracker and I commented on it.