available-version-codes.txt not found after upgrading to the latest Bugsnag plugin #940
Comments
|
Yeah, the problem is these changes: bugsnag/bugsnag-android-gradle-plugin@27592a9#diff-0b3ba5e394543c53bbd77a52b87f07c4ff12e47518f2f3b26f1cd28f8246d7fc. They're using the old ApkVariantOutput which forces the version code to be resolved. They'd need to switch to the Provider based API. |
|
Thanks for taking a look @SUPERCILEX! cc @yousif-bugsnag |
|
This issue has been automatically marked as stale because it has not had recent |
github-actions
bot
added
the
waiting-for-reply
|
I'm getting same error when running gradle tasks such as -FAILURE: Build failed with an exception.
* Where:
Script '/Users/hivetechltd/Documents/human/roto-native/node_modules/@sentry/react-native/sentry.gradle' line: 167
* What went wrong:
java.io.FileNotFoundException: /Users/User/Documents/react-native/myapp/android/app/build/intermediates/gpp/release/available-version-codes.txt (No such file or directory)
> /Users/User/Documents/react-native/myapp/android/app/build/intermediates/gpp/release/available-version-codes.txt (No such file or directory)
Problem happened after I upgraded react-native version, which requires a new gradle version as well (7.3 compared to previous 6.5) and since I was using older version of gradle-play-publisher plugin (2.2.1), i was getting an error when running -* What went wrong:
A problem was found with the configuration of task ':app:publishReleaseBundle' (type 'PublishBundle').
- In plugin 'com.github.triplet.play' type 'com.github.triplet.gradle.play.tasks.PublishBundle' property 'outputDir' is annotated with @PathSensitive but that is not allowed for 'OutputDirectory' properties.
Reason: This modifier is used in conjunction with a property of type 'OutputDirectory' but this doesn't have semantics.
Possible solution: Remove the '@PathSensitive' annotation.
Please refer to https://docs.gradle.org/7.3.3/userguide/validation_problems.html#incompatible_annotations for more details about this problem.I have no choice now but to update triplet plugin which i did and now i get same error situation as with Bugsnag plugin in this github issue, although in my situation it is issue with sentry package @SUPERCILEX How can it be that it works well with older version of |
|
Hi, @n-kulic. Were you able to resolve this issue? I just started helping out on a React Native project (running 0.67.4), and I'm seeing the following issue since upgrading The app is using Gradle Play Publisher like this. app/build.gradle build.gradle I'm new to Gradle Play Publisher, and still figuring out the app, but any pointers would be much appreciated. Thanks! |
|
@darrylyoung I used And in |
|
Thanks, @n-kulic. That's much appreciated. I'll give it a go. |
|
This is still a problem with version 3.8.1 |
|
I have created an issue in the sentry-react-native project, because I think they have to implement a fix for this. |
|
I'm having this issue and we are not using react native or bugsnag. |
Describe the bug
I originally filed an issue against Bugsnag (bugsnag/bugsnag-android-gradle-plugin#383) but got told that this might be a gradle-play-publisher issue.
We're using gradle-play-publisher in combination with bugsnag-android-gradle-plugin. The setup for gradle-play-publisher looks like this:
After upgrading bugsnag-android-gradle-plugin to version 5.7.5 we started seeing the following error whenever
publishInternalReleaseBundleis invoked:The issue is reproducible locally with:
The theory is that a recent change (potentially this one: bugsnag/bugsnag-android-gradle-plugin#375) in Bugsnag's plugin is triggering premature initialization of gradle-play-publisher in the wrong build phase, but I'm hoping to get some help troubleshooting this.
Versions
Tasks executed
Expected behavior
The plugin doesn't look up the
available-version-codes.txtduring configuration phase, which IIUC isn't supposed to be there that early.Additional context (if a crash, provide stack trace)
Full stacktrace
The text was updated successfully, but these errors were encountered: