Skip to content
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

APNs push err:strconv.ParseInt: parsing "1469425701606": value out of range #34

Closed
klights opened this issue Jul 25, 2016 · 10 comments
Closed
Labels

Comments

@klights
Copy link

klights commented Jul 25, 2016

strconv.ParseInt: parsing "1469425701606": value out of range
The error above happended sometime when i call client.Push(notification). Please help.

@sideshow
Copy link
Owner

Hey @klights
What version of go are you running?
How often is this happening, And is this the latest version of master?
Thanks

@klights
Copy link
Author

klights commented Jul 25, 2016

@sideshow Thanks for helping
my go version: go version go1.6.2 windows/amd64
it happended twice since 13:00 today, and this is the latest version of master.

@sideshow
Copy link
Owner

No probs. Can you please paste the stack trace here

@sideshow sideshow added the bug label Jul 27, 2016
@sideshow
Copy link
Owner

sideshow commented Jul 27, 2016

@klights I was able to reproduce this with golang compiled in 32 bit mode. Can you confirm wether or not you are running 32 or 64 bit and add a stack trace if possible, thanks.

@klights
Copy link
Author

klights commented Jul 27, 2016

@sideshow
it's so strange, and it hasn't occurred anymore, but i'm sure that it happended twice 2 days ago with my log below:
[2016/07/25 13:51:19 CST] EROR APNs push err:strconv.ParseInt: parsing "1469425701606": value out of range

i'll continue to observe, once it happend again i'll report more detail info to here.

@klights
Copy link
Author

klights commented Jul 28, 2016

@sideshow
Hello, I found the bug. The error will occur when http response like {"reason":"Unregistered","timestamp":1469668760413}.

sideshow added a commit that referenced this issue Aug 2, 2016
@sideshow
Copy link
Owner

sideshow commented Aug 2, 2016

@klights I have pushed a branch called fix-int-range
It should resolve the issue. Please have a try with this branch and let me know if you still experience the issue.

@sideshow
Copy link
Owner

Hey @klights did you get a chance to test this, and is it still happening?

alissonsales added a commit that referenced this issue Aug 17, 2016
@klights
Copy link
Author

klights commented Aug 19, 2016

@sideshow I checkout the branch fix-int-range and it resolve the issue.

@sideshow
Copy link
Owner

Great thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants