VirgilSecurity / react-native-virgil-crypto

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

No signature of method: org.apache.groovy.json.internal.LazyMap.plus() is applicable for argument types: (String) values: [/blob/master/LICENSE] Possible solutions: plus(java.util.Collection), plus(java.util.Map), put(java.lang.String, java.lang.Object), values(), values(), put(java.lang.Object, java.lang.Object)

VEmpink opened this issue · comments

When I commented on the code at react-native-virgil-crypto/android/build.gradle' line: 96 the error is gone, what's the purpose of the code at that line? Is that ok when I remove that code?

Getting this error message:
A problem occurred configuring project ':react-native-virgil-crypto'. No signature of method: org.apache.groovy.json.internal.LazyMap.plus() is applicable for argument types: (String) values: [/blob/master/LICENSE] Possible solutions: plus(java.util.Collection), plus(java.util.Map), put(java.lang.String, java.lang.Object), values(), values(), put(java.lang.Object, java.lang.Object)

Any solution?

commented

Is there a solution for this?? Can someone please comment on it?

Hi nnaren1902,
We will try to reproduce and reply as soon as possible.
Please, could you provide more details ? (react native version, or maybe project sample)

@mbalyaba I am experiencing the same problem. To provide some further information:
"react-native": "0.64.0",
"@virgilsecurity/e3kit-native": "^2.4.3",
"@virgilsecurity/key-storage-rn": "^1.0.0",
"@react-native-community/async-storage": "^1.7.1",
"react-native-virgil-crypto": "^0.5.0", (Tried 0.6.1 as well)

I was able to trace the error to > \node_modules\react-native-virgil-crypto\android\build.gradle > line: 96 >
url packageJson.repository + '/blob/master/LICENSE'

In line 96 it tries to get the url from the package-json in \node_modules\react-native-virgil-crypto\ for the repository but repository is a json object instead of the expected url. Therefore line 96 in the build.gradle should be:

url packageJson.repository.url + '/blob/master/LICENSE'

any luck this error is still exist

@razamerchantwork as far as I know it does. We ran a patch on it to get rid of this error during buildtime and would advise to do that as well.

What patch did you use?

So, this bugs occurs when you use node 14 and is fixed by using node 16 🤘.