As of April 12th, you must go to Progress SupportLink to create new support cases or to access existing cases. Please, bookmark the SupportLink URL and use the new portal to contact the support team.
I assume the file attribute "_expiresAt" which is returned by the Kinvey.Files.find() is based on the servertime of Kinvey or Google. At the time I was testing I got for TTL = 3600:
_expiresAt: "2018-07-28T22:25:12.986Z"
... fine. Now I increase it by 1 hour: TTL = 7200 and to the same request like a minute later:
_expiresAt: "2018-07-28T22:26:04.178Z"
... weird: I expected 2018-07-28T23:....
Any higher TTL value will be ignored as well. Is the property "_expiresAt" not representing the real _expiresAt?
In your samples here you use findById in conjunction with TTL. Does the TTL option only work with findById in relation with file references?
Tayger
Hello
I was trying to increase the _expireAt of file-links this way:
I assume the file attribute "_expiresAt" which is returned by the Kinvey.Files.find() is based on the servertime of Kinvey or Google. At the time I was testing I got for TTL = 3600:
_expiresAt: "2018-07-28T22:25:12.986Z"
... fine. Now I increase it by 1 hour: TTL = 7200 and to the same request like a minute later:
_expiresAt: "2018-07-28T22:26:04.178Z"
... weird: I expected 2018-07-28T23:....
Any higher TTL value will be ignored as well. Is the property "_expiresAt" not representing the real _expiresAt?
In your samples here you use findById in conjunction with TTL. Does the TTL option only work with findById in relation with file references?
Regards