We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Always
When run the project facing below issue:
Could not resolve all artifacts for configuration ':classpath'. Could not find io.realm:realm-gradle-plugin:6.0.1. Searched in the following locations: - https://dl.google.com/dl/android/maven2/io/realm/realm-gradle-plugin/6.0.1/realm-gradle-plugin-6.0.1.pom - https://dl.google.com/dl/android/maven2/io/realm/realm-gradle-plugin/6.0.1/realm-gradle-plugin-6.0.1.jar - https://jcenter.bintray.com/io/realm/realm-gradle-plugin/6.0.1/realm-gradle-plugin-6.0.1.pom - https://jcenter.bintray.com/io/realm/realm-gradle-plugin/6.0.1/realm-gradle-plugin-6.0.1.jar - https://repo1.maven.org/maven2/io/realm/realm-gradle-plugin/6.0.1/realm-gradle-plugin-6.0.1.pom - https://repo1.maven.org/maven2/io/realm/realm-gradle-plugin/6.0.1/realm-gradle-plugin-6.0.1.jar
No response
SDK 11
Local Database only
Yes
MAC OS
Which debugger for React Native: ..
The text was updated successfully, but these errors were encountered:
➤ PM Bot commented:
Jira ticket: RJS-2901
Sorry, something went wrong.
This is the repository holding the code for the Javascript SDK, whereas your issue appears to be related to the Java/Kotlin SDK.
No branches or pull requests
How frequently does the bug occur?
Always
Description
When run the project facing below issue:
Stacktrace & log output
No response
Can you reproduce the bug?
Always
Reproduction Steps
No response
Version
SDK 11
What services are you using?
Local Database only
Are you using encryption?
Yes
Platform OS and version(s)
MAC OS
Build environment
Which debugger for React Native: ..
Cocoapods version
No response
The text was updated successfully, but these errors were encountered: