Assigned
Status Update
No update yet.
Comments
se...@google.com
se...@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?
ka...@gmail.com
I checked the project and there is no reference to AGP 7.2
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.
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.
se...@google.com
This is a known issue, we are working with those teams so they release a compatible plugin.
is...@google.com
jp...@google.com
js...@gmail.com
Thanks!
rt...@gmail.com
When can we expect an update on this?
jo...@nfa.cz
Last communication from firebase-perf team stated a release is scheduled for this week.
th...@gmail.com
But it looks like not only perf but androidx.navigation.safeargs.gradle.SafeArgsPlugin also has this issue.
Description
From
Please create a new issue, if you are interested in this.inA short description of the request:
As a future request, I would like to propose the parallel upload of multiple chunks for resumable upload.
As a future request, I would like to propose modifying the resumable upload using Drive API. In the current stage, the resumable upload is required to be uploaded in chunks in order with the synchronous process. The next chunk can be uploaded after the current chunk is completely uploaded. In this case, when the file size becomes large, the upload time is linearly large.
What is the purpose of this new feature?
If the resumable upload with the asynchronous process got to be able to be achieved, the upload time will become much shorter than that with the current process. By this, the process cost for uploading the files can be reduced.
What existing data does this use?
In the current stage, the official document is this.https://developers.google.com/drive/api/v3/manage-uploads#resumable