Now our logs are rapidly filling with these messages:
App 2951343 output: WARNING: The Class.identifier is undocumented and was meant for internal framework usage only. As it is no longer used by the framework it will be removed in a coming non-breaking ViewComponent release.
App 2951343 output: WARNING: The Class.identifier is undocumented and was meant for internal framework usage only. As it is no longer used by the framework it will be removed in a coming non-breaking ViewComponent release.
App 2951343 output: WARNING: The Class.identifier is undocumented and was meant for internal framework usage only. As it is no longer used by the framework it will be removed in a coming non-breaking ViewComponent release.
App 2951343 output: WARNING: The Class.identifier is undocumented and was meant for internal framework usage only. As it is no longer used by the framework it will be removed in a coming non-breaking ViewComponent release.
App 2951343 output: WARNING: The Class.identifier is undocumented and was meant for internal framework usage only. As it is no longer used by the framework it will be removed in a coming non-breaking ViewComponent release.
App 2951343 output: WARNING: The Class.identifier is undocumented and was meant for internal framework usage only. As it is no longer used by the framework it will be removed in a coming non-breaking ViewComponent release.
App 2951343 output: WARNING: The Class.identifier is undocumented and was meant for internal framework usage only. As it is no longer used by the framework it will be removed in a coming non-breaking ViewComponent release.
App 2951343 output: WARNING: The Class.identifier is undocumented and was meant for internal framework usage only. As it is no longer used by the framework it will be removed in a coming non-breaking ViewComponent release.
Hi @jcoyne 👋 You shouldn't see these logs with agent v9.15.0, which has just been released! Thanks for sharing and I'm going to close this issue, but please re-open if you're seeing anything else we can help with.
related to #2870
Now our logs are rapidly filling with these messages:
Can you avoid calling this deprecated method?