-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong message timestamp on 32-bit devices #525
Comments
Hi @disabled. Nice Github handle :) @ricardopereira @tcard can you please advise on this issue? |
We were converting timestamps to NSInteger, which is a 32-bit or 64-bit int depending on the architecture. `long long` is guaranteed to be 64-bit wide. Fixes #525.
We were converting timestamps to NSInteger, which is a 32-bit or 64-bit int depending on the architecture. `long long` is guaranteed to be 64-bit wide. Fixes #525.
Hi @disabled! Thanks for the report. I've just pushed a fix to the repo. It will be included in the next release. In the meantime, you can point your Podfile (or however you're including the library) to the current master branch head. Please tell us if this actually fixes your problem, and of any other problem you may encounter. Thanks in advance! |
Hi @tcard. Thanks, timestamp is working fine now! |
We were converting timestamps to NSInteger, which is a 32-bit or 64-bit int depending on the architecture. `long long` is guaranteed to be 64-bit wide. Fixes #525.
Hello,
We are using ably-php to send messages and ably-ios to receive them.
In this scenario, message timestamp on iOS is wrong (using either ARTRest or ARTRealtime), but only on 32-bit devices. On 64-bit devices everything is working fine.
Here is example:
The text was updated successfully, but these errors were encountered: