Thank you for your question!
I understand your concern and have good news to share with you. We recently discovered a solution to hide this warning and implemented the change internally. The update will be available with an internal build in the first half of May as well as the next official release scheduled to go live by the end of June, 2016.
Please excuse us for the temporary inconvenience!