Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GoogleMaps issue - 400 bad request #36

Open
taglia3 opened this issue Mar 13, 2019 · 4 comments
Open

GoogleMaps issue - 400 bad request #36

taglia3 opened this issue Mar 13, 2019 · 4 comments

Comments

@taglia3
Copy link

taglia3 commented Mar 13, 2019

Hi,

I've an issue with GoogleMaps and Bagel, in particular the map tiles don't load and the request to Google returns 400 (bad request).
I've debugged the Bagel pod and see that if I comment out the swizzling of the resume method it works fine.
It seems the the original network method isn't called with the right parameters, the body request isn't propagated.

The request with the uncomment swizzled resume (400m bad request) is:
Screenshot 2019-03-13 at 12 01 34

And the request with the commented swizzled method (200 ok) is:
Screenshot 2019-03-13 at 12 01 40

@yagiz
Copy link
Owner

yagiz commented Apr 30, 2019

This is huge. I'll inspect on it. If you provide a dummy example project it would be great tho. @taglia3

@tejas-ardeshna
Copy link

@yagiz Facing the same issue, try google map demo provided by firebase.

@davidhorvath
Copy link

@yagiz When can we expect the fix for this? (Commenting out swizzleSessionTaskResume in the pod solves this issue as @taglia3 said)

@yagiz
Copy link
Owner

yagiz commented Jul 10, 2019

@davidhorvath I need more time to inspect this. If there is no issue about the date/time when it's commented out, then we may fix this by removing swizzleSessionTaskResume. @davidhorvath

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants