Status Update
No update yet.
Comments
si...@google.com
This mentioned interface was removed only starting 7.2, so you shouldn't have problems with using firebase with AGP 7.1. Are you sure you don't have a dependency somewhere (maybe buildSrc?) on AGP or just gradle-api 7.2?
si...@google.com
I looked in ~/.gradle/caches/modules-2/files-2.1/com.android.tools.build/gradle-api and ~/.gradle/caches/modules-2/files-2.1/com.android.tools.build/gradle
Only 7.1.0-beta04 and 7.1.0-beta05 is there.
I checked with a new project. This problem only occurs when I enable the com.google.gms.google-services
and com.google.firebase.firebase-perf plugin.
Without these plugins everything works fine.
Ti...@pplsi.com
This is a known issue, we are working with those teams so they release a compatible plugin.
Ti...@pplsi.com
Ti...@pplsi.com
si...@google.com
Last communication from firebase-perf team stated a release is scheduled for this week.
Ti...@pplsi.com
But it looks like not only perf but androidx.navigation.safeargs.gradle.SafeArgsPlugin also has this issue.
si...@google.com
Yep, androidx.navigation.safeargs.gradle.SafeArgsPlugin seems to be an issue too.
si...@google.com
si...@google.com
safegargs will be fixed with the next jetpack release which is currently scheduled for end of January.
sorry it is taking so long, the holidays have delayed many releases.
si...@google.com
Ti...@pplsi.com
firebase perf still has the issue, but I just removed that plugin for now as it requires no app side changes. instead I just commented it out. google-services 4.3.10 does not seem to be an issue.
I was able to get by the nav plugin issue by using a new snapshot:
buildscript {
repositories {
google()
mavenCentral()
maven("https://androidx.dev/snapshots/builds/8054565/artifacts/repository")
}
}
then update the plugin to
classpath("androidx.navigation:navigation-safe-args-gradle-plugin:2.5.0-SNAPSHOT")
I don't know whether I should update the rest of my nav deps to 2.5.0 snapshot, but this'll do for now.
Ti...@pplsi.com
Firebase has published perf-plugin 1.4.1 which includes the fix to this issue
Description
Please provide as much information as possible. At least, this should include a description of your issue and steps to reproduce the problem. If possible please provide a summary of what steps or workarounds you have already tried, and any docs or articles you found (un)helpful.
Problem you have encountered: When someone asks our chatbot a question, the chatbot may or may not respond. We started having this issue in February 2023 and it has been ongoing. We currently have two bots and both are experiencing the same issues.
When the bot doesn't respond, we can check the training screen and it will not reflect the activity on the user-activity side either.
This also impacts the "welcome" message that is supposed to generate to each user upon opening our chatbot screen. Each user should receive a welcome message which currently they may or may not receive. We can confirm they're not receiving this by viewing the user-activity in our training tab. There's an increase of messages that are not connected with our "welcome" intent.
What you expected to happen: A confirmation that there's an issue and that it's being resolved or steps on how to resolve the issue if it's something on our end as we have not changed anything within our settings or functionality.
Steps to reproduce: Simply engage one of our bots, they may or may not respond.
Other information (workarounds you have tried, documentation consulted, etc): N/A we've tried accessing our chatbots from different locations thinking it may be a connectivity with the location they're hosted on but each platform is experiencing the same outcomes.