Map zoom/filtering is not possible on the Huawei P30 Pro (Android 10) when Google Maps is selected.

[pilotspelman]

Guidelines

• I have read the guidelines to open issues

Steps to reproduce

1. Open Aves
2. Click the three dots in the upper right corner
3. Click the map option
4. Click the Map Style icon in the upper right corner and select Open TopoMap
5. Pinch-to-zoom and pan are possible
6. Click the Map Style icon in the upper right corner and select any of the Google Maps options.
7. The map now freezes and is not usable.
8. Click the Map Style icon in the upper right corner and select Open TopoMap again.
9. Pinch-to-zoom and pan to filter photos are possible again

The other non-Google Maps partly works, but Open TopoMap works best.

Expected results

Pinch-to-zoom and pan-to-filter photos should be possible regardless of the selected map style.

Actual results

See above.

Screenshots or Video

Screenshots / Video demonstration

[Upload media here]

Logs

aves-logs-20260714_012034.txt

Custom environment

• I use a custom rom (if so, please specify below)
• I use a custom launcher (if so, please specify below)

Additional context

No response

[deckerst]

Do you have the Google Mobile Services installed on this Huawei device? I thought Google and Huawei didn't mingle, but I don't remember the timeline of this separation.

[pilotspelman]

Yes, the Huawei P30 Pro has official, factory-certified GMS pre-installed. It was one of the last Huawei models released before the separation. Google Maps and the Google Play Store work completely normally on this device.
I have already tried clearing the cache and all data for both Aves and Google Play Services, but the filtering and location display issues remain the same.
As a regular user, I noticed that switching the map style to 'Open TopoMap' makes everything work perfectly. I really want to praise you for including alternative map styles like Open TopoMap in Aves—it is a fantastic fallback that saves the day right now!
Could the recent app update have changed how Aves specifically communicates with Google's map framework?

[deckerst]

The Google Map layers use a proprietary plugin from Google which may or may not change (we never know with proprietary stuff). All the other map layers use different, open-source code for rendering.

There is also a difference in the way the Google Map view is included in the app, and that may have changed with an upgrade of the framework I'm using. Was it working with a previous version of Aves? If so, would you know with which version it stopped working?

Also, as I don't really understand how your map looks and behaves when it fails, could you please take a screen recording with a Google Map layer in Aves?

[pilotspelman]

Yes, it worked with a previous version of Aves, but I don't remember the version number. Could you provide an older APK file for the Google Play version so I can check? Maybe start with the version before the current one.

Unfortunately, GitHub does not accept the upload (7MB), so I'm providing you with a link instead.

Link to screen recording on my own NextCloud

[deckerst]

All the APKs are there with the releases:
https://github.com/deckerst/aves/releases/

However, installing one would overwrite your currently installed version, which may not be what you want. In any case, if you do, I'm interested to know which version introduced the issue.

Also, I've tried to reproduce the issue on an Android 10 emulator but the Google Map layers are working fine.

Edit: a few observations after watching your recording:

• the Google map view does register your gestures (as the coordinates in the filter at the top get updated), but the rendering is broken,
• the Google map view at least loads its logo, so it seems to be a rendering update issue,
• you're trying to pinch-to-zoom on the map preview in the Info page, but this view does not accept gestures (by design).

[deckerst]

From the logs I see a strange certificate issue from Google Maps:

07-14 01:19:33.614 14374 15114 W PhFlagUpdateRegistry: Caused by: java.lang.SecurityException: GoogleCertificatesRslt: not allowed: pkg=deckers.thibault.aves, sha256=[1254b337cd99157557fac4759d03695153343824050ec1c93b2d2642c666e4e2], atk=false, ver=262532013.true (go/gsrlt)
07-14 01:19:33.614 14374 15114 W PhFlagUpdateRegistry: 	at android.os.Parcel.createException(Parcel.java:2071)
07-14 01:19:33.614 14374 15114 W PhFlagUpdateRegistry: 	at android.os.Parcel.readException(Parcel.java:2039)
07-14 01:19:33.614 14374 15114 W PhFlagUpdateRegistry: 	at android.os.Parcel.readException(Parcel.java:1987)
07-14 01:19:33.614 14374 15114 W PhFlagUpdateRegistry: 	at m140.azb.c(:com.google.android.gms.policy_maps_core_dynamite@260830207@260830202025.896086277.896086277:11)
07-14 01:19:33.614 14374 15114 W PhFlagUpdateRegistry: 	at m140.cxk.a(:com.google.android.gms.policy_maps_core_dynamite@260830207@260830202025.896086277.896086277:32)
...

It may be a temporary issue, as the app is registered correctly with Google Services (as it works on other devices).