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

timeIntervalSinceReferenceDate crash #874

Closed
odyssey1357 opened this issue Dec 23, 2014 · 3 comments
Closed

timeIntervalSinceReferenceDate crash #874

odyssey1357 opened this issue Dec 23, 2014 · 3 comments

Comments

@odyssey1357
Copy link

Hello. I am using SalesForce SDK 3.0 in my app. While my application usage I got some feedbacks about crash at "application becomes active" event. I got a little log from BugSense:

-[__NSCFString timeIntervalSinceReferenceDate]: unrecognized selector sent to instance
/----------------------------------------------/
0 CoreFoundation + 130
1 libobjc.A.dylib objc_exception_throw + 38
2 CoreFoundation + 202
3 CoreFoundation + 706
4 CoreFoundation CF_forwarding_prep_0 + 24
5 CoreFoundation + 44
6 MyApp +[SFSecurityLockout inactivityExpired] + 100
7 MyApp +[SFSecurityLockout validateTimer] + 60
8 MyApp -[SalesforceSDKManager handleAppForeground:] + 1060
/
----------------------------------------------_/

P.S. I got a plist file with UserDefaults from one of my app users. I found this key-value pair:
timer.lastactivity
Мария
I know "timer.lastactivity" must keep date value, but it keeps string. My app doesn't use UserDefaults value by key "timer.lastactivity".

What's wrong? How can it be fixed.
Thanks for reply.

@khawkins
Copy link
Contributor

khawkins commented Jan 9, 2015

That's...very strange. The value that's set for timer.lastactivity should always be a date, the getting and setting of which is fully encapsulated by the SFInactivityTimerCenter class.

Do you have a reproduction scenario for this? And can you tell me how you originated the Mobile SDK into your app (forceios, the distribution repo binaries, etc.)?

@khawkins
Copy link
Contributor

In the absence of further information, I can't reproduce this bug. Feel free to reopen if you can provide a reproduction case.

@ClaudeSutterlin
Copy link

For what it's worth, we're experiencing this issue as well. Upwards of 1000 occurrences a day. I'll report back if I find any information to assist in debugging.

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

No branches or pull requests

3 participants