Status Update
No update yet.
Comments
kk...@google.com
kk...@google.com
Analyzing dynamic features on their own like that doesn't work properly since even though they "depend" on the app they're actually including into an app so for example the unused resource check only makes sense when you look at it from the app perspective, not the other way around.
I believe in 7.0 we've fixed this in the sense that there isn't a lint task on the individual dynamic features.
em...@anrufliste.com
+1. In AGP 7.0 there are no lint tasks in dynamic-features; instead, any dynamic-features are analyzed when running lint on the app module. OP, can you try with AGP 7.0.0-rc01, run lintRelease on the corresponding application module, and see if you still hit the same issue?
em...@anrufliste.com
Not using dynamic feature modules but have this with an application module and a library module, happening on 7.0.0-rc01. I haven't figured out a repro yet but will upload one if I manage.
kk...@google.com
Re #5, yes, a repro project would be very helpful, thanks!
kk...@google.com
Closing this bug as not reproducible, but please reopen if you have a repro project.
Description
The current Meta Data for German short numbers starting with 116 are not covering any valid number as defined in the official 116xxx ruling (
In addition compare the toll free check, where the whole 116xxx range is already used. Without that change, a number would be marked as not valid but toll free, which would not make sense.
The other way round would be ok and even more future. If a new number is assigned in this range, it would be instantly checked as valid, but only toll free if manually added (if that is really tool free). Right now it is the opposite, so if the new number is not toll free, we directly have to false informations (not valid but toll free).