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

Google Maps does not render on cellular #32

Open
robsturtz opened this issue Nov 25, 2012 · 12 comments
Open

Google Maps does not render on cellular #32

robsturtz opened this issue Nov 25, 2012 · 12 comments
Assignees
Labels
Milestone

Comments

@robsturtz
Copy link
Collaborator

the static google map does not render when using cellular

@sosaucily
Copy link
Owner

The research I've seen shows how this is likely related to the IP of the device. Other than proxying all requests through our web server, there are no recommendations online.

However, I have tried including our API key to our requests for google static maps, which may work and help explain why others aren't having the same issue.

@robsturtz
Copy link
Collaborator Author

How can I test with the API key in the request over cellular?

@sosaucily
Copy link
Owner

Wait for the update? :)

Other than getting a dev version on your phone it's hard.

Perhaps when you notice the issue happening, I can send you a sample URL to
google maps and we can try directly from the web browser

Jesse Smith

On Nov 25, 2012, at 5:05 PM, robsturtz notifications@github.com wrote:

How can I test with the API key in the request over cellular?

On Nov 25, 2012, at 4:43 PM, Jesse Smith notifications@github.com wrote:

The research I've seen shows how this is likely related to the IP of the
device. Other than proxying all requests through our web server, there are
no recommendations online.

However, I have tried including our API key to our requests for google
static maps, which may work and help explain why others aren't having the
same issue.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701250>.


Reply to this email directly or view it on
GitHubhttps://github.com//issues/32#issuecomment-10701519.

@robsturtz
Copy link
Collaborator Author

It happens pretty much every time on cellular including this one I just
generated. http://oyster.me/stories/315

On Nov 25, 2012, at 6:46 PM, Jesse Smith notifications@github.com wrote:

Wait for the update? :)

Other than getting a dev version on your phone it's hard.

Perhaps when you notice the issue happening, I can send you a sample URL to
google maps and we can try directly from the web browser

Jesse Smith

On Nov 25, 2012, at 5:05 PM, robsturtz notifications@github.com wrote:

How can I test with the API key in the request over cellular?

On Nov 25, 2012, at 4:43 PM, Jesse Smith notifications@github.com wrote:

The research I've seen shows how this is likely related to the IP of the
device. Other than proxying all requests through our web server, there are
no recommendations online.

However, I have tried including our API key to our requests for google
static maps, which may work and help explain why others aren't having the
same issue.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701250>.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701519>.


Reply to this email directly or view it on
GitHubhttps://github.com//issues/32#issuecomment-10702828.

@sosaucily
Copy link
Owner

OK, let's try each of these from both wifi and cell. Second one has the
apikey, not the first.

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false&key=AIzaSyCloHHOTgUAwKqVVpovHVzGioPQ8RkQeTY

On Sun, Nov 25, 2012 at 8:32 PM, robsturtz notifications@github.com wrote:

It happens pretty much every time on cellular including this one I just
generated. http://oyster.me/stories/315

On Nov 25, 2012, at 6:46 PM, Jesse Smith notifications@github.com
wrote:

Wait for the update? :)

Other than getting a dev version on your phone it's hard.

Perhaps when you notice the issue happening, I can send you a sample URL
to
google maps and we can try directly from the web browser

Jesse Smith

On Nov 25, 2012, at 5:05 PM, robsturtz notifications@github.com wrote:

How can I test with the API key in the request over cellular?

On Nov 25, 2012, at 4:43 PM, Jesse Smith notifications@github.com
wrote:

The research I've seen shows how this is likely related to the IP of the
device. Other than proxying all requests through our web server, there are
no recommendations online.

However, I have tried including our API key to our requests for google
static maps, which may work and help explain why others aren't having the
same issue.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701250>.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701519>.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10702828>.


Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-10704352.

--Jesse Smith

@sosaucily
Copy link
Owner

From cellular (AT&T) both those links work for me. Let's see if we can
prove this solution by checking that the first fails (consistently) and the
second succeeds (consistently).

On Sun, Nov 25, 2012 at 9:17 PM, Jesse Smith Jesses16@gmail.com wrote:

OK, let's try each of these from both wifi and cell. Second one has the
apikey, not the first.

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false&key=AIzaSyCloHHOTgUAwKqVVpovHVzGioPQ8RkQeTY

On Sun, Nov 25, 2012 at 8:32 PM, robsturtz notifications@github.comwrote:

It happens pretty much every time on cellular including this one I just
generated. http://oyster.me/stories/315

On Nov 25, 2012, at 6:46 PM, Jesse Smith notifications@github.com
wrote:

Wait for the update? :)

Other than getting a dev version on your phone it's hard.

Perhaps when you notice the issue happening, I can send you a sample URL
to
google maps and we can try directly from the web browser

Jesse Smith

On Nov 25, 2012, at 5:05 PM, robsturtz notifications@github.com wrote:

How can I test with the API key in the request over cellular?

On Nov 25, 2012, at 4:43 PM, Jesse Smith notifications@github.com
wrote:

The research I've seen shows how this is likely related to the IP of the
device. Other than proxying all requests through our web server, there
are
no recommendations online.

However, I have tried including our API key to our requests for google
static maps, which may work and help explain why others aren't having the
same issue.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701250>.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701519>.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10702828>.


Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-10704352.

--Jesse Smith

--Jesse Smith

@robsturtz
Copy link
Collaborator Author

For me the first failed on cellular (AT&T). The 2nd worked. Then I switched
to wifi and they both worked. Then I switched back to cellular and both
worked (caching perhaps?)

On Nov 25, 2012, at 9:20 PM, Jesse Smith notifications@github.com wrote:

From cellular (AT&T) both those links work for me. Let's see if we can
prove this solution by checking that the first fails (consistently) and the
second succeeds (consistently).

On Sun, Nov 25, 2012 at 9:17 PM, Jesse Smith Jesses16@gmail.com wrote:

OK, let's try each of these from both wifi and cell. Second one has the
apikey, not the first.

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false&key=AIzaSyCloHHOTgUAwKqVVpovHVzGioPQ8RkQeTY

On Sun, Nov 25, 2012 at 8:32 PM, robsturtz notifications@github.comwrote:

It happens pretty much every time on cellular including this one I just
generated. http://oyster.me/stories/315

On Nov 25, 2012, at 6:46 PM, Jesse Smith notifications@github.com
wrote:

Wait for the update? :)

Other than getting a dev version on your phone it's hard.

Perhaps when you notice the issue happening, I can send you a sample URL
to
google maps and we can try directly from the web browser

Jesse Smith

On Nov 25, 2012, at 5:05 PM, robsturtz notifications@github.com wrote:

How can I test with the API key in the request over cellular?

On Nov 25, 2012, at 4:43 PM, Jesse Smith notifications@github.com
wrote:

The research I've seen shows how this is likely related to the IP of the
device. Other than proxying all requests through our web server, there
are
no recommendations online.

However, I have tried including our API key to our requests for google
static maps, which may work and help explain why others aren't having
the
same issue.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701250>.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701519>.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10702828>.


Reply to this email directly or view it on GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10704352>.

--Jesse Smith

--Jesse Smith


Reply to this email directly or view it on
GitHubhttps://github.com//issues/32#issuecomment-10704993.

@robsturtz
Copy link
Collaborator Author

This image indicates exceeding the API limit. If we don't have a key they
might be pooling all requests?

Anyway seems to work correctly with the key for me consistently across
cellular and wifi.
[image: image.png]

On Nov 25, 2012, at 9:20 PM, Jesse Smith notifications@github.com wrote:

From cellular (AT&T) both those links work for me. Let's see if we can
prove this solution by checking that the first fails (consistently) and the
second succeeds (consistently).

On Sun, Nov 25, 2012 at 9:17 PM, Jesse Smith Jesses16@gmail.com wrote:

OK, let's try each of these from both wifi and cell. Second one has the
apikey, not the first.

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false&key=AIzaSyCloHHOTgUAwKqVVpovHVzGioPQ8RkQeTY

On Sun, Nov 25, 2012 at 8:32 PM, robsturtz notifications@github.comwrote:

It happens pretty much every time on cellular including this one I just
generated. http://oyster.me/stories/315

On Nov 25, 2012, at 6:46 PM, Jesse Smith notifications@github.com
wrote:

Wait for the update? :)

Other than getting a dev version on your phone it's hard.

Perhaps when you notice the issue happening, I can send you a sample URL
to
google maps and we can try directly from the web browser

Jesse Smith

On Nov 25, 2012, at 5:05 PM, robsturtz notifications@github.com wrote:

How can I test with the API key in the request over cellular?

On Nov 25, 2012, at 4:43 PM, Jesse Smith notifications@github.com
wrote:

The research I've seen shows how this is likely related to the IP of the
device. Other than proxying all requests through our web server, there
are
no recommendations online.

However, I have tried including our API key to our requests for google
static maps, which may work and help explain why others aren't having
the
same issue.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701250>.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701519>.


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10702828>.


Reply to this email directly or view it on GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10704352>.

--Jesse Smith

--Jesse Smith


Reply to this email directly or view it on
GitHubhttps://github.com//issues/32#issuecomment-10704993.

@sosaucily
Copy link
Owner

Good test! Perhaps; can you clear cache?

Let's keep playing with these links for a while until we feel confident.

I see hits coming across our API Console in google now, so that's a good
sign.

On Sun, Nov 25, 2012 at 9:50 PM, robsturtz notifications@github.com wrote:

This image indicates exceeding the API limit. If we don't have a key they
might be pooling all requests?

Anyway seems to work correctly with the key for me consistently across
cellular and wifi.
[image: image.png]

On Nov 25, 2012, at 9:20 PM, Jesse Smith notifications@github.com
wrote:

From cellular (AT&T) both those links work for me. Let's see if we can
prove this solution by checking that the first fails (consistently) and
the
second succeeds (consistently).

On Sun, Nov 25, 2012 at 9:17 PM, Jesse Smith Jesses16@gmail.com wrote:

OK, let's try each of these from both wifi and cell. Second one has the
apikey, not the first.

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false&key=AIzaSyCloHHOTgUAwKqVVpovHVzGioPQ8RkQeTY

On Sun, Nov 25, 2012 at 8:32 PM, robsturtz notifications@github.comwrote:

It happens pretty much every time on cellular including this one I just
generated. http://oyster.me/stories/315

On Nov 25, 2012, at 6:46 PM, Jesse Smith notifications@github.com
wrote:

Wait for the update? :)

Other than getting a dev version on your phone it's hard.

Perhaps when you notice the issue happening, I can send you a sample
URL
to
google maps and we can try directly from the web browser

Jesse Smith

On Nov 25, 2012, at 5:05 PM, robsturtz notifications@github.com
wrote:

How can I test with the API key in the request over cellular?

On Nov 25, 2012, at 4:43 PM, Jesse Smith notifications@github.com
wrote:

The research I've seen shows how this is likely related to the IP of
the
device. Other than proxying all requests through our web server, there
are
no recommendations online.

However, I have tried including our API key to our requests for google
static maps, which may work and help explain why others aren't having
the
same issue.


Reply to this email directly or view it on
GitHub<

https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701250>.


Reply to this email directly or view it on
GitHub<

https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701519>.


Reply to this email directly or view it on
GitHub<

https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10702828>.


Reply to this email directly or view it on GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10704352>.

--Jesse Smith

--Jesse Smith


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10704993>.


Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-10705384.

--Jesse Smith

@robsturtz
Copy link
Collaborator Author

Yes I've been cache busting by changing the label parameter with each
refresh. Always busted on cellular without key. Always works on wifi
without key. Works on both cell and wifi with key.

On Nov 25, 2012, at 9:57 PM, Jesse Smith notifications@github.com wrote:

Good test! Perhaps; can you clear cache?

Let's keep playing with these links for a while until we feel confident.

I see hits coming across our API Console in google now, so that's a good
sign.

On Sun, Nov 25, 2012 at 9:50 PM, robsturtz notifications@github.com
wrote:

This image indicates exceeding the API limit. If we don't have a key they
might be pooling all requests?

Anyway seems to work correctly with the key for me consistently across
cellular and wifi.
[image: image.png]

On Nov 25, 2012, at 9:20 PM, Jesse Smith notifications@github.com
wrote:

From cellular (AT&T) both those links work for me. Let's see if we can
prove this solution by checking that the first fails (consistently) and
the
second succeeds (consistently).

On Sun, Nov 25, 2012 at 9:17 PM, Jesse Smith Jesses16@gmail.com wrote:

OK, let's try each of these from both wifi and cell. Second one has the
apikey, not the first.

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false&key=AIzaSyCloHHOTgUAwKqVVpovHVzGioPQ8RkQeTY

On Sun, Nov 25, 2012 at 8:32 PM, robsturtz notifications@github.comwrote:

It happens pretty much every time on cellular including this one I
just
generated. http://oyster.me/stories/315

On Nov 25, 2012, at 6:46 PM, Jesse Smith notifications@github.com
wrote:

Wait for the update? :)

Other than getting a dev version on your phone it's hard.

Perhaps when you notice the issue happening, I can send you a sample
URL
to
google maps and we can try directly from the web browser

Jesse Smith

On Nov 25, 2012, at 5:05 PM, robsturtz notifications@github.com
wrote:

How can I test with the API key in the request over cellular?

On Nov 25, 2012, at 4:43 PM, Jesse Smith notifications@github.com
wrote:

The research I've seen shows how this is likely related to the IP of
the
device. Other than proxying all requests through our web server, there
are
no recommendations online.

However, I have tried including our API key to our requests for google
static maps, which may work and help explain why others aren't having
the
same issue.


Reply to this email directly or view it on
GitHub<

https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701250>.


Reply to this email directly or view it on
GitHub<

https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701519>.


Reply to this email directly or view it on
GitHub<

https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10702828>.


Reply to this email directly or view it on GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10704352>.

--Jesse Smith

--Jesse Smith


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10704993>.


Reply to this email directly or view it on GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10705384>.

--Jesse Smith


Reply to this email directly or view it on
GitHubhttps://github.com//issues/32#issuecomment-10705481.

@sosaucily
Copy link
Owner

Nice! Seems like we've got it then.

Lets prioritize any other fixes deemed critical and get it into version
1.01.

Talk after work tmrw?

On Sun, Nov 25, 2012 at 10:01 PM, robsturtz notifications@github.comwrote:

Yes I've been cache busting by changing the label parameter with each
refresh. Always busted on cellular without key. Always works on wifi
without key. Works on both cell and wifi with key.

On Nov 25, 2012, at 9:57 PM, Jesse Smith notifications@github.com
wrote:

Good test! Perhaps; can you clear cache?

Let's keep playing with these links for a while until we feel confident.

I see hits coming across our API Console in google now, so that's a good
sign.

On Sun, Nov 25, 2012 at 9:50 PM, robsturtz notifications@github.com
wrote:

This image indicates exceeding the API limit. If we don't have a key
they
might be pooling all requests?

Anyway seems to work correctly with the key for me consistently across
cellular and wifi.
[image: image.png]

On Nov 25, 2012, at 9:20 PM, Jesse Smith notifications@github.com
wrote:

From cellular (AT&T) both those links work for me. Let's see if we can
prove this solution by checking that the first fails (consistently) and
the
second succeeds (consistently).

On Sun, Nov 25, 2012 at 9:17 PM, Jesse Smith Jesses16@gmail.com
wrote:

OK, let's try each of these from both wifi and cell. Second one has
the
apikey, not the first.

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false&key=AIzaSyCloHHOTgUAwKqVVpovHVzGioPQ8RkQeTY

On Sun, Nov 25, 2012 at 8:32 PM, robsturtz notifications@github.comwrote:

It happens pretty much every time on cellular including this one I
just
generated. http://oyster.me/stories/315

On Nov 25, 2012, at 6:46 PM, Jesse Smith notifications@github.com
wrote:

Wait for the update? :)

Other than getting a dev version on your phone it's hard.

Perhaps when you notice the issue happening, I can send you a sample
URL
to
google maps and we can try directly from the web browser

Jesse Smith

On Nov 25, 2012, at 5:05 PM, robsturtz notifications@github.com
wrote:

How can I test with the API key in the request over cellular?

On Nov 25, 2012, at 4:43 PM, Jesse Smith notifications@github.com
wrote:

The research I've seen shows how this is likely related to the IP of
the
device. Other than proxying all requests through our web server,
there
are
no recommendations online.

However, I have tried including our API key to our requests for
google
static maps, which may work and help explain why others aren't having
the
same issue.


Reply to this email directly or view it on
GitHub<

https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701250>.


Reply to this email directly or view it on
GitHub<

https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701519>.


Reply to this email directly or view it on
GitHub<

https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10702828>.


Reply to this email directly or view it on GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10704352>.

--Jesse Smith

--Jesse Smith


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10704993>.


Reply to this email directly or view it on GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10705384>.

--Jesse Smith


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10705481>.


Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-10705527.

--Jesse Smith

@robsturtz
Copy link
Collaborator Author

Good deal. I started filing a few things in the github issues for www
project. I'll call you on the drive home tomorrow.

On Nov 25, 2012, at 10:04 PM, Jesse Smith notifications@github.com wrote:

Nice! Seems like we've got it then.

Lets prioritize any other fixes deemed critical and get it into version
1.01.

Talk after work tmrw?

On Sun, Nov 25, 2012 at 10:01 PM, robsturtz notifications@github.comwrote:

Yes I've been cache busting by changing the label parameter with each
refresh. Always busted on cellular without key. Always works on wifi
without key. Works on both cell and wifi with key.

On Nov 25, 2012, at 9:57 PM, Jesse Smith notifications@github.com
wrote:

Good test! Perhaps; can you clear cache?

Let's keep playing with these links for a while until we feel confident.

I see hits coming across our API Console in google now, so that's a good
sign.

On Sun, Nov 25, 2012 at 9:50 PM, robsturtz notifications@github.com
wrote:

This image indicates exceeding the API limit. If we don't have a key
they
might be pooling all requests?

Anyway seems to work correctly with the key for me consistently across
cellular and wifi.
[image: image.png]

On Nov 25, 2012, at 9:20 PM, Jesse Smith notifications@github.com
wrote:

From cellular (AT&T) both those links work for me. Let's see if we can
prove this solution by checking that the first fails (consistently) and
the
second succeeds (consistently).

On Sun, Nov 25, 2012 at 9:17 PM, Jesse Smith Jesses16@gmail.com
wrote:

OK, let's try each of these from both wifi and cell. Second one has
the
apikey, not the first.

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false

http://maps.googleapis.com/maps/api/staticmap?center=37.794471,-122.410526&zoom=17&markers=color:blue%7Clabel:S%7C37.794471,-122.410526&size=576x174&sensor=false&key=AIzaSyCloHHOTgUAwKqVVpovHVzGioPQ8RkQeTY

On Sun, Nov 25, 2012 at 8:32 PM, robsturtz notifications@github.comwrote:

It happens pretty much every time on cellular including this one I
just
generated. http://oyster.me/stories/315

On Nov 25, 2012, at 6:46 PM, Jesse Smith notifications@github.com
wrote:

Wait for the update? :)

Other than getting a dev version on your phone it's hard.

Perhaps when you notice the issue happening, I can send you a sample
URL
to
google maps and we can try directly from the web browser

Jesse Smith

On Nov 25, 2012, at 5:05 PM, robsturtz notifications@github.com
wrote:

How can I test with the API key in the request over cellular?

On Nov 25, 2012, at 4:43 PM, Jesse Smith notifications@github.com
wrote:

The research I've seen shows how this is likely related to the IP of
the
device. Other than proxying all requests through our web server,
there
are
no recommendations online.

However, I have tried including our API key to our requests for
google
static maps, which may work and help explain why others aren't
having
the
same issue.


Reply to this email directly or view it on
GitHub<

https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701250>.


Reply to this email directly or view it on
GitHub<

https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10701519>.


Reply to this email directly or view it on
GitHub<

https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10702828>.


Reply to this email directly or view it on GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10704352>.

--Jesse Smith

--Jesse Smith


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10704993>.


Reply to this email directly or view it on GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10705384>.

--Jesse Smith


Reply to this email directly or view it on
GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10705481>.


Reply to this email directly or view it on GitHub<
https://github.com/jesses16/InstadateWWW/issues/32#issuecomment-10705527>.

--Jesse Smith


Reply to this email directly or view it on
GitHubhttps://github.com//issues/32#issuecomment-10705561.

@ghost ghost assigned sosaucily Dec 2, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants