Comments (12)
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.
from instadatewww.
How can I test with the API key in the request over cellular?
from instadatewww.
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 [email protected] wrote:
How can I test with the API key in the request over cellular?
On Nov 25, 2012, at 4:43 PM, Jesse Smith [email protected] 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.
from instadatewww.
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 [email protected] 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 [email protected] wrote:
How can I test with the API key in the request over cellular?
On Nov 25, 2012, at 4:43 PM, Jesse Smith [email protected] 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.
from instadatewww.
OK, let's try each of these from both wifi and cell. Second one has the
apikey, not the first.
On Sun, Nov 25, 2012 at 8:32 PM, robsturtz [email protected] wrote:
It happens pretty much every time on cellular including this one I just
generated. http://oyster.me/stories/315On Nov 25, 2012, at 6:46 PM, Jesse Smith [email protected]
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 browserJesse Smith
On Nov 25, 2012, at 5:05 PM, robsturtz [email protected] wrote:
How can I test with the API key in the request over cellular?
On Nov 25, 2012, at 4:43 PM, Jesse Smith [email protected]
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
from instadatewww.
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 [email protected] wrote:
OK, let's try each of these from both wifi and cell. Second one has the
apikey, not the first.On Sun, Nov 25, 2012 at 8:32 PM, robsturtz [email protected]:
It happens pretty much every time on cellular including this one I just
generated. http://oyster.me/stories/315On Nov 25, 2012, at 6:46 PM, Jesse Smith [email protected]
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 browserJesse Smith
On Nov 25, 2012, at 5:05 PM, robsturtz [email protected] wrote:
How can I test with the API key in the request over cellular?
On Nov 25, 2012, at 4:43 PM, Jesse Smith [email protected]
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
from instadatewww.
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 [email protected] 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 [email protected] wrote:
OK, let's try each of these from both wifi and cell. Second one has the
apikey, not the first.On Sun, Nov 25, 2012 at 8:32 PM, robsturtz [email protected]:
It happens pretty much every time on cellular including this one I just
generated. http://oyster.me/stories/315On Nov 25, 2012, at 6:46 PM, Jesse Smith [email protected]
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 browserJesse Smith
On Nov 25, 2012, at 5:05 PM, robsturtz [email protected] wrote:
How can I test with the API key in the request over cellular?
On Nov 25, 2012, at 4:43 PM, Jesse Smith [email protected]
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.
from instadatewww.
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 [email protected] 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 [email protected] wrote:
OK, let's try each of these from both wifi and cell. Second one has the
apikey, not the first.On Sun, Nov 25, 2012 at 8:32 PM, robsturtz [email protected]:
It happens pretty much every time on cellular including this one I just
generated. http://oyster.me/stories/315On Nov 25, 2012, at 6:46 PM, Jesse Smith [email protected]
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 browserJesse Smith
On Nov 25, 2012, at 5:05 PM, robsturtz [email protected] wrote:
How can I test with the API key in the request over cellular?
On Nov 25, 2012, at 4:43 PM, Jesse Smith [email protected]
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.
from instadatewww.
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 [email protected] 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 [email protected]
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 [email protected] wrote:
OK, let's try each of these from both wifi and cell. Second one has the
apikey, not the first.On Sun, Nov 25, 2012 at 8:32 PM, robsturtz [email protected]:
It happens pretty much every time on cellular including this one I just
generated. http://oyster.me/stories/315On Nov 25, 2012, at 6:46 PM, Jesse Smith [email protected]
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 browserJesse Smith
On Nov 25, 2012, at 5:05 PM, robsturtz [email protected]
wrote:How can I test with the API key in the request over cellular?
On Nov 25, 2012, at 4:43 PM, Jesse Smith [email protected]
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
from instadatewww.
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 [email protected] 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 [email protected]
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 [email protected]
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 [email protected] wrote:
OK, let's try each of these from both wifi and cell. Second one has the
apikey, not the first.On Sun, Nov 25, 2012 at 8:32 PM, robsturtz [email protected]:
It happens pretty much every time on cellular including this one I
just
generated. http://oyster.me/stories/315On Nov 25, 2012, at 6:46 PM, Jesse Smith [email protected]
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 browserJesse Smith
On Nov 25, 2012, at 5:05 PM, robsturtz [email protected]
wrote:How can I test with the API key in the request over cellular?
On Nov 25, 2012, at 4:43 PM, Jesse Smith [email protected]
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.
from instadatewww.
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 [email protected]:
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 [email protected]
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 [email protected]
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 [email protected]
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 [email protected]
wrote:OK, let's try each of these from both wifi and cell. Second one has
the
apikey, not the first.On Sun, Nov 25, 2012 at 8:32 PM, robsturtz [email protected]:
It happens pretty much every time on cellular including this one I
just
generated. http://oyster.me/stories/315On Nov 25, 2012, at 6:46 PM, Jesse Smith [email protected]
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 browserJesse Smith
On Nov 25, 2012, at 5:05 PM, robsturtz [email protected]
wrote:How can I test with the API key in the request over cellular?
On Nov 25, 2012, at 4:43 PM, Jesse Smith [email protected]
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
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
from instadatewww.
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 [email protected] 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 [email protected]:
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 [email protected]
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 [email protected]
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 [email protected]
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 [email protected]
wrote:OK, let's try each of these from both wifi and cell. Second one has
the
apikey, not the first.On Sun, Nov 25, 2012 at 8:32 PM, robsturtz [email protected]:
It happens pretty much every time on cellular including this one I
just
generated. http://oyster.me/stories/315On Nov 25, 2012, at 6:46 PM, Jesse Smith [email protected]
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 browserJesse Smith
On Nov 25, 2012, at 5:05 PM, robsturtz [email protected]
wrote:How can I test with the API key in the request over cellular?
On Nov 25, 2012, at 4:43 PM, Jesse Smith [email protected]
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
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.
from instadatewww.
Related Issues (20)
- Add a clear button 'x' in the zipcode field. HOT 1
- Disable buttons after tap
- Permalink mobile view for shared dates
- Create launch tour HOT 2
- Add ability to block certain venues
- category management admin
- API calls happen concurrently
- background bubble image is not set to retina
- Only two chapters sometimes!
- Use a location bounding box rather than a zipcode and miles HOT 1
- Update yelp presentation for compliance
- Fix css issue on web permalink page
- App header should read "OysterMe" HOT 1
- Add Jambase API for local music
- Getting only 2 results! HOT 1
- Is upcoming working? Maybe they're throttling? HOT 1
- Swipe for more - backend HOT 1
- Swipe for more - frontend
- Swipe for more - Images
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from instadatewww.