Hi, Murshid.
This is a known issue which has been fixed in upcoming 4.1.1 and 4.2 packages. It's still not certain whether there will be a fix for older versions, due to difficutilties of patching that much live setups out there - because the issue isn't fatal on itlself and the SP you added should be usable (please test for yourself); it's just a web UI error which doesn't break actual SAML flows.