mapView(_:idleAt:) called before map reaches final position when animating camera position [220183522]

Assigned

Bug

Status Update

No update yet.

Description

ma...@gmail.com

created issue #1

Feb 17, 2022 10:27PM

Issue report
----------------

When making an animated change to the camera position, the GMSMapViewDelegate method mapView(_:idleAt:) is called before the map idles at the final position. When mapView(_:idleAt:) is called, the position that it reports is not the same as the position that the map is being animated to.

Changing the camera position without animation correctly reports the final position when mapView(_:idleAt:) is called.

Expected behavior:

GMSMapViewDelegate.mapView(_:idleAt:) should be called once the map reaches its final position after the animation completes, and should contain the same position passed into GMSMapView.animate(to: <GMSCameraPosition>).

What steps will reproduce the problem?

1. Call `mapView.animate(to: <GMSCameraPosition>)`
2. Observe the timing of and the position that is passed into `GMSMapViewDelegate.mapView(_:idleAt:)`.

If I print when the delegate methods are called, I see that idleAt gets called prior to the final didChangePosition delegate call and does not contain the position that was passed into the animateToCameraPosition call. The final didChangePosition call does contain the position that I'm animating to, but I need to know the final position when the map idles.

Here's the camera position I want to animate to:
mapView.animate(to: GMSCameraPosition(latitude: 44.9778, longitude: -93.2650, zoom: 10))

Log:
mapView animateToPosition CLLocationCoordinate2D(latitude: 44.9778, longitude: -93.265) 10.0
mapView didChangePosition CLLocationCoordinate2D(latitude: 50.58661030778135, longitude: -10.560035593807697) 4.573082
mapView didChangePosition CLLocationCoordinate2D(latitude: 49.72720401661033, longitude: -23.232449926435944) 5.404618
mapView didChangePosition CLLocationCoordinate2D(latitude: 48.758097148636786, longitude: -37.522459253668785) 6.342297
mapView didChangePosition CLLocationCoordinate2D(latitude: 48.080882050343185, longitude: -47.50836364924908) 6.99755
mapView didChangePosition CLLocationCoordinate2D(latitude: 47.27439480059722, longitude: -59.40045800060034) 7.777883
mapView didChangePosition CLLocationCoordinate2D(latitude: 46.43944882346799, longitude: -71.71219065785407) 8.5857525
mapView didChangePosition CLLocationCoordinate2D(latitude: 45.610743222534914, longitude: -83.93190812319517) 9.387583
mapView idleAtPosition CLLocationCoordinate2D(latitude: 45.610743222534914, longitude: -83.93190812319517) 9.387583
mapView didChangePosition CLLocationCoordinate2D(latitude: 44.97779999772054, longitude: -93.26500006020068) 10.0

Tested with:
- Google Maps iOS SDK 6.0.1
- Xcode 13.2.1
- iOS 15.2.1

GoogleMapsView.zip

41 MB

Download

Comments

ma...@google.com <ma...@google.com> Feb 18, 2022 12:28AM

Assigned to ma...@google.com.

ma...@google.com <ma...@google.com> #2Feb 18, 2022 08:33AM

Thanks for reaching out. To investigate the problem, we require a few details. Could you please provide your GMS module versions, recent system logs and video of the issue.

You can find instructions for retrieving the versions and logs on this page. Let me know if you need any help with retrieving the logs.

[Deleted User] <[Deleted User]> #3Apr 4, 2022 11:49AM

thank you! I will look at this as soon as I can.

ma...@google.com <ma...@google.com> #4Apr 5, 2022 03:20AM

hello,
I would assume the GMS module version is the google play service version that is running on debugging phone. that version is 25.08.32 (200300-731361394).

logcat logs (when I start the app):

2025-03-10 09:27:10.755 17848-17848 GHSAFM-3p-...inActivity com.google.homesampleapp.default I ====================================
Version 2.0.0-default
App GHSAFM-3p-ecosystem
====================================
2025-03-10 09:27:10.756 17848-17848 GHSAFM-3p-...inActivity com.google.homesampleapp.default D onCreate()
2025-03-10 09:27:10.757 17848-17848 GHSAFM-3p-...inActivity com.google.homesampleapp.default D lifecycleObservers [[com.google.homesampleapp.lifecycle.HalfSheetSuppressionObserver@b819bd1]]
2025-03-10 09:27:10.766 17848-17848 GHSAFM-3p-...em-UtilsKt com.google.homesampleapp.default D *** Preference Files ***
2025-03-10 09:27:10.839 17848-17848 ThreeFingerSwipe com.google.homesampleapp.default I mSwipeDistanceThreshold:18
2025-03-10 09:27:10.840 17848-17848 ThreeFingerSwipe com.google.homesampleapp.default I mMaxWidth = 720; mMaxHeight = 1491
2025-03-10 09:27:10.851 17848-17848 ThreeFingerSwipe com.google.homesampleapp.default I getPackageName = com.google.homesampleapp.default
2025-03-10 09:27:10.962 17848-17848 GHSAFM-3p-...inActivity com.google.homesampleapp.default D onStart()
2025-03-10 09:27:10.966 17848-17848 GHSAFM-3p-...onObserver com.google.homesampleapp.default D onStart()
2025-03-10 09:27:11.020 17848-17848 Compatibil...geReporter com.google.homesampleapp.default D Compat change id reported: 237531167; UID 10238; state: DISABLED
2025-03-10 09:27:11.040 17848-17848 OpenGLRenderer com.google.homesampleapp.default W Unknown dataspace 0
2025-03-10 09:27:11.110 17848-17848 Choreographer com.google.homesampleapp.default I Skipped 58 frames! The application may be doing too much work on its main thread.
2025-03-10 09:27:11.359 17848-17848 mpleapp.default com.google.homesampleapp.default W Method java.lang.Object androidx.compose.runtime.snapshots.SnapshotStateMap.mutate(kotlin.jvm.functions.Function1) failed lock verification and will run slower.
Common causes for lock verification issues are non-optimized dex code
and incorrect proguard optimizations.
2025-03-10 09:27:11.359 17848-17848 mpleapp.default com.google.homesampleapp.default W Method void androidx.compose.runtime.snapshots.SnapshotStateMap.update(kotlin.jvm.functions.Function1) failed lock verification and will run slower.
2025-03-10 09:27:11.360 17848-17848 mpleapp.default com.google.homesampleapp.default W Method boolean androidx.compose.runtime.snapshots.SnapshotStateMap.removeIf$runtime_release(kotlin.jvm.functions.Function1) failed lock verification and will run slower.
2025-03-10 09:27:11.789 17848-17902 mali_gralloc com.google.homesampleapp.default D register: id=2930000016c, handle=0xf654b0c0, importpid=-1, gRegisteredHandles=0
2025-03-10 09:27:11.793 17848-17902 mali_gralloc com.google.homesampleapp.default D register: id=2930000016d, handle=0xf654b7c0, importpid=-1, gRegisteredHandles=1
2025-03-10 09:27:11.794 17848-17902 mali_gralloc com.google.homesampleapp.default D register: id=2930000016e, handle=0xf654ba60, importpid=-1, gRegisteredHandles=2
2025-03-10 09:27:11.795 17848-17902 mali_gralloc com.google.homesampleapp.default D register: id=2930000016f, handle=0xf654bb40, importpid=-1, gRegisteredHandles=3
2025-03-10 09:27:12.284 17848-17848 mpleapp.default com.google.homesampleapp.default W Method boolean androidx.compose.runtime.snapshots.SnapshotStateList.conditionalUpdate(kotlin.jvm.functions.Function1) failed lock verification and will run slower.
2025-03-10 09:27:12.285 17848-17848 mpleapp.default com.google.homesampleapp.default W Method java.lang.Object androidx.compose.runtime.snapshots.SnapshotStateList.mutate(kotlin.jvm.functions.Function1) failed lock verification and will run slower.
2025-03-10 09:27:12.285 17848-17848 mpleapp.default com.google.homesampleapp.default W Method void androidx.compose.runtime.snapshots.SnapshotStateList.update(kotlin.jvm.functions.Function1) failed lock verification and will run slower.
2025-03-10 09:27:12.439 17848-17848 GHSAFM-3p-...posablesKt com.google.homesampleapp.default D MsgAlertDialog [null]
2025-03-10 09:27:12.863 17848-17848 GHSAFM-3p-...Repository com.google.homesampleapp.default D shouldShowHalfsheetNotification
2025-03-10 09:27:12.864 17848-17868 OpenGLRenderer com.google.homesampleapp.default I Davey! duration=2265ms; Flags=1, FrameTimelineVsyncId=129210, IntendedVsync=1395390399803, Vsync=1396038344715, InputEventId=0, HandleInputStart=1396041416078, AnimationStart=1396041427808, PerformTraversalsStart=1396041752770, DrawStart=1397575614077, FrameDeadline=1395411622025, FrameInterval=1396040116885, FrameStartTime=11171464, SyncQueued=1397611300115, SyncStart=1397745453692, IssueDrawCommandsStart=1397746579653, SwapBuffers=1397787823807, FrameCompleted=1397789712269, DequeueBufferDuration=25846, QueueBufferDuration=408769, GpuCompleted=1397789712269, SwapBuffersCompleted=1397788405576, DisplayPresentTime=0, CommandSubmissionCompleted=1397787823807,
2025-03-10 09:27:12.952 17848-17848 Compatibil...geReporter com.google.homesampleapp.default D Compat change id reported: 247079863; UID 10238; state: DISABLED
2025-03-10 09:27:12.952 17848-17848 GHSAFM-3p-...HomeScreen com.google.homesampleapp.default D HomeRoute [[]]
2025-03-10 09:27:12.956 17848-17848 GHSAFM-3p-...$HomeRoute com.google.homesampleapp.default D HomeScreen: LifecycleResumeEffect
2025-03-10 09:27:12.958 17848-17848 GHSAFM-3p-...$HomeRoute com.google.homesampleapp.default D intent [Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 cmp=com.google.homesampleapp.default/com.google.homesampleapp.MainActivity }]
2025-03-10 09:27:12.959 17848-17848 GHSAFM-3p-...$HomeRoute com.google.homesampleapp.default D Invocation: Main
2025-03-10 09:27:12.960 17848-17848 GHSAFM-3p-...eViewModel com.google.homesampleapp.default D subscribeToDevicesPeriodicUpdates()
2025-03-10 09:27:12.969 17848-17848 Choreographer com.google.homesampleapp.default I Skipped 160 frames! The application may be doing too much work on its main thread.
2025-03-10 09:27:12.982 17848-17909 ConnectionStatusConfig com.google.homesampleapp.default W Dynamic lookup for intent failed for action: com.google.android.gms.home.service.START
2025-03-10 09:27:12.991 17848-17909 GmsClient com.google.homesampleapp.default W unable to connect to service: com.google.android.gms.home.service.START on com.google.android.gms
2025-03-10 09:27:13.050 17848-17868 OpenGLRenderer com.google.homesampleapp.default I Davey! duration=1857ms; Flags=0, FrameTimelineVsyncId=129763, IntendedVsync=1396105386434, Vsync=1397892932194, InputEventId=0, HandleInputStart=1397900815307, AnimationStart=1397900831153, PerformTraversalsStart=1397936259269, DrawStart=1397936789692, FrameDeadline=1397813486785, FrameInterval=1397899770038, FrameStartTime=11172161, SyncQueued=1397958749884, SyncStart=1397958831961, IssueDrawCommandsStart=1397958919307, SwapBuffers=1397961135384, FrameCompleted=1397962792269, DequeueBufferDuration=17039, QueueBufferDuration=303923, GpuCompleted=1397962792269, SwapBuffersCompleted=1397961530461, DisplayPresentTime=0, CommandSubmissionCompleted=1397961135384,
2025-03-10 09:27:13.050 17848-17848 GHSAFM-3p-...iModelFlow com.google.homesampleapp.default D *** devicesListUiModelFlow changed ***
2025-03-10 09:27:13.174 17848-17848 GHSAFM-3p-...er$onStart com.google.homesampleapp.default E Error on suppressHalfSheetNotification (Ask Gemini)
com.google.android.gms.common.api.ApiException: 17: API: CommissioningClient.API is not available on this device. Connection failed with: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null}
at com.google.android.gms.common.internal.ApiExceptionUtil.fromStatus(com.google.android.gms:play-services-base@@18.2.0:3)
at com.google.android.gms.common.api.internal.ApiExceptionMapper.getException(com.google.android.gms:play-services-base@@18.2.0:1)
at com.google.android.gms.common.api.internal.zag.zad(com.google.android.gms:play-services-base@@18.2.0:1)
at com.google.android.gms.common.api.internal.zabq.zaE(com.google.android.gms:play-services-base@@18.2.0:7)
at com.google.android.gms.common.api.internal.zabq.zaD(com.google.android.gms:play-services-base@@18.2.0:2)
at com.google.android.gms.common.api.internal.zabq.zar(com.google.android.gms:play-services-base@@18.2.0:24)
at com.google.android.gms.common.api.internal.zabt.run(com.google.android.gms:play-services-base@@18.2.0:12)
at android.os.Handler.handleCallback(Handler.java:958)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:205)
at android.os.Looper.loop(Looper.java:294)
at android.os.HandlerThread.run(HandlerThread.java:67)
2025-03-10 09:27:16.663 17848-17912 ProfileInstaller com.google.homesampleapp.default D Installing profile for com.google.homesampleapp.default

logcat logs (when I click the addDevice button):

2025-03-10 09:29:24.876 17848-17848 GHSAFM-3p-...sionDevice com.google.homesampleapp.default D onAddDeviceClick
2025-03-10 09:29:24.877 17848-17848 GHSAFM-3p-...eViewModel com.google.homesampleapp.default D unsubscribeToPeriodicUpdates()
2025-03-10 09:29:24.879 17848-17848 GHSAFM-3p-...meScreenKt com.google.homesampleapp.default D CommissionDevice: starting
2025-03-10 09:29:24.909 17848-17909 ConnectionStatusConfig com.google.homesampleapp.default W Dynamic lookup for intent failed for action: com.google.android.gms.home.service.START
2025-03-10 09:29:24.913 17848-17909 GmsClient com.google.homesampleapp.default W unable to connect to service: com.google.android.gms.home.service.START on com.google.android.gms
2025-03-10 09:29:24.978 17848-17848 GHSAFM-3p-...meScreenKt com.google.homesampleapp.default E com.google.android.gms.common.api.ApiException: 17: API: CommissioningClient.API is not available on this device. Connection failed with: ConnectionResult{statusCode=API_UNAVAILABLE, resolution=null, message=null} (Ask Gemini)
at com.google.android.gms.common.internal.ApiExceptionUtil.fromStatus(com.google.android.gms:play-services-base@@18.2.0:3)
at com.google.android.gms.common.api.internal.ApiExceptionMapper.getException(com.google.android.gms:play-services-base@@18.2.0:1)
at com.google.android.gms.common.api.internal.zag.zad(com.google.android.gms:play-services-base@@18.2.0:1)
at com.google.android.gms.common.api.internal.zabq.zaE(com.google.android.gms:play-services-base@@18.2.0:7)
at com.google.android.gms.common.api.internal.zabq.zaD(com.google.android.gms:play-services-base@@18.2.0:2)
at com.google.android.gms.common.api.internal.zabq.zar(com.google.android.gms:play-services-base@@18.2.0:24)
at com.google.android.gms.common.api.internal.zabt.run(com.google.android.gms:play-services-base@@18.2.0:12)
at android.os.Handler.handleCallback(Handler.java:958)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:205)
at android.os.Looper.loop(Looper.java:294)
at android.os.HandlerThread.run(HandlerThread.java:67)

When I run the application on a emulator like the Pixel 9 Pro with api level 34, then the application works fine (only I can't use matter over an emulator).
hope this helps.

is...@google.com <is...@google.com> May 7, 2022 07:07AM

Status: New

ra...@google.com <ra...@google.com> Jun 29, 2022 11:27AM

Assigned to ra...@google.com.

rj...@gmail.com <rj...@gmail.com> #5Aug 4, 2022 02:01PM

These are the videos of the problem (one is with the physical device and one is with the emulator)

an...@gmail.com <an...@gmail.com> #6Aug 15, 2022 12:07PM

Thanks for sharing the logs. We still need the versions for all api modules to find out what is missing. I have attached shell.sh file to this comment, which you can use to get versions.txt. In your terminal point to folder where that file is and type:

./shell.sh phoneId

Replace phoneId with yours(use adb devices to find your phoneID)

Share the versions.txt with us.

br...@gmail.com <br...@gmail.com> #7Nov 10, 2022 09:38PM

hello i have done what you said and here is the versions.txt

jy...@gmail.com <jy...@gmail.com> #8Dec 5, 2022 11:40AM

Hello, I have came to the conclusion that matter is incompatible with the Motorola e14. but I still need a phone to test the matter application. do you know any budget android phones (under €200)? like the Samsung galaxy A16.
Thank you for helping me.
kind regards,
Aron van Diepen

Message last modified on Dec 5, 2022 11:43AM

a....@gmail.com <a....@gmail.com> #9Jan 11, 2023 03:24PM

Based on your versions, it seems that the necessary modules for Matter commissioning are missing or not accessible on your Motorola e14, even though you have a recent Play Services version.

To ensure these modules are available, please refer to these steps:

Add the Play services Home dependency to your build.gradle:

implementation 'com.google.android.gms:play-services-home:16.0.0-beta1'

Declare the module dependency in your AndroidManifest.xml within the <application> tag:

(For Android 14) Add the <queries> block to your AndroidManifest.xml:

You can programmatically check if the Home module is available at runtime using the ModuleInstallClient. Refer to the "Ensuring API availability with ModuleInstallClient" documentation for details on how to implement this check.

da...@gmail.com <da...@gmail.com> #10Mar 23, 2023 08:26AM

I can confirm this issue, it seems to happen only on faster devices, testing on iPhone 12 Pro.

do...@vieclamdoimenhphattai.com <do...@vieclamdoimenhphattai.com> #11Apr 7, 2023 02:00AM

https://drive.google.com/file/d/15pxlfW27tjt0fJajk-YphT8XFoUv7Qix/view?usp=drive_web (google_privacy_policy_vi.pdf)

[Deleted User] <[Deleted User]> #12Aug 7, 2023 05:01PM

Closeed

am...@nextgeni.com <am...@nextgeni.com> #13Mar 4, 2025 08:24AM

Same issue happens on my device (12 pro max)