Subject: Urgent Inquiry: Google Maps Marker Bugs (iOS & Android) + Future iOS 16 Compatibility After Google SDK Changes
Hello Thunkable Team,
I hope you are doing well.
I am reaching out regarding multiple issues with the Google Maps component on Thunkable, as well as recent information I received from Google about upcoming SDK changes.
1. Google Maps / Places / Navigation SDK: iOS 16 Support Ending (Important Timeline Question)
Google recently notified me that:
-
Starting Q2 2026, the new major versions of the Maps, Places, and Navigation SDK for iOS
will no longer support iOS 16, and will require iOS 17+. -
If the development environment does not explicitly lock the SDK version,
it may automatically upgrade to the new major version, dropping iOS 16 support unintentionally.
Because Thunkable manages all native SDK versions internally, I would like to ask:
① When does Thunkable plan to update the internal Google Maps / Places / Navigation iOS SDK?
② Will Thunkable’s iOS build system automatically increase the minimum iOS version to 17 when this update happens?
③ Will Thunkable provide notice or changelog before such a change affects active apps?
This information is very important for deployment planning because my app still has iOS 16 users.
2. Current Bugs (Critical): Google Maps Markers Not Rendering Correctly
I am experiencing two major problems affecting both platforms:
iOS Issue – Marker Position Inaccuracy
-
Markers do not appear in the correct geographic location.
-
Coordinates are accurate, but the rendered marker appears shifted or offset.
-
I have repeatedly adjusted values but the misalignment persists.
-
This issue appears only in Thunkable’s Google Maps component.
Question:
④ Is this iOS marker inaccuracy related to the older Google Maps SDK version currently used by Thunkable?
Android Issue – Custom Marker Images Not Displayed
On Android:
-
Custom markers (PNG/JPG icons) do not appear at all,
even though the same assets and code work on iOS (aside from the offset issue). -
The map loads normally, but the marker icon is missing or invisible.
Question:
⑤ Is the missing Android custom marker issue also related to the Google Maps SDK version inside Thunkable?
⑥ Is this a known issue, or should I provide a reproducible sample project?
3. Request for Support & Clarification
To resolve these problems and plan for future updates, I kindly request:
-
The current version of the internal Google Maps SDK used by Thunkable (iOS & Android)
-
Whether these marker issues are known bugs
-
Whether SDK updates are planned and if they may resolve these problems
-
Thunkable’s expected timeline for adopting the new Google Maps SDK that ends iOS 16 support
-
Whether there will be any way to preserve older iOS support until my transition is planned