Felix Krause

I guess that would be something for @mRs-, who is the developer of HexColors

I agree with @mRs- here. It's an advantage to have a dependency to not pull the same code multiple times if it's already in the project

What alternative to Hex codes would you use in our JSON configuration?

Can you check your .app folder if it contains the TSMessages bundle with the containing this file: https://github.com/toursprung/TSMessages/blob/master/Pod/Assets/TSMessagesDefaultDesign.json Can you set a breakpoint at https://github.com/toursprung/TSMessages/blob/master/Pod/Classes/TSMessageView.m#L76 and see if the values...

Can you try the latest version on master? I refactored some things, it should work better now.

Yes, that's exactly what I'm concerned about. The designated initialiser grows and grows. There is already an issue with some thoughts about that: https://github.com/toursprung/TSMessages/issues/54 I guess a major redesign of...

Well, it's not something that's your fault or your job. It's something I've been unhappy with TSMessages for a long time now. @dennisreimann and me are working on a better...

When it crashes there, the color value seems to be empty. Check if the json file for the design was properly delivered with the app.

It's working fine over here... As @mafellows mentioned, it seems to have a naming conflict with other classes.

@kiliankoe @davidrothera To be honest I'm afraid a new version introduces new errors, as the last release has been ages ago... I haven't had time to maintain TSMessages recently unfortunately....