I have a reservation application with a c# mvc api mssqlserver backend and angular frontend, everything is fine in Chrome on browser
however when I go to Safari IOS the dates are off by a single day
for example - on browser: 28th reservation( fromdate:28th todate: 28th)
startdate: 2018-06-28 00:00:00.0000000
end date: 2018-06-28 00:00:00.0000000
- on IOS safari: 28th reservation(fromdate: 27th todate: 27th)
example: 2
on browser: june28th-july19th
on IOS safari: june 27th - july 18th
the dates are retrieved from the db table and I can ensure that their format is
(2018-06-28 00:00:00.0000000)
Additionally, I noticed that when I get that exact datetime on ios it's different than browser- for example, I checked into my reservation at 11:08am and on IOS it showed the same date/time as 7:08am this could possibly be a factor but I don't know how to approach this issue
Related
I send request via REST API
https://www.mysite.pl/rest/V1/orders/89
And have date and time:
"created_at": "2021-09-21 15:59:34",
When I go to Saels->Orders in admin there is different data and time:
"Sep 21, 2021, 5:59:34 PM"
So there is a 2 hours difference. I think this cause a problem with my payment module. In admin timezone is set to CET Warsaw. Why in REST API call there is other time ?
I fixed this issue for me by selecting the "Coordinated Universal time" in admin:
Store -> configuration -> General -> General -> Local Options
I'm integrating identity server with my angular 6 app. I have an issue with angular-oauth2-oidc library which throws me an error about not a valid token, which is valid when I'm checking it by using hasValidAccessToken function then return me true value. Console shows me different status.
https://ibb.co/CVswZ9K
public isValidAccessToken() {
return this.oauthService.hasValidAccessToken();
}
Having a look at that error message, there are three timestamps:
now: 1547200214894 (GMT: Friday, January 11, 2019 9:50:14.894 AM)
issuedAtMSec: 1547201970000 (GMT: Friday, January 11, 2019 10:19:30 AM)
expiresAtMSec: 1547202270000 (GMT: Friday, January 11, 2019 10:24:30 AM)
The token is not valid as it was issued in the future. Either the server you are getting your token from is in the future, or your machine is in the past.
In our Angular 5 application, we are using Microsoft Graph to retrieve mail messages from a mailbox and then send a reply. For creating the reply, we use the REST API:
https://graph.microsoft.com/v1.0/me/messages/{message ID}/createReply
This creates a reply with a timezone that is UTC, but we expect it to be GMT+1. For example, in the mail body it says:
From: Melissa van Dijk
Sent: Friday, February 23, 2018 9:51:49 AM (wrong timestamp)
To: Melissa van Dijk
Subject: Meet for lunch?
We checked the settings in our Office 365 mail account and there it is specified that our local timezone is GMT+1 (Brussels, Amsterdam...).
(When replying via Outlook webmail, we get a correct timestamp).
Is this a bug or do we have to correct this timestamp ourselves? Or do we need to pass the timezone with the REST call somehow?
Thanks in advance!
I'm not sure if you can adjust the human-formatted timestamps in the HTML message body, but you can certainly use the ISO 8601 formatted timestamps in the other fields in the JSON of the response. For example, you'll find:
{
...
"sentDateTime": "2018-02-23T09:51:49Z",
...
}
While this is also in UTC (denoted by the Z), you can easily parse it by using a JavaScript Date object, or Angular's own datetime functions, or your favorite time library such as Luxon, Moment, or Date-fns. From there, displaying it in local time is trivial.
i integrated google calendar in my iOS application, and insert events from application using this Call "
https://www.googleapis.com/calendar/v3/calendars/primary/events "
and events inserted sucessfully in my google calendar
i updated pods due to ios 11 now this api
now it gives this error in response. cant figure it out where the problem is.
ERROR: Invalid value for: Invalid format: \"2017-12-07 07:00:00\" is malformed at \" 07:00:00\
The error prolly is due to wrong time format. Follow the RFC3339 for date time formats. It looks something like:
2015-05-28T09:00:00-07:00
Notice the letter T which stands for full date/full-time.
I'm trying to lookup my app from this method: http://itunes.apple.com/US/lookup?bundleId=com.writingfuture.where2
But it always return
{
"resultCount":0,
"results": []
}
My app status in the store is perfectly fine (ready for sale). Here's a detail:
Bundle ID: com.writingfuture.where2
Apple ID: 467311933
Type: iOS App
Version: 2.0.1
Status: Ready for Sale
Date Created: Dec 4, 2012
Date Released: Dec 10, 2012
I have no idea why I can't lookup for my app with this method.
Do you guys have any idea?
Thanks in advance,
Chammp
Looks like your app is ONLY available in Thailand storefront - so the lookup should include country code in the base lookup URL:
http://itunes.apple.com/th/lookup?bundleId=com.writingfuture.where2
The alternative to using bundleId is simply looking up by adamID:
http://itunes.apple.com/th/lookup?id=467311933
If your app is available only in Thailand you should add info about country in request
http://itunes.apple.com/lookup?bundleId=com.writingfuture.where2&country=th