-
Notifications
You must be signed in to change notification settings - Fork 26
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
Build failed - android #14
Comments
@M-HARIS-97 it sounds like you're using a newer version of react-native that is using gradle 8? If I'm reading that error correctly, this is an issue with a newer version of gradle? |
@jspizziri Pls check the following;
|
@M-HARIS-97 I saw that, but I've not seen that build error before. So its either a problem with how you're building it, or its a problem with the upstream dependency suddenly being broken. My guess is that it's the first option. |
@jspizziri This is my current version details. I am following the official document (https://github.com/5-stones/react-native-readium#installation) for installing readium and trying to take a build for android. At that time I got this error :) |
@jspizziri Pls check the following for the detailed description;
|
@M-HARIS-97 do you get the same issue when attempting to build the example project? |
@jspizziri Example project means? |
@jspizziri Same issue Pls check this NanoHttpd/nanohttpd#634 |
@jspizziri issue fixed. Added some code changes to android/build.gradle file. Please refer to the following image for more information |
@M-HARIS-97 this looks like something that would need to be changed in this repo, correct? If so could you open a PR? |
@jspizziri I think it has to do with the new version of RN. So no need to change the repo. |
There's more information on this in the readium migration docs here https://github.com/readium/kotlin-toolkit/blob/main/docs/migration-guide.md#221 I'm going to upgrade to |
…tpd dependency a dependency of the kotlin-toolkit was removed from maven which caused new builds to break. this resolves that issue #14
@M-HARIS-97 I just released a patch version |
@jspizziri OK, Thanks for your response. |
@jspizziri The problem is encountered again. |
@M-HARIS-97 can you try running it again? I've seen issues like this with temporary outages with jitpack.io |
@M-HARIS-97 I just confirmed, jitpack is having an outage, there are a number of errors attempting to reach other unrelated packages. I'm sure they'll have it resolved in the next few hours. |
@jspizziri I also confirmed. I think |
@M-HARIS-97 I don't know if that would solve the issue? I imagine www is just an alias for the non-www site, not separate servers. If they are separate I'd imagine both of them would have issues simultaneously, but if I'm wrong about that please send me some docs on it. |
@jspizziri I've seen some discussion around this on Git (Link), Thats why I'm asking |
both gets down together |
The plan is to migrate the Kotlin toolkit to Maven Central next year, because JitPack is becoming more and more unreliable. |
@jspizziri @mickael-menu It's still down. Is there any solution to fix it? |
@jspizziri @mickael-menu Its back |
Could not determine the dependencies of task ':react-native-readium:compileReleaseAidl'.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.3.3/userguide/command_line_interface.html#sec:command_line_warnings
The text was updated successfully, but these errors were encountered: