What steps will reproduce the problem?

1. Share a photo with an app
2. Record the share timestamp
3. Record the callback timestamp

What is the expected output? What do you see instead?

I expect to see a quick and stable response time (e.g. between 1 and 30 seconds). Instead I see a random unstable response time (e.g. between 1 second and 20 minutes). The time of day has a bit of an effect (e.g. business hours Pacific Time seems to be the most unstable time) so this might be server traffic related, but it still affects development efforts enough to warrant at least an explanation for raised awareness.

What version of the product are you using? On what operating system?

Latest Glass firmware - 2013.08.21

Please provide any additional information below.

We're currently investigating this issue, which seems to be affecting multiple users.

We believe that the cause of this issue has been tracked down and fixed. If you still find yourself experiencing significant lag times, please let us know.

We are still experiencing the issue. The latency is more than a minute. For subscriptions, we are using https://mirrornotifications.appspot.com/forward?url= On the Glassware side, we see the response almost immediately.

I still have the lag about 1-5minutes for Glass to receive updates from the server as well for the callbacks from timeline actions. When using the playground https://developers.google.com/glass/playground the response is immediate. The lag only happens on the actual device (I've tried 2 different WiFi networks and GSM over bluetooth - on all of them it worked fine until recently)

I am wondering, is it to do with the use of mirrornotifications.appspot.com proxy server for subscription. I am inclined to use my own SSL enabled server for subscription, and then check on the latency.

I don't think the issue is related with subscription, rather, how glass device gets notified when data is available for the device.

It is your Glassware that gets notified upon sharing of content by Glass device, via subscription. The Glass device just receives the content or shares content. As I said earlier, the Glassware is able to push content w/o lag, but Glass device doesnot receive the content in-time.

I have the same issue that the Glass receives the timeline updates after some delay.

could you please point me to the location, where it says, how to deploy Java-starter-project to Google App Engine. I want to use the Google infrastructure to deploy my Glassware and check if that improves the performace of timeline cards rendering to Glass.

I have asked this issue in stack overflow, also talked to glass customer support, but could not be resolved. (http://stackoverflow.com/questions/17578757/any-reason-why-latency-in-updating-timelineitem-to-my-glass-device/17687032#17687032)

I believe there may be two different issues: (1) Glass connected to private network which is inside enterprise network with firewall settings (2) Network traffic issue (since i see this delay in even private home network)

There are two issues and two different scenarios:

Issues: (1) Issue related to pushing data to the glass device (it has been fixed, it takes around < 45 seconds, it is acceptable now) (2) Issue related to sending notification back to Mirror Server to Glassware app running in the Google App Engine.

Scenarios: (1) Glass connected to private network which is inside enterprise network with firewall settings (2) Network traffic issue (both private home network and private network inside firewall settings)

I installed the glassware on App Engine. Would check to see if the response is better, since now using Google infrastructure.

My glassware app is running in the Google App Engine, still i see very slow response depends on timing and location.

Comment deleted

I am seeing the same issue. When I add cards it can take 5+ minutes to show up on Glass. I see the same problem when using another Glassware, Zapier (which everyone should check out!!). I experience the issue when tethered to my LTE iPad, home wifi, and enterprise wifi. The nasty part is the cards show up when I list query the timeline. So the issue is between Glass and Google (do not rule out my connections).

I've timed callback responses taking as long as 20 minutes since the last update (EX9). Should this ticket be re-opened or a new ticket created?

For me too it started back again where the messages are getting delayed quite a bit. I have a demo in next couple weeks and this will have a negative impact on the demo, can someone please look into it?

My cards are now showing up hours after my demos. It's making it really hard to sell Glass to my company. I keep having to show the Playground to show the resulting cards, which is not ideal. I totally get that this is super early and the Mirror API is still scaling. I just need some feedback that it's not my code.

Comment deleted

It happened to me and i totally understand your feelings.

Worked on many nights and weekends very hard, when demoed, delayed response killed the whole essence of the glassware app as well as glass.
We totally understand that we are in the explorer stage, we should expect such behaviors, however, these issues should be addressed and provide some kind of guidelines or workaround. Thanks

The time of day has a bit of an effect (e.g. business hours Pacific Time seems to be the most unstable time)

I agree, it worked morning but after 4PM PST seen slow response.

I have now been awaiting a response from three test inserts for going on 50 minutes, this it the slowest notification response time that I've experienced yet.

Responses are taking more than one hour now (e.g. I still have received a response from my last set of test inserts). Can we please re-open this ticket? It has not been fixed.

Hey issue #185 followers,

There seem to be new issues with unstable latency. The root cause appears to be different, so it's likely that only a subset of you are impacted. If you're impacted, please check out issue #201 - https://code.google.com/p/google-glass-api/issues/detail?id=201