-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Crash for iPhone 5S #93
Comments
Evernote was unable to submit your note for the following reason: The emailed note was received, but Evernote did not understand the email address. It may have been mistyped, or the user may not exist. Please check to make sure the address was properly entered. Original message information: To prevent excessive emails, you may not receive another error reply for the next 360 minutes.
|
I don't have iPhone 5s but Apple has rejected because of the reason. -[NSDateComponents eventForDatePicker:]: unrecognized selector sent to instance 0x14e86be0 Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSDateComponents eventForDatePicker:]: unrecognized selector sent to instance 0x14e86be0' |
Evernote was unable to submit your note for the following reason: The emailed note was received, but Evernote did not understand the email address. It may have been mistyped, or the user may not exist. Please check to make sure the address was properly entered. Original message information: To prevent excessive emails, you may not receive another error reply for the next 360 minutes.
|
me too, the crash is NSURLConnectionInternalConnection eventForDatePicker:]: unrecognized selector sent to instance 0x180f4650 |
Evernote was unable to submit your note for the following reason: The emailed note was received, but Evernote did not understand the email address. It may have been mistyped, or the user may not exist. Please check to make sure the address was properly entered. Original message information: To prevent excessive emails, you may not receive another error reply for the next 360 minutes.
|
Is this still an issue? If this is a showstopper for Apple, it is a serious problem! |
Evernote was unable to submit your note for the following reason: The emailed note was received, but Evernote did not understand the email address. It may have been mistyped, or the user may not exist. Please check to make sure the address was properly entered. Original message information: To prevent excessive emails, you may not receive another error reply for the next 360 minutes.
|
The Issue persists with the latest version as well , appears to be serious problem |
Evernote was unable to submit your note for the following reason: The emailed note was received, but Evernote did not understand the email address. It may have been mistyped, or the user may not exist. Please check to make sure the address was properly entered. Original message information: To prevent excessive emails, you may not receive another error reply for the next 360 minutes.
|
I was getting a bad access crash from datepicker on 64bit devices. I changed architecture to armv7, armv7s and the crash disappeared. |
Evernote was unable to submit your note for the following reason: The emailed note was received, but Evernote did not understand the email address. It may have been mistyped, or the user may not exist. Please check to make sure the address was properly entered. Original message information: To prevent excessive emails, you may not receive another error reply for the next 360 minutes.
|
You could try the fix from my pull request: #99 |
Evernote was unable to submit your note for the following reason: The emailed note was received, but Evernote did not understand the email address. It may have been mistyped, or the user may not exist. Please check to make sure the address was properly entered. Original message information: To prevent excessive emails, you may not receive another error reply for the next 360 minutes.
|
I didn't check the pull request, but I used NSUserDefaults from where I was getting the date to the callback method. It's not a real solution, but a solid fix. |
Evernote was unable to submit your note for the following reason: The emailed note was received, but Evernote did not understand the email address. It may have been mistyped, or the user may not exist. Please check to make sure the address was properly entered. Original message information: To prevent excessive emails, you may not receive another error reply for the next 360 minutes.
|
This bug already fixed in Now you can use my up-to-date version of ActionSheetPicker (ActionSheetPicker-3.0) |
Evernote was unable to submit your note for the following reason: The emailed note was received, but Evernote did not understand the email address. It may have been mistyped, or the user may not exist. Please check to make sure the address was properly entered. Original message information: To prevent excessive emails, you may not receive another error reply for the next 360 minutes.
|
I have similar issue on Got below stacktrace:
ActionSheetDatePicker should call |
@ypresto |
oh sorry, i was reporting to wrong repo :) |
@ypresto according your problem: try to update to latest version. It should fix your problem. |
skywinder#65 is exactly my problem. I'll update. Thanks for your fix! |
Fix statusBar visibility
The date picker is crashing for iPhone 5S. Works for all other devices and iPad as well.
Tested on multiple 5S's. The callback returns nil date.
The text was updated successfully, but these errors were encountered: