Domain=org.openid.appauth.general Code=-15 "Issued at time is more than 600 seconds before or after the current time" - google-signin

If you change your phone's system time, you will get an error if you log in using Google:Error Domain=org.openid.appauth.general Code=-15 "Issued at time is more than 600 seconds before or after the current time" UserInfo={NSLocalizedDescription=Issued at time is more than 600 seconds before or after the current time}
What do I need to do to change the system time of the mobile phone and still use Google login normally?

Related

Map 624 could not be created for player GUID + unable to zone in while an encounter is in progress (Wintergrasp)

In the worldserver.conf I have disabled all Wintergrasp processing with the following option
Wintergrasp.Enable = 2
When I look at the Wintergrasp map no encounter is in progress, the doors to VOA are open but when I try to enter the VOA raid I get teleported back to my hearthstone location and receive the message:
unable to zone in while an encounter is in progress
The worldserver output shows:
Map 624 could not be created for player GUID Full: 0x0000000000000001 Type: Player Low: 1, porting player to homebind
I have tried changing the worldserver config Wintergrasp.Enable from 0 to 1 or 2 and it didn't have any effect on the in-game error unable to zone in while an encounter is in progress or the worldserver output error Map 624 could not be created for player GUID Full: 0x0000000000000001 Type: Player Low: 1, porting player to homebind
I also tried to see if it timed out but after 4 hours of letting the server run, the error remained the same when trying to enter the VOA raid.
Any tips on how to clear/fully disable the Wintergrasp encounter so I can enter VOA without being teleporter back to my hearthstone location when entering the raid?
Fixed this by setting the AzerothCore Wintergrasp enable setting to 0 so the battleground is disabled but processing is enabled and set the timers for the battle duration to 1 and nobattle timer to 90 minutes. This causes it to finish processing and after processing, it opens up for horde/alliance every 80 minutes with a 1-minute battle in between where you can't zone in. There is a check though in the source that whenever the counter is below 10 minutes you will be unable to zone in. So thats why the nobattle timer should be on 90 minute+. Both factions can enter the raid portal for VOA if you have an option to teleport over there for players

Verify time with 3 seconds buffer

Get Current Audio Upload Time
${time}= Get Current Date
${converted-time}= Convert Date ${time} result_format=%H:%M:%S
Log To Console time is ${converted-time}
Set Global Variable ${converted-time}
this script verifies that after searching the string, the result is returned then verify time is correct.
however, there is elapsed when the robot captured the current time vs the application captured time.
I cannot verify it directly, I need to give 3 seconds buffer.
robot captured time: 16:38:04
app captured time: 16:38:56
Verify Audio Time
[Arguments] ${RandomNumber}
Wait For Elements State //mark[text()='Dual-Channel-Audio-${RandomNumber}']//following::td[text()='${converted-time}']
UI which shows time

Why Google Measurement Protocol is splitting my session before the configured limit?

I'm working on a TV application and I would like to track what people do on it. So I used Google Measurement Protocole to do so. The page and event tracking is working fine because I can see in real time what's is happening on the Analytics 360 website. Everything was ok until I look at the "User explorer" to pick a random user in order to see what he did previously. I found out that he had a lot of sessions in a very short period. So I ran a test for myself yesterday and the result is the same today. I had only 1 session with multiple events for more than an hour and by paying attention to trigger an event before the 30min of inactivity which is configured by default.
Here are examples of data sent :
ds=qml
v=1
tid=UA-XXX-YYY
cd1=local
cm=tv
cid=123456789 (unique id)
uip=XX.XX.XX.XX
ua=SAMSUNG
ul=en
cd=HomePage
dp=HomePage
dt=home
cs=MY_TV_APP
t=event
ec=MY_TV_APP
ea=click on button
el=HomePage
or
ds=qml
v=1
tid=UA-XXX-YYY
cd1=local
cm=tv
cid=123456789 (unique id)
uip=XX.XX.XX.XX
ua=SAMSUNG
ul=en
cd=HomePage
dp=HomePage
dt=home
cs=MY_TV_APP
t=pageview
Here is a screenshot of my session: here
As you can see, there are 7 sessions instead of 1... I don't understand why my session was splitted into 7 parts. I tried to use "sc=start" and "sc=end", the result is the same.
Has anyone ever encountered this problem before?

Link should navigate for book after a certion time

I have a aspx page for booking tickets, and i am providing link to users through mail(link of booking page) .
when they click that link it should check the time 09:00 AM then it should navigate to booking page else redirect to another page showing message "not allowed this time"
if (DateTime.Now.Hour == 9)
Response.Redirect("Page.aspx");
else
Response.Write("<script language='javascript'>alert('Not allowed this time');</script>");
You are checking for a Current time of the Server using DateTime.Now.Hour. It takes current time from a server, and taking only HOUR part of this datetime. If your hour is 9 o'clock (it don't consider minutes), user will be redirected to the some Page.aspx. You have to change the name.
If it is not 9 o'clock, corresponding alert will be displayed.

BidSystem, online auction, problem with timing

guys!
I'm developing an online auction with time limit.
The ending time period is only for one opened auction.
After logging into the site I show the time left for the open auction. The time is calculated in this way:
EndDateTime = Date and Time of end of auction;
DateTime.Now() = current Date and Time
timeLeft= (EndDateTime - DateTime.Now()).Seconds().
In javascript, I update the time left by:
timeLeft=timeLeft-1
The problem is that when I login from different browsers at the same time the browsers show a different count down.
Help me, please!
I guess there will always be differences of a few seconds because of the server processing time and the time needed to download the page.
The best way would be to actually send the end time to the browser and calculate the time remaining in javascript. That way the times should be the same (on the same machine of course).
Roman,
I had a little look at eBay (they know a thing or two about this stuff :)) and noticed that once the item is inside the last 90 seconds, a GET request gets fired every 2 seconds to update the variables in the javascript via a json response. you can look at this inside firebug/fiddler to see what it does.
here is an example of the json it pulls down:
{
"ViewItemLiteResponse":{
"Item":[
{
"IsRefreshPage":false,
"ViewerItemRelation":"NONE",
"EndDate":{
"Time":"12:38:48 BST",
"Date":"01 Oct, 2010"
},
"LastModifiedDate":1285932821000,
"CurrentPrice":{
"CleanAmount":"23.00",
"Amount":23,
"MoneyStandard":"£23.00",
"CurrencyCode":"GBP"
},
"IsEnded":false,
"AccessedDate":1285933031000,
"BidCount":4,
"MinimumToBid":{
"CleanAmount":"24.00",
"Amount":24,
"MoneyStandard":"£24.00",
"CurrencyCode":"GBP"
},
"TimeLeft":{
"SecondsLeft":37,
"MinutesLeft":1,
"HoursLeft":0,
"DaysLeft":0
},
"Id":160485015499,
"IsFinalized":false,
"ViewerItemRelationId":0,
"IsAutoRefreshEnabled":true
}
]
}
}
You could do something similar inside your code.
[edit] - on further looking at the eBay code, altho it only runs the intensive GET requests in the last 90 seconds, the same json as above is added when the page is initially loaded as well. Then, at 3 mins or so, the GET request is run every 10 seconds. therefore i assume the same javascript is run against that structure whether it be >90 seconds or not.
This may be a problem with javascript loading at different speeds,
or the setInterval will trigger at slightly different times depending on the loop
i would look into those two

Resources