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

log to console #8

Closed
nikhilpandey4 opened this issue Mar 21, 2017 · 6 comments
Closed

log to console #8

nikhilpandey4 opened this issue Mar 21, 2017 · 6 comments

Comments

@nikhilpandey4
Copy link

Whenever two text fields are connected via nextNavigationField following types of log messages occur

Reading from private effective user settings.
navigationFieldDidTapNextButton: <UITextField: 0x7fb48d725cb0; frame = (0 0; 328 30); text = '100'; clipsToBounds = YES; opaque = NO; autoresize = RM+BM; gestureRecognizers = <NSArray: 0x60800045aa90>; layer = <CALayer: 0x600000035a20>>
navigationFieldDidTapNextButton: <UITextField: 0x7fb48d61c780; frame = (0 0; 328 30); text = ''; clipsToBounds = YES; opaque = NO; autoresize = RM+BM; gestureRecognizers = <NSArray: 0x60000025e1e0>; layer = <CALayer: 0x600000036d40>>
navigationFieldDidTapNextButton: <UITextField: 0x7fb48d6201e0; frame = (0 0; 328 30); text = ''; clipsToBounds = YES; opaque = NO; autoresize = RM+BM; gestureRecognizers = <NSArray: 0x600000440ed0>; layer = <CALayer: 0x600000037b80>>
navigationFieldDidTapNextButton: <UITextField: 0x7fb48d625590; frame = (0 0; 328 30); text = ''; clipsToBounds = YES; opaque = NO; autoresize = RM+BM; gestureRecognizers = <NSArray: 0x60000044a5c0>; layer = <CALayer: 0x6000000394c0>>
navigationFieldDidTapNextButton: <UITextField: 0x7fb48d628c40; frame = (0 0; 328 30); text = ''; clipsToBounds = YES; opaque = NO; autoresize = RM+BM; gestureRecognizers = <NSArray: 0x60000044d2f0>; layer = <CALayer: 0x60000003a320>>
navigationFieldDidTapNextButton: <UITextField: 0x7fb48d628c40; frame = (0 0; 328 30); text = ''; clipsToBounds = YES; opaque = NO; autoresize = RM+BM; gestureRecognizers = <NSArray: 0x60000044d2f0>; layer = <CALayer: 0x60000003a320>>
Though no problem with running of app is found but why this log message appears should be investigated.
Thanks

@T-Pham
Copy link
Owner

T-Pham commented Mar 21, 2017

Hey @nikhilpandey4, thanks for opening this issue here.
May I know what iOS version you was on when you get this issue?

@nikhilpandey4
Copy link
Author

nikhilpandey4 commented Mar 21, 2017 via email

@T-Pham
Copy link
Owner

T-Pham commented Mar 21, 2017

Actually, it seems like you got the message when running your app in the iOS simulator.

The message "Reading from private effective user settings." is likely from the iOS SDK and not from this library at all.

For the rest of the message, "navigationFieldDidTapNextButton: ....", please check your code, it must print the string out somewhere somehow. Search for print("navigationFieldDidTapNextButton: in your whole project to see if there is any result.

Just FYI, I don't leave any print statement in the library code. I do leave some print statements in the Example app though.

@nikhilpandey4
Copy link
Author

nikhilpandey4 commented Mar 22, 2017 via email

@T-Pham
Copy link
Owner

T-Pham commented Mar 22, 2017

IMHO, just because of the message appears only when this library is added doesn't mean the message comes from this library. This message is built for UITextField and UITextView which are from the iOS SDK and your code has to be changed to adopt this library as well.

There are reports that interacting with UITextField somehow produces the message "Reading from private effective user settings."
And I guess the "navigationFieldDidTapNextButton:" part is from your code in the delegate for this library.

Anyway, since it does not affect the performance in anyway as per your input, I will close the issue for now. I am more than willing to re-open it whenever it can be proved to be caused by this library.

Have a nice day ahead!

@T-Pham T-Pham closed this as completed Mar 22, 2017
@nikhilpandey4
Copy link
Author

nikhilpandey4 commented Mar 22, 2017 via email

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

2 participants