Error: [MC] Reading from public effective user settings.

[PiyushSanepara]

Swift version: Swift 3.0 Xcode version: Xcode 8.1

Note: I am also using IQKeyboard

[k0nserv]

Could you include some more error output and code to illustrate the problem?

[PiyushSanepara]

2016-12-21 15:15:26.941776 FloatLabelDemoNew[309:43804] [MC] System group container for systemgroup.com.apple.configurationprofiles path is /private/var/containers/Shared/SystemGroup/systemgroup.com.apple.configurationprofiles 2016-12-21 15:15:26.946414 FloatLabelDemoNew[309:43804] [MC] Reading from public effective user settings.

[k0nserv]

Is this actually causing any problems? From this Stackoverflow question it seems like it should be causing any problems and is only a harmless log message

[PiyushSanepara]

See the screen, i am setup Title Color(Green) for both field (Email and Password), but it work for password only.

[k0nserv]

Can I see your code? It might be a different problem

[PiyushSanepara]

I am using this with attribute inspector see:

[bogren]

To answer your first question: If you link with iOS 10 you must declare access to any user private data types. You do this by adding a the key and description to your app's Info.plist. Here is a list of frameworks: Contacts, Calendar, Reminders, Photos, Bluetooth Sharing, Microphone, Camera, Location, Health, HomeKit, Media Library, Motion, CallKit, Speech Recognition, SiriKit, TV Provider.

This is probably why you see the warning message in the debugger, and your app is going to crash if it's trying to use one of the frameworks.

[bogren]

I need more info to be able to answer your second issue. You can try to set the titleColor using the designables.

[PiyushSanepara]

@bogren i try designables but it doesn't work

[yatanadam]

@bogren @PiyushSanepara me too.

[bogren]

I need more info the be able to help :(

[hellohelloye]

I met the same problem, it crashed in session.dataTask function. I added the privacy key words but somehow it did not work. the error message you quoted is actually just a warning message not the cause of the crash. The actual cause of the crash is a EXC_BAD_ACCESS due to an improper conversion between Error and NSError because of the transaction of swift version to 3.0