-
-
Notifications
You must be signed in to change notification settings - Fork 86
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
[super_clipboard] Can't build as a flutter module #379
Comments
If you can make a PR for cargokit that would be very welcome. Otherwise this will be resolved once things get migrated to native assets (currently experimental in Flutter). That way cargokit will no longer be required. |
Hello, i have the same issue. |
My temporary solution is to change the source in the pub cache folder lol. Sent from my iPhoneOn May 31, 2024, at 19:07, tibo-lumapps ***@***.***> wrote:
Hello, i have the same issue.
I saw you made a PR, did you find any temporary fix for now ?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
@knopp I've already submitted the PR. Would you mind to take a look? It's a minor change and should be pretty safe. |
When build as a flutter module and integrated into the existing android project, there is no applicationVariants and result in following compilation failure: Could not get unknown property 'applicationVariants' for extension 'android' of type com.android.build.gradle.LibraryExtension. In such case, we will use libraryVariants instead superlistapp/super_native_extensions#379 --------- Co-authored-by: Ji Fang <[email protected]>
@jifang, thank you. I merged it in cargokit, I'll try to release updated irondash_engine_context and super_native_extensions today. |
Should be fixed in 0.8.17. |
When build the super_clipboard as a flutter module and integrate into the existing android project, I am getting the following error
Not only the irondash library, the
super_native_extensions-0.8.16/cargokit/gradle/plugin.gradle
has the same problem.It looks like that the gradle plugin assumes that it must be part of an application target. This issue can be fixed by modifying the gradle script like following
Is there a non intrusive way to solve this issue?
The text was updated successfully, but these errors were encountered: