Fixed
Status Update
Comments
al...@google.com <al...@google.com> #2
Thank you for your patience, we have rolled back a change in the Google 3D Tiles API service. Could you check on your end if this fixes your issue?
al...@google.com <al...@google.com> #3
Thank you for your prompt response and for rolling back the recent change
in the *Google 3D Tiles API service*. I have tested it on my end, and I can
confirm that the issue is now resolved.
I truly appreciate your quick action in addressing this matter. Your
support is invaluable, and I'm grateful for the efficiency and dedication
of your team.
Thanks again for your help!
*Best regards,Mohammad*
On Fri, Feb 14, 2025 at 7:17 AM <buganizer-system@google.com> wrote:
in the *Google 3D Tiles API service*. I have tested it on my end, and I can
confirm that the issue is now resolved.
I truly appreciate your quick action in addressing this matter. Your
support is invaluable, and I'm grateful for the efficiency and dedication
of your team.
Thanks again for your help!
*Best regards,Mohammad*
On Fri, Feb 14, 2025 at 7:17 AM <buganizer-system@google.com> wrote:
ch...@google.com <ch...@google.com>
di...@google.com <di...@google.com>
ap...@google.com <ap...@google.com> #4
Thank you for the confirmation.
Note however that we plan to restart the rollout soon. IIUC the version 2.7.13 of Blosm was released with a fix: could you confirm with the developer that this version of the plugin would continue working if we were to restart the rollout now?
pr...@google.com <pr...@google.com> #5
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.window:window:1.2.0-beta04
androidx.window:window-core:1.2.0-beta04
androidx.window:window-java:1.2.0-beta04
androidx.window:window-rxjava2:1.2.0-beta04
androidx.window:window-rxjava3:1.2.0-beta04
androidx.window:window-testing:1.2.0-beta04
pa...@gmail.com <pa...@gmail.com> #6
Think my phone ain't got to spyware on it
pr...@google.com <pr...@google.com> #7
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.window:window-testing:1.4.0-alpha01
Description
The following lint check is baseline suppressed in your project. Please remove all instances of this suppression from
window/window/lint-baseline.xml
and address the associated issues before your next stable release.5 instance(s) of
RestrictedApiAndroidX
ActivityStack.getToken can only be called from within the same library group (referenced groupId=
androidx.window.extensions
from groupId=androidx.window
)Found in
src/main/java/androidx/window/embedding/EmbeddingAdapter.kt
at line 0:ActivityStack.getToken can only be called from within the same library group (referenced groupId=
androidx.window.extensions
from groupId=androidx.window
)Found in
src/main/java/androidx/window/embedding/EmbeddingAdapter.kt
at line 0:ActivityStack.getToken can only be called from within the same library group (referenced groupId=
androidx.window.extensions
from groupId=androidx.window
)Found in
src/main/java/androidx/window/embedding/EmbeddingAdapter.kt
at line 0:ActivityStack.getToken can only be called from within the same library group (referenced groupId=
androidx.window.extensions
from groupId=androidx.window
)Found in
src/main/java/androidx/window/embedding/EmbeddingAdapter.kt
at line 0:WindowExtensions.VENDOR_API_LEVEL_2 can only be accessed from within the same library group (referenced groupId=
androidx.window.extensions
from groupId=androidx.window
)Found in
src/main/java/androidx/window/embedding/EmbeddingCompat.kt
at line 0: