Fixed
Status Update
Comments
ca...@google.com <ca...@google.com>
ca...@google.com <ca...@google.com> #2
We have passed this to the development team and will update this issue with more information as it becomes available.
ca...@google.com <ca...@google.com> #3
+1 on this.
fa...@ext.careem.com <fa...@ext.careem.com> #4
Can confirm this issue. Fixed after a reboot.
da...@gmail.com <da...@gmail.com> #6
- Build Number: google/bramble/bramble:S/SPP1.210122.020.A3/7145137:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
It does not work on bramble.
Filed by Android Beta Feedback. Version (Bundled): 2.15-betterbug.external_20201211_RC02
To learn more about our feedback process, please visithttps://developer.android.com/preview/feedback#feedback-app .
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
It does not work on bramble.
Filed by Android Beta Feedback. Version (Bundled): 2.15-betterbug.external_20201211_RC02
To learn more about our feedback process, please visit
cl...@googlemail.com <cl...@googlemail.com> #7
Same here on 4a, very infrequent though. Reboot fixes the issue.
mi...@gmail.com <mi...@gmail.com> #8
Same issue un pixel 5. Can't reproduce, happens randomly 1-2 times a week.
mo...@gmail.com <mo...@gmail.com> #9
- Build Number: google/blueline/blueline:S/SPP1.210122.022/7158812:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Back Gesture disabled when changing something in the settings
Filed by Android Beta Feedback. Version (Bundled): 2.15-betterbug.external_20201211_RC02
To learn more about our feedback process, please visithttps://developer.android.com/preview/feedback#feedback-app .
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Back Gesture disabled when changing something in the settings
Filed by Android Beta Feedback. Version (Bundled): 2.15-betterbug.external_20201211_RC02
To learn more about our feedback process, please visit
de...@gmail.com <de...@gmail.com> #10
- Build Number: google/sunfish/sunfish:S/SPP1.210122.022/7158812:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Issue is still present in the new dp1.1 update
Filed by Android Beta Feedback. Version (Bundled): 2.15-betterbug.external_20201211_RC02
To learn more about our feedback process, please visithttps://developer.android.com/preview/feedback#feedback-app .
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
Issue is still present in the new dp1.1 update
Filed by Android Beta Feedback. Version (Bundled): 2.15-betterbug.external_20201211_RC02
To learn more about our feedback process, please visit
mi...@gmail.com <mi...@gmail.com> #11
I had the same problem until recently. Every app, all functions. New update seemed to fix it for me. Pixel 3a
Build: S (SPP1.210122.022)
Build: S (SPP1.210122.022)
ca...@google.com <ca...@google.com> #12
Same issue for me. Pixel 5 - just started today on all apps. Rebooting does not fix the issue. Will have to go to the three-button navigation until it's fixed.
Description
===========================================================================================
#REMINDER: Please do not disclose any possible PII such as: email address, IP, contact number, any part of name, project numbers and billing accounts as these information may violate security and privacy. Comments or attachments that include PII will be removed and restricted from public viewing.
Furthermore, please refrain from replying to a comment as this will make your email address visible. Instead, you may use the Issue Tracker’s comment feature for your replies.
It is OK to share your API Project ID, but _not_ API keys or client ID credentials.
To learn more about personal data, visit
===========================================================================================
What is the incorrect behavior that you are experiencing?
I tried to build a stable app weve had running since obj-c days this week in XCode and the whole map fails to render.
What was worse was it threw tonnes of Constaint errors and broke the layout of a very complex UI to pieces.
After much testing and walking through the steps in the documentation to init the app.
I realised that if you only configure the mapView in the Story board > and set Custom Class to "GMSMapView"
and dont also call the new init: in the code which takes the frame size
the whole mapView not only fails to load (it used to show a basic map)
It also chooses a default frame of 0,0,0,0 and ignores the constraints for the view setup in the SB.
If the map view is part of a complex UI with a lots of overlays the whole UI breaks and causes a LOT of constraint errors in the console.
Ive noticed a few other issues mention "app layout suddenly broke"
What should happen instead?
Before v 8.0.0 configuring the basic mapview in SB > Custom Class was common.
So would be still used in a lot of apps.
Which now suddenly break for an unknown reason when you try to build against v 8+.
Preferred fix
- Can we render a basic map if map is configured only in SB > Custom Class.
Definitely needs fixing
If you dont want to render the map can the SDK stop resetting the frame to 0,0,0,0 and respect any constraint set in the SB
as it cause a LOT of constraint errors.
And it took two days to find a solution as the documentation only shows how to configure the GMSMapView in code.
Link to the Demo application[1] that reproduces the problem:
attached
Steps to reproduce the problem:
1. Create new app Swift or Obj-C, configure the pod and enter the key
2. Add a View to the Viewcontroller
3. add constraints on all 4 side with margin of 0. The mapView should fill the whole screen
4. click on the map View in SB and open the Identity inspector
5. Under custom class field enter "GMSMapView"
6. Run the app
7. The map no longer renders.
8. Open the 3d inspector, click on the GMSMapView and note the dimensions are no 0.0.0.0
and is ignoring the 4 constraints around the map view and breaking the whole UI.
See DEBUG_VIEW.png in the attached project.
Older apps would have configured the map view this way and now suddenly they randomly break.
Maybe the default frame should respect the constraints set and not pull the whole UI out of sync and scare the hell out of devs with a tonne of layout warnings :)
Maybe some error logging to warn people map now needs to be configured in code.
Cheers
Brian Clear
clearbrian@googlemail.com
Operating system version:
Google Maps SDK for iOS version: GoogleMaps (8.3.1)
We would not have built this app for a while and the new init that takes the frame in options came in v8 so may be an issue after that.
Hardware model:
Fails in all iphones, ipads and simulator
-------------------------------------------------------------------
[1] You can fork