Fixed
Status Update
Comments
ad...@google.com <ad...@google.com>
ad...@google.com <ad...@google.com> #2
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?
sa...@google.com <sa...@google.com> #3
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.
lb...@gmail.com <lb...@gmail.com> #4
This is a known issue, we are working with those teams so they release a compatible plugin.
sa...@google.com <sa...@google.com> #5
Thanks!
lb...@gmail.com <lb...@gmail.com> #6
When can we expect an update on this?
na...@google.com <na...@google.com> #7
Last communication from firebase-perf team stated a release is scheduled for this week.
lb...@gmail.com <lb...@gmail.com> #8
But it looks like not only perf but androidx.navigation.safeargs.gradle.SafeArgsPlugin
also has this issue.
lb...@gmail.com <lb...@gmail.com> #9
Yep, androidx.navigation.safeargs.gradle.SafeArgsPlugin
seems to be an issue too.
Description
- Steps to reproduce the problem (including sample code if appropriate).
Download the zip file I've attached here and let your app open it.
Try to open it using ZipFile and using ZipInputStream .
Alternatively, use the app I've attached, which copies it to the external storage and tries to open it using both methods.
- What happened.
Using ZipFile , it works fine.
If you use ZipInputStream, you will get an exception:
java.util.zip.ZipException: only DEFLATED entries can have EXT descriptor
at java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:321)
at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:124)
- What you think the correct behavior should be.
Both should work fine.
The reason is that Google pushes developers to use SAF, and it doesn't provide a way to use ZipFile as we don't have paths to files and not everything even has a path.
Google didn't provide a way to open all zip files because of this, while we could easily use ZipFile before.
Attached here a sample project to show the issue. Also attached a sample problematic file.