firebase-messaging build error on windows #5966
Comments
|
I found a few problems with this issue:
|
|
Hi @xspeed1989, thank you for reaching out. I'm having difficulty in reproducing the issue. Could you share an MCVE to help us investigate the issue? Thanks! |
|
Hey @xspeed1989. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically. If you have more information that will help us get to the bottom of this, just add a comment! |
I am new to android and java , what is MSVE |
|
cfgFile is D:\somepath\to_file Content after the colon is truncated |
|
MCVE stands for minimal, complete and verifiable example. You can check this StackOverflow post for more information. Also, could you the steps how to reproduce the issue? |
|
OS:WINDOWS 11 X64
Android Studio Jellyfish | 2023.3.1
1. git clone --recurse-submodules
***@***.***:firebase/firebase-android-sdk.git
(commit:091e1e19e9852113e90285c2ff8bc5dcfd6379ab)
2. build firebase-messaging from android studio build menu
lehcar09 ***@***.***> 于2024年5月24日周五 23:37写道：
… MCVE stands for minimal, complete and verifiable example. You can check
this StackOverflow post
<https://stackoverflow.com/help/minimal-reproducible-example> for more
information. Also, could you the steps how to reproduce the issue?
—
Reply to this email directly, view it on GitHub
<#5966 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHMPLQKN3J23O2PSNQVDCTZD5NCRAVCNFSM6AAAAABHXINOCKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRZHA2DKOBYG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Thank you for the details you shared. I tried to reproduce the issue using my machine, however, I wasn't able to reproduce the issue. I noticed that the commit ID you shared is not the latest commit in the repository. Could you try updating up to the latest and check if the issue persists? In the meantime, I'll notify our engineers to further investigate the issue and see what we can do here. |
|
Hey @xspeed1989. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically. If you have more information that will help us get to the bottom of this, just add a comment! |
I try it with latest commit(7a313c3), have the same problem. ./gradlew -PprojectsToPublish="firebase-messaging" publishReleasingLibrariesToMavenLocalExecution failed for task ':firebase-messaging:generateReleaseProto'.
Try:
|
|
@lehcar09 ./gradlew -PprojectsToPublish="firebase-messaging" publishReleasingLibrariesToMavenLocal --stacktrace Execution failed for task ':firebase-messaging:generateReleaseProto'.
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. For more on this, please refer to https://docs.gradle.org/8.4/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation. BUILD FAILED in 4s |
|
Since there haven't been any recent updates here, I am going to close this issue. @xspeed1989 if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this. |
Android Studio version:
Android Studio Jellyfish | 2023.3.1
Build #AI-233.14808.21.2331.11709847, built on April 13, 2024
Runtime version: 17.0.10+0--11572160 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows 11.0
GC: G1 Young Generation, G1 Old Generation
Memory: 4096M
Cores: 20
Registry:
ide.experimental.ui=true
Non-Bundled Plugins:
com.intellij.plugins.vscodekeymap (233.11799.188)
Firebase Component: messaging
Component version: 24.0.1
Describe the problem
[24.0.1](protoc: stdout: . stderr: --firebaseEncoders_out: com.google.firebase.encoders.proto.codegen.InvalidConfigException: Config file 'D' does not exist or is a directory.)
The text was updated successfully, but these errors were encountered: